For more information about this image and its history, please see the relevant manifest file (library/clearlinux). This image is updated via pull requests to the docker-library/official-images GitHub repo.
For detailed information about the virtual/transfer sizes and individual layers of each of the above supported tags, please see the repos/clearlinux/tag-details.md file in the docker-library/repo-info GitHub repo.
This serves as the official Clear Linux OS image.
The clearlinux:latest tag will point to clearlinux:base which will track toward the latest release version of the distribution.
This image contains the os-core and os-core-update bundles, the latter can be used to add additional Clear Linux OS components (see here for more details about swupd and here for more information on bundles).
The following Dockerfile will install the editors and dev-utils bundles on top of the base image
FROM clearlinux:base
RUN swupd bundle-add editors dev-utilsWhere editors contains the usual suspects for command line editors and dev-utils contains some handy development tools like strace, gdb and valgrind.
This image is officially supported on Docker version 1.12.0.
Support for older versions (down to 1.6) is provided on a best-effort basis.
Please see the Docker installation documentation for details on how to upgrade your Docker daemon.
Documentation for this image is stored in the clearlinux/ directory of the docker-library/docs GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.
If you have any problems with or questions about this image, please contact us through a GitHub issue. If the issue is related to a CVE, please check for a cve-tracker issue on the official-images repository first.
You can also reach many of the official image maintainers via the #docker-library IRC channel on Freenode.
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.