mirror of https://github.com/docker/docs.git
Updates to Engine overview (#10073)
* update engine overview * address review comments * fix urls
This commit is contained in:
Usha Mandya
GitHub
parent
43658593d7
commit
7044283cc0
204
install/index.md
204
install/index.md
|
|
@ -17,121 +17,36 @@ redirect_from:
|
|||
- /engine/installation/
|
||||
- /en/latest/installation/
|
||||
- /linux/
|
||||
toc_max: 2
|
||||
---
|
||||
|
||||
Docker Engine - Community is ideal for developers and small
|
||||
teams looking to get started with Docker and experimenting with container-based
|
||||
apps. Docker Engine - Community has three types of update channels, **stable**, **test**, and **nightly**:
|
||||
Docker Engine is an open source containerization technology for building and
|
||||
containerizing your applications. Docker Engine acts as a client-server
|
||||
application with:
|
||||
* A server with a long-running daemon process [`dockerd`](/engine/reference/commandline/dockerd/).
|
||||
* APIs which specify interfaces that programs can use to talk to and
|
||||
instruct the Docker daemon.
|
||||
* A command line interface (CLI) client [`docker`](/engine/reference/commandline/cli/).
|
||||
|
||||
The CLI uses Docker APIs to control or interact with the Docker daemon
|
||||
through scripting or direct CLI commands. Many other Docker applications use the
|
||||
underlying API and CLI. The daemon creates and manage Docker objects, such as
|
||||
images, containers, networks, and volumes.
|
||||
|
||||
Docker Engine 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.
|
||||
|
||||
## Releases
|
||||
For more information, see [Release channels](#release-channels).
|
||||
|
||||
For the Docker Engine - Community, the open
|
||||
repositories [Docker Engine](https://github.com/docker/engine) and
|
||||
[Docker Client](https://github.com/docker/cli) apply.
|
||||
## Supported platforms
|
||||
|
||||
Releases of Docker Engine and Docker Client for general availability
|
||||
are versioned using dotted triples. The components of this triple
|
||||
are `YY.mm.<patch>` 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 Engine - Community binaries for a release are available on [download.docker.com](https://download.docker.com/)
|
||||
as packages for the supported operating systems. Docker Engine - Enterprise binaries are
|
||||
available on the [Docker Hub](https://hub.docker.com/) 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-20180720214833-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 `<year>.<month>`, 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.
|
||||
|
||||
## Next release
|
||||
|
||||
The activity for upcoming year-month releases is tracked in the milestones
|
||||
of the repository.
|
||||
|
||||
## Support
|
||||
|
||||
Docker Engine - Community releases of a year-month branch are supported with patches
|
||||
as needed for 7 months after the first year-month general availability
|
||||
release. Docker Engine - Enterprise releases are supported for 24 months after the first
|
||||
year-month general availability release.
|
||||
|
||||
This means bug reports and backports to release branches are assessed
|
||||
until the end-of-life date.
|
||||
|
||||
After the year-month branch has reached end-of-life, the branch may be
|
||||
deleted from the repository.
|
||||
|
||||
### Reporting security issues
|
||||
|
||||
The Docker maintainers take security seriously. If you discover a security
|
||||
issue, please bring it to their attention right away!
|
||||
|
||||
Please DO NOT file a public issue; instead send your report privately
|
||||
to security@docker.com.
|
||||
|
||||
Security reports are greatly appreciated, and Docker will publicly thank you
|
||||
for it. Docker also likes to send gifts — if you're into swag, make sure to
|
||||
let us know. Docker currently does not offer a paid security bounty program
|
||||
but are not ruling it out in the future.
|
||||
|
||||
### Supported platforms
|
||||
|
||||
Docker Engine - Community is available on multiple platforms. Use the following tables
|
||||
to choose the best installation path for you.
|
||||
Docker Engine is available on a variety of Linux platforms, [Mac](/docker-for-mac/install/)
|
||||
and [Windows](/docker-for-windows/install/) through Docker Desktop, Windows
|
||||
Server, and as a static binary installation. Find your preferred operating
|
||||
system below.
|
||||
|
||||
#### Desktop
|
||||
|
||||
|
|
@ -154,6 +69,63 @@ to choose the best installation path for you.
|
|||
| [Fedora]({{ install-prefix-ce }}/fedora/) | [{{ green-check }}]({{ install-prefix-ce }}/fedora/) | | [{{ green-check }}]({{ install-prefix-ce }}/fedora/) | | |
|
||||
| [Ubuntu]({{ install-prefix-ce }}/ubuntu/) | [{{ green-check }}]({{ install-prefix-ce }}/ubuntu/) | [{{ green-check }}]({{ install-prefix-ce }}/ubuntu/) | [{{ green-check }}]({{ install-prefix-ce }}/ubuntu/) | [{{ green-check }}]({{ install-prefix-ce }}/ubuntu/) | [{{ green-check }}]({{ install-prefix-ce }}/ubuntu/) |
|
||||
|
||||
## Release channels
|
||||
|
||||
### Stable
|
||||
|
||||
Year-month releases are made from a release branch diverged from the master
|
||||
branch. The branch is created with format `<year>.<month>`, 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.
|
||||
|
||||
### Test
|
||||
|
||||
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.
|
||||
|
||||
> **Note:**
|
||||
> 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`.
|
||||
|
||||
### Nightly
|
||||
|
||||
Nightly builds give you the latest builds of work in progress for the next major
|
||||
release. They are created once per day from the master branch with the version
|
||||
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-20180720214833-f61e0f7`.
|
||||
|
||||
These builds allow for testing from the latest code on the master branch.
|
||||
|
||||
> **Note:**
|
||||
> No qualifications or guarantees are made for the nightly builds.
|
||||
|
||||
The release channel for these builds is called `nightly`.
|
||||
|
||||
## Support
|
||||
|
||||
Docker Engine releases of a year-month branch are supported with patches as needed for 7 months after the first year-month general availability
|
||||
release.
|
||||
|
||||
This means bug reports and backports to release branches are assessed
|
||||
until the end-of-life date.
|
||||
|
||||
After the year-month branch has reached end-of-life, the branch may be
|
||||
deleted from the repository.
|
||||
|
||||
### Backporting
|
||||
|
||||
Backports to the Docker products are prioritized by the Docker company. A
|
||||
|
|
@ -168,16 +140,22 @@ or by adding a comment to the PR.
|
|||
|
||||
Patch releases are always backward compatible with its year-month version.
|
||||
|
||||
## Not covered
|
||||
### Licensing
|
||||
|
||||
As a general rule, anything not mentioned in this document may change in any release.
|
||||
Docker is licensed under the Apache License, Version 2.0. See
|
||||
[LICENSE](https://github.com/moby/moby/blob/master/LICENSE) for the full
|
||||
license text.
|
||||
|
||||
## Exceptions
|
||||
## Reporting security issues
|
||||
|
||||
Exceptions are made in the interest of __security patches__. If a break
|
||||
in release procedure or product functionality is required, it will
|
||||
be communicated clearly, and the solution will be considered against
|
||||
total impact.
|
||||
The Docker maintainers take security seriously. If you discover a security
|
||||
issue, please bring it to their attention right away!
|
||||
|
||||
Please DO NOT file a public issue; instead send your report privately
|
||||
to security@docker.com.
|
||||
|
||||
Security reports are greatly appreciated, and Docker will publicly thank you
|
||||
for it.
|
||||
|
||||
## Get started
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue