About Docker CE Estimated reading time: 7 minutes Docker Community Edition (CE) is ideal for developers and small teams looking to get started with Docker and experimenting with container-based apps. Docker CE has three types of update channels, stable, test, and nightly: • Stable gives you latest releases for general availability. • Test gives pre-releases that are ready for testing before general availability. • Nightly gives you latest builds of work in progress for the next major release. For more information about Docker CE, see. Releases For the Docker CE engine, the open repositories and apply. Releases of Docker Engine and Docker Client for general availability are versioned using dotted triples. Join GitHub today. GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together. The components of this triple are YY.mm. Where the YY.mm component is referred to as the year-month release. The version numbering format is chosen to illustrate cadence and does not guarantee SemVer, but the desired date for general availability. The version number may have additional information, such as beta and release candidate qualifications. Such releases are considered “pre-releases”. The cadence of the year-month releases is every 6 months starting with the 18.09 release. ![]() The patch releases for a year-month release take place as needed to address bug fixes during its support cycle. Docker CE binaries for a release are available on as packages for the supported operating systems. Docker EE binaries are available on the for the supported operating systems. The release channels are available for each of the year-month releases and allow users to “pin” on a year-month release of choice. The release channel also receives patch releases when they become available. Nightly builds Nightly builds are created once per day from the master branch. The version number for nightly builds take the format. 0.0.0-YYYYmmddHHMMSS-abcdefabcdef where the time is the commit time in UTC and the final suffix is the prefix of the commit hash, for example 0.0.0-4833-f61e0f7. These builds allow for testing from the latest code on the master branch. No qualifications or guarantees are made for the nightly builds. The release channel for these builds is called nightly. Pre-releases In preparation for a new year-month release, a branch is created from the master branch with format YY.mm when the milestones desired by Docker for the release have achieved feature-complete. Pre-releases such as betas and release candidates are conducted from their respective release branches. Patch releases and the corresponding pre-releases are performed from within the corresponding release branch. While pre-releases are done to assist in the stabilization process, no guarantees are provided. Binaries built for pre-releases are available in the test channel for the targeted year-month release using the naming format test-YY.mm, for example test-18.09. General availability Year-month releases are made from a release branch diverged from the master branch. ![]() The branch is created with format., for example 18.09. The year-month name indicates the earliest possible calendar month to expect the release to be generally available. All further patch releases are performed from that branch. For example, once v18.09.0 is released, all subsequent patch releases are built from the 18.09 branch. Binaries built from this releases are available in the stable channel stable-YY.mm, for example stable-18.09, as well as the corresponding test channel. Relationship between CE and EE code For a given year-month release, Docker releases both CE and EE variants concurrently. EE is a superset of the code delivered in CE.
0 Комментарии
Оставить ответ. |
АвторНапишите что-нибудь о себе. Не надо ничего особенного, просто общие данные. Архивы
Март 2019
Категории |