mirror of https://github.com/docker/docs.git
Update all outdated callouts
This commit is contained in:
Sarah Sanders
parent
cf534658d7
commit
be328b9958
|
|
@ -268,12 +268,12 @@ quickly see what container is your app and which container is the mysql database
|
|||
When you're ready to tear it all down, simply run `docker compose down` or hit the trash can on the Docker Desktop Dashboard
|
||||
for the entire app. The containers will stop and the network will be removed.
|
||||
|
||||
>**Warning**
|
||||
> [!WARNING]
|
||||
>
|
||||
>By default, named volumes in your compose file are not removed when you run `docker compose down`. If you want to
|
||||
> By default, named volumes in your compose file are not removed when you run `docker compose down`. If you want to
|
||||
>remove the volumes, you need to add the `--volumes` flag.
|
||||
>
|
||||
>The Docker Desktop Dashboard does not remove volumes when you delete the app stack.
|
||||
> The Docker Desktop Dashboard does not remove volumes when you delete the app stack.
|
||||
|
||||
## Summary
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
>**Important**
|
||||
>[!IMPORTANT]
|
||||
>
|
||||
>Docker Compose's integration for ECS and ACI is retiring in November 2023.
|
||||
|
|
|
|||
|
|
@ -30,9 +30,9 @@ of the convenience script:
|
|||
using the script to update an existing installation, dependencies may not be
|
||||
updated to the expected version, resulting in outdated versions.
|
||||
|
||||
> **Tip: preview script steps before running**
|
||||
> [!TIP]
|
||||
>
|
||||
> You can run the script with the `--dry-run` option to learn what steps the
|
||||
> Preview script steps before running. You can run the script with the `--dry-run` option to learn what steps the
|
||||
> script will run when invoked:
|
||||
>
|
||||
> ```console
|
||||
|
|
|
|||
|
|
@ -1004,9 +1004,9 @@ For the full change log or additional information, check the [Compose repository
|
|||
|
||||
{{< release-date date="2022-09-27" >}}
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
> - Updates on environment file syntax & interpolation: see [compose#9879](https://github.com/docker/compose/issues/9879)
|
||||
> [!NOTE]
|
||||
>
|
||||
> - Updates on environment file syntax & interpolation: see [compose#9879](https://github.com/docker/compose/issues/9879)
|
||||
> - Setting `DOCKER_HOST` via `.env` files is not supported in Compose v2
|
||||
|
||||
### Updates
|
||||
|
|
@ -1145,10 +1145,9 @@ For the full change log, check the [Compose repository 2.10.0 release page](http
|
|||
> [!IMPORTANT]
|
||||
>
|
||||
> Compose v2.9.0 contains changes to the environment variable's precedence that have since been reverted. We recommend using v2.10+ to avoid compatibility issues.
|
||||
>
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
>
|
||||
> This release reverts the breaking changes introduced in [Compose v2.8.0](#280) by [`compose-go v1.3.0`](https://github.com/compose-spec/compose-go/releases/tag/v1.3.0).
|
||||
|
||||
### Updates
|
||||
|
|
@ -1976,8 +1975,9 @@ This release contains minor improvements and bug fixes.
|
|||
|
||||
- Reverted a 1.23.0 change that appended random strings to container names
|
||||
created by `docker-compose up`, causing addressability issues.
|
||||
> [!NOTE]: Containers created by `docker-compose run` will continue to use
|
||||
randomly generated names to avoid collisions during parallel runs.
|
||||
> [!NOTE]
|
||||
>
|
||||
> Containers created by `docker-compose run` will continue to use randomly generated names to avoid collisions during parallel runs.
|
||||
|
||||
- Fixed an issue where some `dockerfile` paths would fail unexpectedly when
|
||||
attempting to build on Windows.
|
||||
|
|
@ -2981,7 +2981,10 @@ naming scheme accordingly before upgrading.
|
|||
- Containers dependencies can now be set up to wait on positive healthchecks
|
||||
when declared using `depends_on`. See the documentation for the updated
|
||||
syntax.
|
||||
**Note**: This feature will not be ported to version 3 Compose files.
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
> This feature will not be ported to version 3 Compose files.
|
||||
|
||||
- Added support for the `sysctls` parameter in service definitions
|
||||
|
||||
|
|
|
|||
|
|
@ -1926,7 +1926,9 @@ events or unexpected unmounts.
|
|||
|
||||
### Beta 18.1 Release Notes (2016-07-07 1.12.0-rc3-beta18.1)
|
||||
|
||||
>**Note**: Docker 1.12.0 RC3 release introduces a backward incompatible change from RC2. You can fix this by recreating or updating your containers.
|
||||
>[!NOTE]
|
||||
>
|
||||
> Docker 1.12.0 RC3 release introduces a backward incompatible change from RC2. You can fix this by recreating or updating your containers.
|
||||
|
||||
**Hotfix**
|
||||
|
||||
|
|
|
|||
|
|
@ -1276,9 +1276,10 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus
|
|||
TCP connection is idle for more than 5 minutes (related to
|
||||
[docker/for-mac#1374](https://github.com/docker/for-mac/issues/1374))
|
||||
|
||||
> [!NOTE]: The link above goes to Docker for Mac issues because a
|
||||
Mac user reported this problem, which applied to both Mac and Windows
|
||||
and was fixed on both.
|
||||
> [!NOTE]
|
||||
>
|
||||
> The link above goes to Docker for Mac issues because a
|
||||
Mac user reported this problem, which applied to both Mac and Windows and was fixed on both.
|
||||
|
||||
### Docker Community Edition 17.07.0-rc3-win23 Release Notes (2017-08-21 17.07.0-win23)
|
||||
|
||||
|
|
@ -2070,7 +2071,9 @@ Unreleased. See Beta 23 for changes.
|
|||
|
||||
### Beta 18.1 Release (2016-07-07 1.12.0-rc3-beta18.1)
|
||||
|
||||
>**Note**: Docker 1.12.0 RC3 release introduces a backward incompatible change from RC2. You can fix this by recreating or updating your containers.
|
||||
>[!NOTE]
|
||||
>
|
||||
> Docker 1.12.0 RC3 release introduces a backward incompatible change from RC2. You can fix this by recreating or updating your containers.
|
||||
|
||||
**Hotfix**
|
||||
|
||||
|
|
@ -2493,7 +2496,9 @@ are working on a solution.
|
|||
* Fix msi version
|
||||
* Don't truncate Toolbox link
|
||||
|
||||
>**Note**: Docker for Windows skipped from Beta 1 to Beta 5 at this point to synch up the version numbering with Docker for Mac, which went into beta cycles a little earlier.
|
||||
>[!NOTE]
|
||||
>
|
||||
> Docker for Windows skipped from Beta 1 to Beta 5 at this point to synch up the version numbering with Docker for Mac, which went into beta cycles a little earlier.
|
||||
|
||||
### Beta 1 Release (2016-03-24 1.10.6)
|
||||
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ To move the disk image file to a different location:
|
|||
|
||||
3. Select **Apply & Restart** for the changes to take effect.
|
||||
|
||||
>**Important**
|
||||
>[!IMPORTANT]
|
||||
>
|
||||
> Do not move the file directly in Finder as this can cause Docker Desktop to lose track of the file.
|
||||
|
||||
|
|
|
|||
|
|
@ -22,9 +22,9 @@ As a default, Docker uses the [`json-file` logging driver](drivers/json-file.md)
|
|||
caches container logs as JSON internally. In addition to using the logging drivers
|
||||
included with Docker, you can also implement and use [logging driver plugins](plugins.md).
|
||||
|
||||
> **Tip: use the `local` logging driver to prevent disk-exhaustion**
|
||||
> [!TIP]
|
||||
>
|
||||
> By default, no log-rotation is performed. As a result, log-files stored by the
|
||||
> Use the `local` logging driver to prevent disk-exhaustion. By default, no log-rotation is performed. As a result, log-files stored by the
|
||||
> default [`json-file` logging driver](drivers/json-file.md) logging driver can cause
|
||||
> a significant amount of disk space to be used for containers that generate much
|
||||
> output, which can lead to disk space exhaustion.
|
||||
|
|
|
|||
|
|
@ -9,9 +9,9 @@ aliases:
|
|||
- /network/links/
|
||||
---
|
||||
|
||||
>**Warning**
|
||||
>
|
||||
>The `--link` flag is a legacy feature of Docker. It may eventually
|
||||
> [!WARNING]
|
||||
>
|
||||
> The `--link` flag is a legacy feature of Docker. It may eventually
|
||||
be removed. Unless you absolutely need to continue using it, we recommend that you use
|
||||
user-defined networks to facilitate communication between two containers instead of using
|
||||
`--link`. One feature that user-defined networks do not support that you can do
|
||||
|
|
|
|||
|
|
@ -71,13 +71,9 @@ toc_max: 2
|
|||
## 17.03.0-ce
|
||||
2017-03-01
|
||||
|
||||
**IMPORTANT**: Starting with this release, Docker is on a monthly release cycle and uses a
|
||||
new YY.MM versioning scheme to reflect this. Two channels are available: monthly and quarterly.
|
||||
Any given monthly release will only receive security and bugfixes until the next monthly
|
||||
release is available. Quarterly releases receive security and bugfixes for 4 months after
|
||||
initial release. This release includes bugfixes for 1.13.1 but
|
||||
there are no major feature additions and the API version stays the same.
|
||||
Upgrading from Docker 1.13.1 to 17.03.0 is expected to be simple and low-risk.
|
||||
>[!IMPORTANT]
|
||||
>
|
||||
> Starting with this release, Docker is on a monthly release cycle and uses a new YY.MM versioning scheme to reflect this. Two channels are available: monthly and quarterly. Any given monthly release will only receive security and bugfixes until the next monthly release is available. Quarterly releases receive security and bugfixes for 4 months after initial release. This release includes bugfixes for 1.13.1 but there are no major feature additions and the API version stays the same. Upgrading from Docker 1.13.1 to 17.03.0 is expected to be simple and low-risk.
|
||||
|
||||
### Client
|
||||
|
||||
|
|
|
|||
|
|
@ -399,15 +399,9 @@ to learn how to use the `docker scan` command to check if images are vulnerable.
|
|||
## 20.10.11
|
||||
2021-11-17
|
||||
|
||||
> **IMPORTANT**
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Due to [net/http changes](https://github.com/golang/go/issues/40909) in [Go 1.16](https://golang.org/doc/go1.16#net/http),
|
||||
> HTTP proxies configured through the `$HTTP_PROXY` environment variable are no
|
||||
> longer used for TLS (`https://`) connections. Make sure you also set an `$HTTPS_PROXY`
|
||||
> environment variable for handling requests to `https://` URLs.
|
||||
>
|
||||
> Refer to [Configure the daemon to use a proxy](/manuals/engine/daemon/proxy.md)
|
||||
> to learn how to configure the Docker Daemon to use a proxy server.
|
||||
> Due to [net/http changes](https://github.com/golang/go/issues/40909) in [Go 1.16](https://golang.org/doc/go1.16#net/http), HTTP proxies configured through the `$HTTP_PROXY` environment variable are no longer used for TLS (`https://`) connections. Make sure you also set an `$HTTPS_PROXY` environment variable for handling requests to `https://` URLs. Refer to [Configure the daemon to use a proxy](/manuals/engine/daemon/proxy.md) to learn how to configure the Docker Daemon to use a proxy server.
|
||||
|
||||
|
||||
### Distribution
|
||||
|
|
@ -428,15 +422,9 @@ to learn how to use the `docker scan` command to check if images are vulnerable.
|
|||
## 20.10.10
|
||||
2021-10-25
|
||||
|
||||
> **IMPORTANT**
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Due to [net/http changes](https://github.com/golang/go/issues/40909) in [Go 1.16](https://golang.org/doc/go1.16#net/http),
|
||||
> HTTP proxies configured through the `$HTTP_PROXY` environment variable are no
|
||||
> longer used for TLS (`https://`) connections. Make sure you also set an `$HTTPS_PROXY`
|
||||
> environment variable for handling requests to `https://` URLs.
|
||||
>
|
||||
> Refer to the [HTTP/HTTPS proxy section](/manuals/engine/daemon/proxy.md)
|
||||
> to learn how to configure the Docker Daemon to use a proxy server.
|
||||
> Due to [net/http changes](https://github.com/golang/go/issues/40909) in [Go 1.16](https://golang.org/doc/go1.16#net/http), HTTP proxies configured through the `$HTTP_PROXY` environment variable are no longer used for TLS (`https://`) connections. Make sure you also set an `$HTTPS_PROXY` environment variable for handling requests to `https://` URLs. Refer to the [HTTP/HTTPS proxy section](/manuals/engine/daemon/proxy.md) to learn how to configure the Docker Daemon to use a proxy server.
|
||||
|
||||
|
||||
### Builder
|
||||
|
|
@ -468,15 +456,9 @@ to learn how to use the `docker scan` command to check if images are vulnerable.
|
|||
This release is a security release with security fixes in the CLI, runtime, as
|
||||
well as updated versions of the containerd.io package.
|
||||
|
||||
> **IMPORTANT**
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Due to [net/http changes](https://github.com/golang/go/issues/40909) in [Go 1.16](https://golang.org/doc/go1.16#net/http),
|
||||
> HTTP proxies configured through the `$HTTP_PROXY` environment variable are no
|
||||
> longer used for TLS (`https://`) connections. Make sure you also set an `$HTTPS_PROXY`
|
||||
> environment variable for handling requests to `https://` URLs.
|
||||
>
|
||||
> Refer to the [HTTP/HTTPS proxy section](/manuals/engine/daemon/proxy.md)
|
||||
> to learn how to configure the Docker Daemon to use a proxy server.
|
||||
> Due to [net/http changes](https://github.com/golang/go/issues/40909) in [Go 1.16](https://golang.org/doc/go1.16#net/http), HTTP proxies configured through the `$HTTP_PROXY` environment variable are no longer used for TLS (`https://`) connections. Make sure you also set an `$HTTPS_PROXY` environment variable for handling requests to `https://` URLs. Refer to the [HTTP/HTTPS proxy section](/manuals/engine/daemon/proxy.md) to learn how to configure the Docker Daemon to use a proxy server.
|
||||
|
||||
### Client
|
||||
|
||||
|
|
@ -512,15 +494,9 @@ well as updated versions of the containerd.io package.
|
|||
## 20.10.8
|
||||
2021-08-03
|
||||
|
||||
> **IMPORTANT**
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Due to [net/http changes](https://github.com/golang/go/issues/40909) in [Go 1.16](https://golang.org/doc/go1.16#net/http),
|
||||
> HTTP proxies configured through the `$HTTP_PROXY` environment variable are no
|
||||
> longer used for TLS (`https://`) connections. Make sure you also set an `$HTTPS_PROXY`
|
||||
> environment variable for handling requests to `https://` URLs.
|
||||
>
|
||||
> Refer to the [HTTP/HTTPS proxy section](/manuals/engine/daemon/proxy.md)
|
||||
> to learn how to configure the Docker Daemon to use a proxy server.
|
||||
> Due to [net/http changes](https://github.com/golang/go/issues/40909) in [Go 1.16](https://golang.org/doc/go1.16#net/http), HTTP proxies configured through the `$HTTP_PROXY` environment variable are no longer used for TLS (`https://`) connections. Make sure you also set an `$HTTPS_PROXY` environment variable for handling requests to `https://` URLs. Refer to the [HTTP/HTTPS proxy section](/manuals/engine/daemon/proxy.md) to learn how to configure the Docker Daemon to use a proxy server.
|
||||
|
||||
### Deprecation
|
||||
|
||||
|
|
|
|||
|
|
@ -16,15 +16,13 @@ aliases:
|
|||
|
||||
## 1.13.1 (2017-02-08)
|
||||
|
||||
**Important**: On Linux distributions where `devicemapper` was the default storage driver,
|
||||
the `overlay2`, or `overlay` is now used by default (if the kernel supports it).
|
||||
To use devicemapper, you can manually configure the storage driver to use through
|
||||
the `--storage-driver` daemon option, or by setting "storage-driver" in the `daemon.json`
|
||||
configuration file.
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> On Linux distributions where `devicemapper` was the default storage driver, the `overlay2`, or `overlay` is now used by default (if the kernel supports it). To use devicemapper, you can manually configure the storage driver to use through the `--storage-driver` daemon option, or by setting "storage-driver" in the `daemon.json` configuration file.
|
||||
|
||||
**Important**: In Docker 1.13, the managed plugin api changed, as compared to the experimental
|
||||
version introduced in Docker 1.12. You must **uninstall** plugins which you installed with Docker 1.12
|
||||
_before_ upgrading to Docker 1.13. You can uninstall plugins using the `docker plugin rm` command.
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> In Docker 1.13, the managed plugin api changed, as compared to the experimental version introduced in Docker 1.12. You must **uninstall** plugins which you installed with Docker 1.12 _before_ upgrading to Docker 1.13. You can uninstall plugins using the `docker plugin rm` command.
|
||||
|
||||
If you have already upgraded to Docker 1.13 without uninstalling
|
||||
previously-installed plugins, you may see this message when the Docker daemon
|
||||
|
|
@ -66,15 +64,13 @@ To manually remove all plugins and resolve this problem, take the following step
|
|||
|
||||
## 1.13.0 (2017-01-18)
|
||||
|
||||
**Important**: On Linux distributions where `devicemapper` was the default storage driver,
|
||||
the `overlay2`, or `overlay` is now used by default (if the kernel supports it).
|
||||
To use devicemapper, you can manually configure the storage driver to use through
|
||||
the `--storage-driver` daemon option, or by setting "storage-driver" in the `daemon.json`
|
||||
configuration file.
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> On Linux distributions where `devicemapper` was the default storage driver, the `overlay2`, or `overlay` is now used by default (if the kernel supports it). To use devicemapper, you can manually configure the storage driver to use through the `--storage-driver` daemon option, or by setting "storage-driver" in the `daemon.json` configuration file.
|
||||
|
||||
**Important**: In Docker 1.13, the managed plugin api changed, as compared to the experimental
|
||||
version introduced in Docker 1.12. You must **uninstall** plugins which you installed with Docker 1.12
|
||||
_before_ upgrading to Docker 1.13. You can uninstall plugins using the `docker plugin rm` command.
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> In Docker 1.13, the managed plugin api changed, as compared to the experimental version introduced in Docker 1.12. You must **uninstall** plugins which you installed with Docker 1.12 _before_ upgrading to Docker 1.13. You can uninstall plugins using the `docker plugin rm` command.
|
||||
|
||||
If you have already upgraded to Docker 1.13 without uninstalling
|
||||
previously-installed plugins, you may see this message when the Docker daemon
|
||||
|
|
@ -299,16 +295,14 @@ To manually remove all plugins and resolve this problem, take the following step
|
|||
|
||||
## 1.12.6 (2017-01-10)
|
||||
|
||||
**IMPORTANT**: Docker 1.12 ships with an updated systemd unit file for rpm
|
||||
based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When
|
||||
upgrading from an older version of docker, the upgrade process may not
|
||||
automatically install the updated version of the unit file, or fail to start
|
||||
the docker service if;
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Docker 1.12 ships with an updated systemd unit file for rpm
|
||||
based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When upgrading from an older version of Docker, the upgrade process may not automatically install the updated version of the unit file, or fail to start the `docker service` if;
|
||||
> - the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
|
||||
> - a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
|
||||
|
||||
- the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
|
||||
- a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
|
||||
|
||||
Starting the docker service will produce an error:
|
||||
Starting the `docker service` will produce an error:
|
||||
|
||||
Failed to start docker.service: Unit docker.socket failed to load: No such file or directory.
|
||||
|
||||
|
|
@ -326,8 +320,9 @@ To resolve this:
|
|||
After making those changes, run `sudo systemctl daemon-reload`, and `sudo
|
||||
systemctl restart docker` to reload changes and (re)start the docker daemon.
|
||||
|
||||
**NOTE**: Docker 1.12.5 will correctly validate that either an IPv6 subnet is provided or
|
||||
that the IPAM driver can provide one when you specify the `--ipv6` option.
|
||||
> [!NOTE]
|
||||
>
|
||||
> Docker 1.12.5 will correctly validate that either an IPv6 subnet is provided or that the IPAM driver can provide one when you specify the `--ipv6` option.
|
||||
|
||||
If you are currently using the `--ipv6` option _without_ specifying the
|
||||
`--fixed-cidr-v6` option, the Docker daemon will refuse to start with the
|
||||
|
|
@ -369,16 +364,14 @@ which supports automatic allocation of IPv6 subnets.
|
|||
|
||||
## 1.12.5 (2016-12-15)
|
||||
|
||||
**IMPORTANT**: Docker 1.12 ships with an updated systemd unit file for rpm
|
||||
based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When
|
||||
upgrading from an older version of docker, the upgrade process may not
|
||||
automatically install the updated version of the unit file, or fail to start
|
||||
the docker service if;
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Docker 1.12 ships with an updated systemd unit file for rpm
|
||||
based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When upgrading from an older version of Docker, the upgrade process may not automatically install the updated version of the unit file, or fail to start the `docker service` if;
|
||||
> - the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
|
||||
> - a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
|
||||
|
||||
- the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
|
||||
- a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
|
||||
|
||||
Starting the docker service will produce an error:
|
||||
Starting the `docker service` will produce an error:
|
||||
|
||||
Failed to start docker.service: Unit docker.socket failed to load: No such file or directory.
|
||||
|
||||
|
|
@ -396,8 +389,9 @@ To resolve this:
|
|||
After making those changes, run `sudo systemctl daemon-reload`, and `sudo
|
||||
systemctl restart docker` to reload changes and (re)start the docker daemon.
|
||||
|
||||
**NOTE**: Docker 1.12.5 will correctly validate that either an IPv6 subnet is provided or
|
||||
that the IPAM driver can provide one when you specify the `--ipv6` option.
|
||||
> [!NOTE]
|
||||
>
|
||||
> Docker 1.12.5 will correctly validate that either an IPv6 subnet is provided or that the IPAM driver can provide one when you specify the `--ipv6` option.
|
||||
|
||||
If you are currently using the `--ipv6` option _without_ specifying the
|
||||
`--fixed-cidr-v6` option, the Docker daemon will refuse to start with the
|
||||
|
|
@ -447,16 +441,14 @@ which supports automatic allocation of IPv6 subnets.
|
|||
|
||||
## 1.12.4 (2016-12-12)
|
||||
|
||||
**IMPORTANT**: Docker 1.12 ships with an updated systemd unit file for rpm
|
||||
based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When
|
||||
upgrading from an older version of docker, the upgrade process may not
|
||||
automatically install the updated version of the unit file, or fail to start
|
||||
the docker service if;
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Docker 1.12 ships with an updated systemd unit file for rpm
|
||||
based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When upgrading from an older version of Docker, the upgrade process may not automatically install the updated version of the unit file, or fail to start the `docker service` if;
|
||||
> - the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
|
||||
> - a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
|
||||
|
||||
- the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
|
||||
- a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
|
||||
|
||||
Starting the docker service will produce an error:
|
||||
Starting the `docker service` will produce an error:
|
||||
|
||||
Failed to start docker.service: Unit docker.socket failed to load: No such file or directory.
|
||||
|
||||
|
|
@ -522,16 +514,14 @@ systemctl restart docker` to reload changes and (re)start the docker daemon.
|
|||
|
||||
## 1.12.3 (2016-10-26)
|
||||
|
||||
**IMPORTANT**: Docker 1.12 ships with an updated systemd unit file for rpm
|
||||
based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When
|
||||
upgrading from an older version of docker, the upgrade process may not
|
||||
automatically install the updated version of the unit file, or fail to start
|
||||
the docker service if;
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Docker 1.12 ships with an updated systemd unit file for rpm
|
||||
based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When upgrading from an older version of Docker, the upgrade process may not automatically install the updated version of the unit file, or fail to start the Docker service if;
|
||||
> - the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
|
||||
> - a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
|
||||
|
||||
- the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
|
||||
- a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
|
||||
|
||||
Starting the docker service will produce an error:
|
||||
Starting the `docker service` will produce an error:
|
||||
|
||||
Failed to start docker.service: Unit docker.socket failed to load: No such file or directory.
|
||||
|
||||
|
|
@ -589,16 +579,14 @@ systemctl restart docker` to reload changes and (re)start the docker daemon.
|
|||
|
||||
## 1.12.2 (2016-10-11)
|
||||
|
||||
**IMPORTANT**: Docker 1.12 ships with an updated systemd unit file for rpm
|
||||
based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When
|
||||
upgrading from an older version of docker, the upgrade process may not
|
||||
automatically install the updated version of the unit file, or fail to start
|
||||
the docker service if;
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Docker 1.12 ships with an updated systemd unit file for rpm
|
||||
based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When upgrading from an older version of Docker, the upgrade process may not automatically install the updated version of the unit file, or fail to start the `docker service` if;
|
||||
> - the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
|
||||
> - a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
|
||||
|
||||
- the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
|
||||
- a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
|
||||
|
||||
Starting the docker service will produce an error:
|
||||
Starting the `docker service` will produce an error:
|
||||
|
||||
Failed to start docker.service: Unit docker.socket failed to load: No such file or directory.
|
||||
|
||||
|
|
@ -663,16 +651,14 @@ systemctl restart docker` to reload changes and (re)start the docker daemon.
|
|||
|
||||
## 1.12.1 (2016-08-18)
|
||||
|
||||
**IMPORTANT**: Docker 1.12 ships with an updated systemd unit file for rpm
|
||||
based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When
|
||||
upgrading from an older version of docker, the upgrade process may not
|
||||
automatically install the updated version of the unit file, or fail to start
|
||||
the docker service if;
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Docker 1.12 ships with an updated systemd unit file for rpm
|
||||
based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When upgrading from an older version of Docker, the upgrade process may not automatically install the updated version of the unit file, or fail to start the `docker service` if;
|
||||
> - the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
|
||||
> - a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
|
||||
|
||||
- the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
|
||||
- a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
|
||||
|
||||
Starting the docker service will produce an error:
|
||||
Starting the `docker service` will produce an error:
|
||||
|
||||
Failed to start docker.service: Unit docker.socket failed to load: No such file or directory.
|
||||
|
||||
|
|
@ -755,16 +741,14 @@ systemctl restart docker` to reload changes and (re)start the docker daemon.
|
|||
## 1.12.0 (2016-07-28)
|
||||
|
||||
|
||||
**IMPORTANT**: Docker 1.12.0 ships with an updated systemd unit file for rpm
|
||||
based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When
|
||||
upgrading from an older version of docker, the upgrade process may not
|
||||
automatically install the updated version of the unit file, or fail to start
|
||||
the docker service if;
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Docker 1.12.0 ships with an updated systemd unit file for rpm
|
||||
based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When upgrading from an older version of Docker, the upgrade process may not automatically install the updated version of the unit file, or fail to start the `docker service` if;
|
||||
> - the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
|
||||
> - a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
|
||||
|
||||
- the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
|
||||
- a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
|
||||
|
||||
Starting the docker service will produce an error:
|
||||
Starting the `docker service` will produce an error:
|
||||
|
||||
Failed to start docker.service: Unit docker.socket failed to load: No such file or directory.
|
||||
|
||||
|
|
@ -782,9 +766,10 @@ To resolve this:
|
|||
After making those changes, run `sudo systemctl daemon-reload`, and `sudo
|
||||
systemctl restart docker` to reload changes and (re)start the docker daemon.
|
||||
|
||||
**IMPORTANT**: With Docker 1.12, a Linux docker installation now has two
|
||||
additional binaries; `dockerd`, and `docker-proxy`. If you have scripts for
|
||||
installing docker, make sure to update them accordingly.
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> With Docker 1.12, a Linux `docker` installation now has two
|
||||
additional binaries; `dockerd`, and `docker-proxy`. If you have scripts for installing `docker`, make sure to update them accordingly.
|
||||
|
||||
### Builder
|
||||
|
||||
|
|
@ -974,7 +959,9 @@ installing docker, make sure to update them accordingly.
|
|||
|
||||
## 1.11.0 (2016-04-13)
|
||||
|
||||
**IMPORTANT**: With Docker 1.11, a Linux docker installation is now made of 4 binaries (`docker`, [`docker-containerd`](https://github.com/docker/containerd), [`docker-containerd-shim`](https://github.com/docker/containerd) and [`docker-runc`](https://github.com/opencontainers/runc)). If you have scripts relying on docker being a single static binaries, make sure to update them. Interaction with the daemon stay the same otherwise, the usage of the other binaries should be transparent. A Windows docker installation remains a single binary, `docker.exe`.
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> With Docker 1.11, a Linux Docker installation is now made of 4 binaries (`docker`, [`docker-containerd`](https://github.com/docker/containerd), [`docker-containerd-shim`](https://github.com/docker/containerd) and [`docker-runc`](https://github.com/opencontainers/runc)). If you have scripts relying on `docker` being a single static binaries, make sure to update them. Interaction with the daemon stay the same otherwise, the usage of the other binaries should be transparent. A Windows Docker installation remains a single binary, `docker.exe`.
|
||||
|
||||
### Builder
|
||||
|
||||
|
|
@ -1223,9 +1210,11 @@ installing docker, make sure to update them accordingly.
|
|||
|
||||
## 1.10.0 (2016-02-04)
|
||||
|
||||
**IMPORTANT**: Docker 1.10 uses a new content-addressable storage for images and layers.
|
||||
A migration is performed the first time docker is run, and can take a significant amount of time depending on the number of images present.
|
||||
Refer to this page on the wiki for more information: https://github.com/docker/docker/wiki/Engine-v1.10.0-content-addressability-migration
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Docker 1.10 uses a new content-addressable storage for images and layers.
|
||||
|
||||
A migration is performed the first time `docker` is run, and can take a significant amount of time depending on the number of images present. Refer to this page on the wiki for more information: https://github.com/docker/docker/wiki/Engine-v1.10.0-content-addressability-migration
|
||||
We also released a cool migration utility that enables you to perform the migration before updating to reduce downtime.
|
||||
Engine 1.10 migrator can be found on Docker Hub: https://hub.docker.com/r/docker/v1.10-migrator/
|
||||
|
||||
|
|
|
|||
|
|
@ -834,14 +834,10 @@ storage driver.
|
|||
by thin provisioning and copy-on-write. Volumes have other benefits, such as
|
||||
allowing you to share data among containers and persisting even when no
|
||||
running container is using them.
|
||||
|
||||
- **Note**: when using `devicemapper` and the `json-file` log driver, the log
|
||||
files generated by a container are still stored in Docker's dataroot directory,
|
||||
by default `/var/lib/docker`. If your containers generate lots of log messages,
|
||||
this may lead to increased disk usage or the inability to manage your system due
|
||||
to a full disk. You can configure a
|
||||
[log driver](/manuals/engine/logging/configure.md) to store your container
|
||||
logs externally.
|
||||
|
||||
> [!NOTE] vf
|
||||
>
|
||||
> When using `devicemapper` and the `json-file` log driver, the log files generated by a container are still stored in Docker's dataroot directory, by default `/var/lib/docker`. If your containers generate lots of log messages, this may lead to increased disk usage or the inability to manage your system due to a full disk. You can configure a [log driver](/manuals/engine/logging/configure.md) to store your container logs externally.
|
||||
|
||||
## Related Information
|
||||
|
||||
|
|
|
|||
|
|
@ -46,10 +46,9 @@ manager nodes.
|
|||
* An odd number `N` of manager nodes in the cluster tolerates the loss of at most `(N-1)/2` managers.
|
||||
Docker recommends a maximum of seven manager nodes for a swarm.
|
||||
|
||||
>**Important**
|
||||
>[!IMPORTANT]
|
||||
>
|
||||
> Adding more managers does NOT mean increased
|
||||
> scalability or higher performance. In general, the opposite is true.
|
||||
> Adding more managers does NOT mean increased scalability or higher performance. In general, the opposite is true.
|
||||
|
||||
## Worker nodes
|
||||
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ the Docker CLI to see details about the service running in the swarm.
|
|||
Endpoint Mode: vip
|
||||
```
|
||||
|
||||
>**Tip**
|
||||
> [!TIP]
|
||||
>
|
||||
> To return the service details in json format, run the same command
|
||||
without the `--pretty` flag.
|
||||
|
|
@ -110,7 +110,7 @@ the Docker CLI to see details about the service running in the swarm.
|
|||
4. Run `docker ps` on the node where the task is running to see details about
|
||||
the container for the task.
|
||||
|
||||
>**Tip**
|
||||
> [!TIP]
|
||||
>
|
||||
> If `helloworld` is running on a node other than your manager node,
|
||||
you must ssh to that node.
|
||||
|
|
|
|||
|
|
@ -234,9 +234,10 @@ The following `admin-settings.json` code and table provides an example of the re
|
|||
For settings to take effect:
|
||||
- On a new install, developers need to launch Docker Desktop and authenticate to their organization.
|
||||
- On an existing install, developers need to quit Docker Desktop through the Docker menu, and then relaunch Docker Desktop. If they are already signed in, they don't need to sign in again for the changes to take effect.
|
||||
>**Important**
|
||||
|
||||
>[!IMPORTANT]
|
||||
>
|
||||
>Selecting **Restart** from the Docker menu isn't enough as it only restarts some components of Docker Desktop.
|
||||
> Selecting **Restart** from the Docker menu isn't enough as it only restarts some components of Docker Desktop.
|
||||
|
||||
Docker doesn't automatically mandate that developers re-launch and sign in once a change has been made so as not to disrupt your developers' workflow.
|
||||
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ The `window.ddClient.backend` object can be used to communicate with the backend
|
|||
the extension metadata.
|
||||
The client is already connected to the backend.
|
||||
|
||||
>**Warning**
|
||||
> [!WARNING]
|
||||
>
|
||||
> It will be removed in a future version. Use [extension](DockerDesktopClient.md#extension) instead.
|
||||
|
||||
|
|
@ -88,7 +88,7 @@ You can use the option `{"all": true}` to list all the running and stopped conta
|
|||
const containers = await window.ddClient.listContainers();
|
||||
```
|
||||
|
||||
>**Warning**
|
||||
> [!WARNING]
|
||||
>
|
||||
> It will be removed in a future version. Use [listContainers](Docker.md#listcontainers) instead.
|
||||
|
||||
|
|
@ -121,7 +121,7 @@ const images = await window.ddClient.listImages();
|
|||
```
|
||||
|
||||
> [!WARNING]
|
||||
>
|
||||
>
|
||||
> It will be removed in a future version. Use [listImages](Docker.md#listimages) instead.
|
||||
|
||||
#### Parameters
|
||||
|
|
@ -152,7 +152,7 @@ window.ddClient.navigateToContainers();
|
|||
```
|
||||
|
||||
> [!WARNING]
|
||||
>
|
||||
>
|
||||
> It will be removed in a future version. Use [viewContainers](NavigationIntents.md#viewcontainers) instead.
|
||||
|
||||
#### Returns
|
||||
|
|
@ -269,7 +269,7 @@ await window.ddClient.navigateToContainerStats(id);
|
|||
```
|
||||
|
||||
> [!WARNING]
|
||||
>
|
||||
>
|
||||
> It will be removed in a future version.
|
||||
|
||||
#### Parameters
|
||||
|
|
@ -412,7 +412,7 @@ window.ddClient.navigateToDevEnvironments();
|
|||
```
|
||||
|
||||
> [!WARNING]
|
||||
>
|
||||
>
|
||||
> It will be removed in a future version. Use [viewDevEnvironments](NavigationIntents.md#viewdevenvironments) instead.
|
||||
|
||||
#### Returns
|
||||
|
|
@ -440,7 +440,7 @@ window.ddClient.execHostCmd(`cliShippedOnHost xxx`).then((cmdResult: any) => {
|
|||
```
|
||||
|
||||
> [!WARNING]
|
||||
>
|
||||
>
|
||||
> It will be removed in a future version. Use [exec](ExtensionCli.md#exec) instead.
|
||||
|
||||
#### Parameters
|
||||
|
|
@ -590,7 +590,7 @@ Opens an external URL with the system default browser.
|
|||
window.ddClient.openExternal("https://docker.com");
|
||||
```
|
||||
|
||||
**Warning**
|
||||
> [!WARNING]
|
||||
>
|
||||
> It will be removed in a future version. Use [openExternal](Host.md#openexternal) instead.
|
||||
|
||||
|
|
@ -682,7 +682,7 @@ Display a toast message of type error.
|
|||
window.ddClient.toastError("message");
|
||||
```
|
||||
|
||||
>**Warning**
|
||||
> [!WARNING]
|
||||
>
|
||||
> It will be removed in a future version. Use [error](Toast.md#error) instead.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue