Guest24897
/
DockerCLI
mirror of https://github.com/docker/cli.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
DockerCLI/docs/deprecated.md

1066 lines
54 KiB
Markdown
Raw Normal View History

Convert Markdown frontmatter to YAML Some frontmatter such as the weights, menu stuff, etc is no longer used 'draft=true' becomes 'published: false' Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-14 18:30:36 -04:00
---
aliases: ["/engine/misc/deprecated/"]
description: "Deprecated Features."
fix frontmatter keywords value type (string, instead of []string) Signed-off-by: Gaetan de Villele <gdevillele@gmail.com>
2016-11-03 17:21:33 -04:00
keywords: "docker, documentation, about, technology, deprecate"
Convert Markdown frontmatter to YAML Some frontmatter such as the weights, menu stuff, etc is no longer used 'draft=true' becomes 'published: false' Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-14 18:30:36 -04:00
---
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
Fix GitHub spelling Signed-off-by: Frieder Bluemle <frieder.bluemle@gmail.com>
2017-10-04 13:03:55 -04:00
<!-- This file is maintained within the docker/cli GitHub
Fix repo references in docs Since CLI was moved to a separate repo, these references are incorrect. Fixed with the help of sed script, verified manually. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
2017-07-28 13:28:23 -04:00
repository at https://github.com/docker/cli/. Make all
Sync docker/docker refs with files mistakenly edited in docker.github.io repo Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-19 13:25:45 -04:00
pull requests against that repo. If you see this file in
another repository, consider it read-only there, as it will
periodically be overwritten by the definitive file. Pull
requests which include edits to this file in other repositories
will be rejected.
-->
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
# Deprecated Engine Features
Include deprecation policy on deprecated features page This section was included on a page on docs.docker.com, but not linked in the navigation. Putting the section on the deprecated features page to be sure they can be found together. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-03-20 05:40:56 -04:00
This page provides an overview of features that are deprecated in Engine. Changes
in packaging, and supported (Linux) distributions are not included. To learn
about end of support for Linux distributions, refer to the
[release notes](https://docs.docker.com/engine/release-notes/).
## Feature Deprecation Policy
As changes are made to Docker there may be times when existing features need to
be removed or replaced with newer features. Before an existing feature is removed
it is labeled as "deprecated" within the documentation and remains in Docker for
Update deprecation policy to 1 stable release The deprecation policy was written when we had monthly releases (edge+stable), and stable releases were released every 3 months. The release cadence has changed to be longer than 3 months for stable releases, so adjusting the policy accordingly. Note that the policy continues to be "at least x releases", so even though we _can_ remove a feature after one release, it does not mean we _must_ remove it: announcing deprecations early helps users migrate away from features we do not intent to support in future. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-03-20 05:43:52 -04:00
at least one stable release unless specified explicitly otherwise. After that time
Include deprecation policy on deprecated features page This section was included on a page on docs.docker.com, but not linked in the navigation. Putting the section on the deprecated features page to be sure they can be found together. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-03-20 05:40:56 -04:00
it may be removed.
Users are expected to take note of the list of deprecated features each release
and plan their migration away from those features, and (if applicable) towards
the replacement features as soon as possible.
## Deprecated Engine Features
docs: add status table to "deprecated.md" Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 08:41:38 -05:00
The table below provides an overview of the current status of deprecated features:
- **Deprecated**: the feature is marked "deprecated" and should no longer be used.
The feature may be removed, disabled, or change behavior in a future release.
The _"Deprecated"_ column contains the release in which the feature was marked
deprecated, whereas the _"Remove"_ column contains a tentative release in which
the feature is to be removed. If no release is included in the _"Remove"_ column,
the release is yet to be decided on.
- **Removed**: the feature was removed, disabled, or hidden. Refer to the linked
section for details. Some features are "soft" deprecated, which means that they
remain functional for backward compatibility, and to allow users to migrate to
alternatives. In such cases, a warning may be printed, and users should not rely
on this feature.
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
| Status | Feature | Deprecated | Remove |
|------------|------------------------------------------------------------------------------------------------------------------------------------|------------|--------|
docs: deprecate TCP connection without TLS Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
2024-03-08 08:50:15 -05:00
| Deprecated | [Unauthenticated TCP connections](#unauthenticated-tcp-connections) | v26.0 | v27.0 |
deprecate old API versions (1.23 and lower) The Docker daemon provides a versioned API for backward compatibility with old clients. Docker clients can perform API-version negotiation to select the most recent API version supported by the daemon (downgrading to and older version of the API when necessary). API version negotiation was introduced in Docker v1.12.0 (API 1.24), and clients before that used a fixed API version. Docker Engine versions through v25.0 provide support for all [API versions](https://docs.docker.com/engine/api/#api-version-matrix) included in stable releases for a given platform. For Docker daemons on Linux, the earliest supported API version is 1.12 (corresponding with Docker Engine v1.0.0), whereas for Docker daemons on Windows, the earliest supported API version is 1.24 (corresponding with Docker Engine v1.12.0). Support for legacy API versions (providing old API versions on current versions of the Docker Engine) is primarily intended to provide compatibility with recent, but still supported versions of the client, which is a common scenario (the Docker daemon may be updated to the latest release, but not all clients may be up-to-date or vice versa). Support for API versions before that (API versions provided by EOL versions of the Docker Daemon) is provided on a "best effort" basis. Use of old API versions is very rare, and support for legacy API versions involves significant complexity (Docker 1.0.0 having been released 10 years ago). Because of this, we'll start deprecating support for legacy API versions. Docker Engine v25.0 by default disables API version older than 1.24 (aligning the minimum supported API version between Linux and Windows daemons). When connecting with a client that uses an API version version older than 1.24, the daemon returns an error. The following example configures the docker CLI to use API version 1.23, which produces an error: DOCKER_API_VERSION=1.23 docker version Error response from daemon: client version 1.23 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version An environment variable (`DOCKER_MIN_API_VERSION`) is introduced that allows re-enabling older API versions in the daemon. This environment variable must be set in the daemon's environment (for example, through a [systemd override file](https://docs.docker.com/config/daemon/systemd/)), and the specified API version must be supported by the daemon (`1.12` or higher on Linux, or `1.24` or higher on Windows). Support for API versions lower than `1.24` will be permanently removed in Docker Engine v26, and the minimum supported API version will be incrementally raised in releases following that. We do not recommend depending on the `DOCKER_MIN_API_VERSION` environment variable other than for exceptional cases where it's not possible to update old clients, and those clients must be supported. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-12-08 20:24:30 -05:00
| Deprecated | [Deprecate legacy API versions](#deprecate-legacy-api-versions) | v25.0 | v26.0 |
docs/deprecated: update status of short cid alias deprecation Starting with API v1.45, the container short ID is removed from the container Aliases. Signed-off-by: Albin Kerouanton <albinker@gmail.com>
2024-03-18 05:39:14 -04:00
| Removed | [Container short ID in network Aliases field](#container-short-id-in-network-aliases-field) | v25.0 | v26.0 |
deprecated: fix anchor and add missing version Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-12-20 17:14:51 -05:00
| Deprecated | [IsAutomated field, and "is-automated" filter on docker search](#isautomated-field-and-is-automated-filter-on-docker-search) | v25.0 | v26.0 |
docs/deprecated: mark logentries logging-driver as "removed" This driver has been deprecated and removed because the service is no longer operational. Update the deprecated features docs to mention it's been fully removed in Docker v25.0. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-12-13 07:19:33 -05:00
| Removed | [logentries logging driver](#logentries-logging-driver) | v24.0 | v25.0 |
docs/deprecated: update "oom-score-adjust" status for daemon Using this option on the daemon will now produce an error (flag will be removed entirely in v26.0). Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-12-20 17:25:56 -05:00
| Removed | [OOM-score adjust for the daemon](#oom-score-adjust-for-the-daemon) | v24.0 | v25.0 |
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
| Removed | [Buildkit build information](#buildkit-build-information) | v23.0 | v24.0 |
| Deprecated | [Legacy builder for Linux images](#legacy-builder-for-linux-images) | v23.0 | - |
| Deprecated | [Legacy builder fallback](#legacy-builder-fallback) | v23.0 | - |
| Removed | [Btrfs storage driver on CentOS 7 and RHEL 7](#btrfs-storage-driver-on-centos-7-and-rhel-7) | v20.10 | v23.0 |
| Removed | [Support for encrypted TLS private keys](#support-for-encrypted-tls-private-keys) | v20.10 | v23.0 |
| Removed | [Kubernetes stack and context support](#kubernetes-stack-and-context-support) | v20.10 | v23.0 |
| Deprecated | [Pulling images from non-compliant image registries](#pulling-images-from-non-compliant-image-registries) | v20.10 | - |
| Removed | [Linux containers on Windows (LCOW)](#linux-containers-on-windows-lcow-experimental) | v20.10 | v23.0 |
| Deprecated | [BLKIO weight options with cgroups v1](#blkio-weight-options-with-cgroups-v1) | v20.10 | - |
| Removed | [Kernel memory limit](#kernel-memory-limit) | v20.10 | v23.0 |
| Removed | [Classic Swarm and overlay networks using external key/value stores](#classic-swarm-and-overlay-networks-using-cluster-store) | v20.10 | v23.0 |
| Removed | [Support for the legacy `~/.dockercfg` configuration file for authentication](#support-for-legacy-dockercfg-configuration-files) | v20.10 | v23.0 |
| Deprecated | [CLI plugins support](#cli-plugins-support) | v20.10 | - |
| Deprecated | [Dockerfile legacy `ENV name value` syntax](#dockerfile-legacy-env-name-value-syntax) | v20.10 | - |
| Removed | [`docker build --stream` flag (experimental)](#docker-build---stream-flag-experimental) | v20.10 | v20.10 |
| Deprecated | [`fluentd-async-connect` log opt](#fluentd-async-connect-log-opt) | v20.10 | - |
| Removed | [Configuration options for experimental CLI features](#configuration-options-for-experimental-cli-features) | v19.03 | v23.0 |
deprecate legacy image formats Mark pulling legacy image formats as deprecated, and describe the DOCKER_ENABLE_DEPRECATED_PULL_SCHEMA_1_IMAGE environment variable. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2024-03-04 03:14:25 -05:00
| Deprecated | [Pushing and pulling with image manifest v2 schema 1](#pushing-and-pulling-with-image-manifest-v2-schema-1) | v19.03 | v27.0 |
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
| Removed | [`docker engine` subcommands](#docker-engine-subcommands) | v19.03 | v20.10 |
| Removed | [Top-level `docker deploy` subcommand (experimental)](#top-level-docker-deploy-subcommand-experimental) | v19.03 | v20.10 |
| Removed | [`docker stack deploy` using "dab" files (experimental)](#docker-stack-deploy-using-dab-files-experimental) | v19.03 | v20.10 |
| Removed | [Support for the `overlay2.override_kernel_check` storage option](#support-for-the-overlay2override_kernel_check-storage-option) | v19.03 | v24.0 |
| Removed | [AuFS storage driver](#aufs-storage-driver) | v19.03 | v24.0 |
| Removed | [Legacy "overlay" storage driver](#legacy-overlay-storage-driver) | v18.09 | v24.0 |
docs/deprecate.md: add version for devicemapper removal to table commit 5d6612798a195b30edf4244ff06f18e80b1167d5 updated the deprecation status for devicemapper to "removed", but forgot to update the status in the table. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-12-07 16:30:28 -05:00
| Removed | [Device mapper storage driver](#device-mapper-storage-driver) | v18.09 | v25.0 |
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
| Removed | [Use of reserved namespaces in engine labels](#use-of-reserved-namespaces-in-engine-labels) | v18.06 | v20.10 |
| Removed | [`--disable-legacy-registry` override daemon option](#--disable-legacy-registry-override-daemon-option) | v17.12 | v19.03 |
| Removed | [Interacting with V1 registries](#interacting-with-v1-registries) | v17.06 | v17.12 |
| Removed | [Asynchronous `service create` and `service update` as default](#asynchronous-service-create-and-service-update-as-default) | v17.05 | v17.10 |
docs/deprecated.md: add version for "-g" / "--graph" removal commit 304c100ed250756a64009605d7b5fc7674441934 updated the deprecation status for these options, but forgot to update the status in the table. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-12-07 16:34:38 -05:00
| Removed | [`-g` and `--graph` flags on `dockerd`](#-g-and---graph-flags-on-dockerd) | v17.05 | v23.0 |
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
| Deprecated | [Top-level network properties in NetworkSettings](#top-level-network-properties-in-networksettings) | v1.13 | v17.12 |
| Removed | [`filter` param for `/images/json` endpoint](#filter-param-for-imagesjson-endpoint) | v1.13 | v20.10 |
| Removed | [`repository:shortid` image references](#repositoryshortid-image-references) | v1.13 | v17.12 |
| Removed | [`docker daemon` subcommand](#docker-daemon-subcommand) | v1.13 | v17.12 |
| Removed | [Duplicate keys with conflicting values in engine labels](#duplicate-keys-with-conflicting-values-in-engine-labels) | v1.13 | v17.12 |
| Deprecated | [`MAINTAINER` in Dockerfile](#maintainer-in-dockerfile) | v1.13 | - |
| Deprecated | [API calls without a version](#api-calls-without-a-version) | v1.13 | v17.12 |
| Removed | [Backing filesystem without `d_type` support for overlay/overlay2](#backing-filesystem-without-d_type-support-for-overlayoverlay2) | v1.13 | v17.12 |
| Removed | [`--automated` and `--stars` flags on `docker search`](#--automated-and---stars-flags-on-docker-search) | v1.12 | v20.10 |
| Deprecated | [`-h` shorthand for `--help`](#-h-shorthand-for---help) | v1.12 | v17.09 |
| Removed | [`-e` and `--email` flags on `docker login`](#-e-and---email-flags-on-docker-login) | v1.11 | v17.06 |
| Deprecated | [Separator (`:`) of `--security-opt` flag on `docker run`](#separator--of---security-opt-flag-on-docker-run) | v1.11 | v17.06 |
| Deprecated | [Ambiguous event fields in API](#ambiguous-event-fields-in-api) | v1.10 | - |
| Removed | [`-f` flag on `docker tag`](#-f-flag-on-docker-tag) | v1.10 | v1.12 |
| Removed | [HostConfig at API container start](#hostconfig-at-api-container-start) | v1.10 | v1.12 |
| Removed | [`--before` and `--since` flags on `docker ps`](#--before-and---since-flags-on-docker-ps) | v1.10 | v1.12 |
| Removed | [Driver-specific log tags](#driver-specific-log-tags) | v1.9 | v1.12 |
| Removed | [Docker Content Trust `ENV` passphrase variables name change](#docker-content-trust-env-passphrase-variables-name-change) | v1.9 | v1.12 |
| Removed | [`/containers/(id or name)/copy` endpoint](#containersid-or-namecopy-endpoint) | v1.8 | v1.12 |
| Removed | [LXC built-in exec driver](#lxc-built-in-exec-driver) | v1.8 | v1.10 |
| Removed | [Old Command Line Options](#old-command-line-options) | v1.8 | v1.10 |
| Removed | [`--api-enable-cors` flag on `dockerd`](#--api-enable-cors-flag-on-dockerd) | v1.6 | v17.09 |
| Removed | [`--run` flag on `docker commit`](#--run-flag-on-docker-commit) | v0.10 | v1.13 |
| Removed | [Three arguments form in `docker import`](#three-arguments-form-in-docker-import) | v0.6.7 | v1.12 |
docs: add status table to "deprecated.md" Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 08:41:38 -05:00
docs: deprecate TCP connection without TLS Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
2024-03-08 08:50:15 -05:00
### Unauthenticated TCP connections
**Deprecated in Release: v26.0**
**Target For Removal In Release: v27.0**
Configuring the Docker daemon to listen on a TCP address will require mandatory
TLS verification. This change aims to ensure secure communication by preventing
unauthorized access to the Docker daemon over potentially insecure networks.
This mandatory TLS requirement applies to all TCP addresses except `tcp://localhost`.
In version 27.0 and later, specifying `--tls=false` or `--tlsverify=false` CLI flags
causes the daemon to fail to start if it's also configured to accept remote connections over TCP.
This also applies to the equivalent configuration options in `daemon.json`.
To facilitate remote access to the Docker daemon over TCP, you'll need to
implement TLS verification. This secures the connection by encrypting data in
transit and providing a mechanism for mutual authentication.
For environments remote daemon access isn't required,
we recommend binding the Docker daemon to a Unix socket.
For daemon's where remote access is required and where TLS encryption is not feasible,
you may want to consider using SSH as an alternative solution.
For further information, assistance, and step-by-step instructions on
configuring TLS (or SSH) for the Docker daemon, refer to
[Protect the Docker daemon socket](https://docs.docker.com/engine/security/protect-access/).
deprecate old API versions (1.23 and lower) The Docker daemon provides a versioned API for backward compatibility with old clients. Docker clients can perform API-version negotiation to select the most recent API version supported by the daemon (downgrading to and older version of the API when necessary). API version negotiation was introduced in Docker v1.12.0 (API 1.24), and clients before that used a fixed API version. Docker Engine versions through v25.0 provide support for all [API versions](https://docs.docker.com/engine/api/#api-version-matrix) included in stable releases for a given platform. For Docker daemons on Linux, the earliest supported API version is 1.12 (corresponding with Docker Engine v1.0.0), whereas for Docker daemons on Windows, the earliest supported API version is 1.24 (corresponding with Docker Engine v1.12.0). Support for legacy API versions (providing old API versions on current versions of the Docker Engine) is primarily intended to provide compatibility with recent, but still supported versions of the client, which is a common scenario (the Docker daemon may be updated to the latest release, but not all clients may be up-to-date or vice versa). Support for API versions before that (API versions provided by EOL versions of the Docker Daemon) is provided on a "best effort" basis. Use of old API versions is very rare, and support for legacy API versions involves significant complexity (Docker 1.0.0 having been released 10 years ago). Because of this, we'll start deprecating support for legacy API versions. Docker Engine v25.0 by default disables API version older than 1.24 (aligning the minimum supported API version between Linux and Windows daemons). When connecting with a client that uses an API version version older than 1.24, the daemon returns an error. The following example configures the docker CLI to use API version 1.23, which produces an error: DOCKER_API_VERSION=1.23 docker version Error response from daemon: client version 1.23 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version An environment variable (`DOCKER_MIN_API_VERSION`) is introduced that allows re-enabling older API versions in the daemon. This environment variable must be set in the daemon's environment (for example, through a [systemd override file](https://docs.docker.com/config/daemon/systemd/)), and the specified API version must be supported by the daemon (`1.12` or higher on Linux, or `1.24` or higher on Windows). Support for API versions lower than `1.24` will be permanently removed in Docker Engine v26, and the minimum supported API version will be incrementally raised in releases following that. We do not recommend depending on the `DOCKER_MIN_API_VERSION` environment variable other than for exceptional cases where it's not possible to update old clients, and those clients must be supported. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-12-08 20:24:30 -05:00
### Deprecate legacy API versions
**Deprecated in Release: v25.0**
**Target For Removal In Release: v26.0**
The Docker daemon provides a versioned API for backward compatibility with old
clients. Docker clients can perform API-version negotiation to select the most
recent API version supported by the daemon (downgrading to and older version of
the API when necessary). API version negotiation was introduced in Docker v1.12.0
(API 1.24), and clients before that used a fixed API version.
Docker Engine versions through v25.0 provide support for all [API versions](https://docs.docker.com/engine/api/#api-version-matrix)
included in stable releases for a given platform. For Docker daemons on Linux,
the earliest supported API version is 1.12 (corresponding with Docker Engine
v1.0.0), whereas for Docker daemons on Windows, the earliest supported API
version is 1.24 (corresponding with Docker Engine v1.12.0).
Support for legacy API versions (providing old API versions on current versions
of the Docker Engine) is primarily intended to provide compatibility with recent,
but still supported versions of the client, which is a common scenario (the Docker
daemon may be updated to the latest release, but not all clients may be up-to-date
or vice versa). Support for API versions before that (API versions provided by
EOL versions of the Docker Daemon) is provided on a "best effort" basis.
Use of old API versions is very rare, and support for legacy API versions
involves significant complexity (Docker 1.0.0 having been released 10 years ago).
Because of this, we'll start deprecating support for legacy API versions.
Docker Engine v25.0 by default disables API version older than 1.24 (aligning
the minimum supported API version between Linux and Windows daemons). When
connecting with a client that uses an API version version older than 1.24,
the daemon returns an error. The following example configures the docker
CLI to use API version 1.23, which produces an error:
```console
DOCKER_API_VERSION=1.23 docker version
Error response from daemon: client version 1.23 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version
```
An environment variable (`DOCKER_MIN_API_VERSION`) is introduced that allows
re-enabling older API versions in the daemon. This environment variable must
be set in the daemon's environment (for example, through a [systemd override
file](https://docs.docker.com/config/daemon/systemd/)), and the specified
API version must be supported by the daemon (`1.12` or higher on Linux, or
`1.24` or higher on Windows).
Support for API versions lower than `1.24` will be permanently removed in Docker
Engine v26, and the minimum supported API version will be incrementally raised
in releases following that.
We do not recommend depending on the `DOCKER_MIN_API_VERSION` environment
variable other than for exceptional cases where it's not possible to update
old clients, and those clients must be supported.
search: deprecate "is-automated" filter and "IsAutomated" field The IsAutomated field is being deprecated by Docker Hub's search API and will always be "false" in future. This patch: - Deprecates the field and the related "is-automated" filter - Removes the "AUTOMATED" column from the default output of "docker search" Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-07-10 14:18:28 -04:00
docs: deprecate short cid in Aliases field Related to https://github.com/moby/moby/pull/46853 Co-Authored-by: Sebastiaan van Stijn <github@gone.nl> Signed-off-by: Albin Kerouanton <albinker@gmail.com>
2023-12-20 16:45:15 -05:00
### Container short ID in network Aliases field
**Deprecated in Release: v25.0**
docs/deprecated: update status of short cid alias deprecation Starting with API v1.45, the container short ID is removed from the container Aliases. Signed-off-by: Albin Kerouanton <albinker@gmail.com>
2024-03-18 05:39:14 -04:00
**Removed In Release: v26.0**
docs: deprecate short cid in Aliases field Related to https://github.com/moby/moby/pull/46853 Co-Authored-by: Sebastiaan van Stijn <github@gone.nl> Signed-off-by: Albin Kerouanton <albinker@gmail.com>
2023-12-20 16:45:15 -05:00
The `Aliases` field returned by `docker inspect` contains the container short
ID once the container is started. This behavior is deprecated in v25.0 but
kept until the next release, v26.0. Starting with that version, the `Aliases`
field will only contain the aliases set through the `docker container create`
and `docker run` flag `--network-alias`.
A new field `DNSNames` containing the container name (if one was specified),
the hostname, the network aliases, as well as the container short ID, has been
introduced in v25.0 and should be used instead of the `Aliases` field.
search: deprecate "is-automated" filter and "IsAutomated" field The IsAutomated field is being deprecated by Docker Hub's search API and will always be "false" in future. This patch: - Deprecates the field and the related "is-automated" filter - Removes the "AUTOMATED" column from the default output of "docker search" Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-07-10 14:18:28 -04:00
### IsAutomated field, and "is-automated" filter on docker search
**Deprecated in Release: v25.0**
**Target For Removal In Release: v26.0**
The "is_automated" field has been deprecated by Docker Hub's search API.
Consequently, the `IsAutomated` field in image search will always be set
to `false` in future, and searching for "is-automated=true" will yield no
results.
The `AUTOMATED` column has been removed from the default `docker search`
and `docker image search` output in v25.0, and the corresponding `IsAutomated`
templating option will be removed in v26.0.
docs/deprecated: mark logentries log-driver for removal The service has been discontinued on November 15, 2022: > Dear Logentries user, > > We have identified you as the owner of, or collaborator of, a Logentries > account. > > The Logentries service will be discontinued on November 15th, 2022. This > means that your Logentries account access will be removed and all your > log data will be permanently deleted on this date. > > Next Steps > If you are interested in an alternative Rapid7 log management solution, > InsightOps will be available for purchase through December 16th, 2022. > Please note, there is no support to migrate your existing Logentries > account to InsightOps. > > Thank you for being a valued user of Logentries. > > Thank you, > Rapid7 Customer Success Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-12-13 03:12:02 -05:00
### Logentries logging driver
**Deprecated in Release: v24.0**
docs/deprecated: mark logentries logging-driver as "removed" This driver has been deprecated and removed because the service is no longer operational. Update the deprecated features docs to mention it's been fully removed in Docker v25.0. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-12-13 07:19:33 -05:00
**Removed in Release: v25.0**
docs/deprecated: mark logentries log-driver for removal The service has been discontinued on November 15, 2022: > Dear Logentries user, > > We have identified you as the owner of, or collaborator of, a Logentries > account. > > The Logentries service will be discontinued on November 15th, 2022. This > means that your Logentries account access will be removed and all your > log data will be permanently deleted on this date. > > Next Steps > If you are interested in an alternative Rapid7 log management solution, > InsightOps will be available for purchase through December 16th, 2022. > Please note, there is no support to migrate your existing Logentries > account to InsightOps. > > Thank you for being a valued user of Logentries. > > Thank you, > Rapid7 Customer Success Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-12-13 03:12:02 -05:00
The logentries service SaaS was shut down on November 15, 2022, rendering
this logging driver non-functional. Users should no longer use this logging
docs/deprecated: mark logentries logging-driver as "removed" This driver has been deprecated and removed because the service is no longer operational. Update the deprecated features docs to mention it's been fully removed in Docker v25.0. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-12-13 07:19:33 -05:00
driver, and the driver has been removed in Docker 25.0. Existing containers
using this logging-driver are migrated to use the "local" logging driver
after upgrading.
docs/deprecated: mark logentries log-driver for removal The service has been discontinued on November 15, 2022: > Dear Logentries user, > > We have identified you as the owner of, or collaborator of, a Logentries > account. > > The Logentries service will be discontinued on November 15th, 2022. This > means that your Logentries account access will be removed and all your > log data will be permanently deleted on this date. > > Next Steps > If you are interested in an alternative Rapid7 log management solution, > InsightOps will be available for purchase through December 16th, 2022. > Please note, there is no support to migrate your existing Logentries > account to InsightOps. > > Thank you for being a valued user of Logentries. > > Thank you, > Rapid7 Customer Success Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-12-13 03:12:02 -05:00
docs: deprecation: OOM-score adjust for the daemon The `oom-score-adjust` option was added to prevent the daemon from being OOM-killed before other processes. This option was mostly added as a convenience, as running the daemon as a systemd unit was not yet common. Having the daemon set its own limits is not best-practice, and something better handled by the process-manager starting the daemon. Docker v20.10 and newer no longer adjust the daemon's OOM score by default, instead setting the OOM-score to the systemd unit (OOMScoreAdjust) that's shipped with the packages. Users currently depending on this feature are recommended to adjust the daemon's OOM score using systemd or through other means, when starting the daemon. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-04-15 08:43:35 -04:00
### OOM-score adjust for the daemon
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
**Deprecated in Release: v24.0**
docs/deprecated: update "oom-score-adjust" status for daemon Using this option on the daemon will now produce an error (flag will be removed entirely in v26.0). Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-12-20 17:25:56 -05:00
**Removed in Release: v25.0**
docs: deprecation: OOM-score adjust for the daemon The `oom-score-adjust` option was added to prevent the daemon from being OOM-killed before other processes. This option was mostly added as a convenience, as running the daemon as a systemd unit was not yet common. Having the daemon set its own limits is not best-practice, and something better handled by the process-manager starting the daemon. Docker v20.10 and newer no longer adjust the daemon's OOM score by default, instead setting the OOM-score to the systemd unit (OOMScoreAdjust) that's shipped with the packages. Users currently depending on this feature are recommended to adjust the daemon's OOM score using systemd or through other means, when starting the daemon. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-04-15 08:43:35 -04:00
The `oom-score-adjust` option was added to prevent the daemon from being
OOM-killed before other processes. This option was mostly added as a
convenience, as running the daemon as a systemd unit was not yet common.
Having the daemon set its own limits is not best-practice, and something
better handled by the process-manager starting the daemon.
Docker v20.10 and newer no longer adjust the daemon's OOM score by default,
instead setting the OOM-score to the systemd unit (OOMScoreAdjust) that's
shipped with the packages.
Users currently depending on this feature are recommended to adjust the
daemon's OOM score using systemd or through other means, when starting
the daemon.
docs: Deprecate buildkit's build information Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
2023-03-02 11:27:05 -05:00
### Buildkit build information
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
**Deprecated in Release: v23.0**
**Removed in Release: v24.0**
docs: Deprecate buildkit's build information Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
2023-03-02 11:27:05 -05:00
[Build information](https://github.com/moby/buildkit/blob/v0.11/docs/buildinfo.md)
structures have been introduced in [BuildKit v0.10.0](https://github.com/moby/buildkit/releases/tag/v0.10.0)
and are generated with build metadata that allows you to see all the sources
(images, git repositories) that were used by the build with their exact
versions and also the configuration that was passed to the build. This
information is also embedded into the image configuration if one is generated.
Update deprecation docs - expand a bit on what's happening - clarify start of deprecation of the classic builder - show examples of error and warning Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-01-27 12:54:06 -05:00
### Legacy builder for Linux images
builder: fallback to legacy Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
2022-01-27 13:30:06 -05:00
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
**Deprecated in Release: v23.0**
builder: fallback to legacy Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
2022-01-27 13:30:06 -05:00
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
Docker v23.0 now uses BuildKit by default to build Linux images, and uses the
Update deprecation docs - expand a bit on what's happening - clarify start of deprecation of the classic builder - show examples of error and warning Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-01-27 12:54:06 -05:00
[Buildx](https://docs.docker.com/buildx/working-with-buildx/) CLI component for
`docker build`. With this change, `docker build` now exposes all advanced features
that BuildKit provides and which were previously only available through the
`docker buildx` subcommands.
The Buildx component is installed automatically when installing the `docker` CLI
using our `.deb` or `.rpm` packages, and statically linked binaries are provided
both on `download.docker.com`, and through the [`docker/buildx-bin` image](https://hub.docker.com/r/docker/buildx-bin)
on Docker Hub. Refer the [Buildx section](http://docs.docker.com/go/buildx/) for
detailed instructions on installing the Buildx component.
This release marks the beginning of the deprecation cycle of the classic ("legacy")
builder for Linux images. No active development will happen on the classic builder
(except for bugfixes). BuildKit development started five Years ago, left the
"experimental" phase since Docker 18.09, and is already the default builder for
docs: deprecated: fix link to Docker Desktop 3.2.0 release notes Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-01-06 10:55:50 -05:00
[Docker Desktop](https://docs.docker.com/desktop/previous-versions/3.x-mac/#docker-desktop-320).
Update deprecation docs - expand a bit on what's happening - clarify start of deprecation of the classic builder - show examples of error and warning Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-01-27 12:54:06 -05:00
While we're comfortable that BuildKit is stable for general use, there may be
some changes in behavior. If you encounter issues with BuildKit, we encourage
you to report issues in the [BuildKit issue tracker on GitHub](https://github.com/moby/buildkit/){:target="_blank" rel="noopener" class="_"}
> Classic builder for building Windows images
>
> BuildKit does not (yet) provide support for building Windows images, and
> `docker build` continues to use the classic builder to build native Windows
> images on Windows daemons.
### Legacy builder fallback
builder: fallback to legacy Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
2022-01-27 13:30:06 -05:00
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
**Deprecated in Release: v23.0**
builder: fallback to legacy Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
2022-01-27 13:30:06 -05:00
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
[Docker v23.0 now uses BuildKit by default to build Linux images](#legacy-builder-for-linux-images),
Update deprecation docs - expand a bit on what's happening - clarify start of deprecation of the classic builder - show examples of error and warning Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-01-27 12:54:06 -05:00
which requires the Buildx component to build images with BuildKit. There may be
situations where the Buildx component is not available, and BuildKit cannot be
used.
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
To provide a smooth transition to BuildKit as the default builder, Docker v23.0
Update deprecation docs - expand a bit on what's happening - clarify start of deprecation of the classic builder - show examples of error and warning Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-01-27 12:54:06 -05:00
has an automatic fallback for some situations, or produces an error to assist
users to resolve the problem.
In situations where the user did not explicitly opt-in to use BuildKit (i.e.,
`DOCKER_BUILDKIT=1` is not set), the CLI automatically falls back to the classic
builder, but prints a deprecation warning:
```
DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
Install the buildx component to build images with BuildKit:
https://docs.docker.com/go/buildx/
```
This situation may occur if the `docker` CLI is installed using the static binaries,
and the Buildx component is not installed or not installed correctly. This fallback
will be removed in a future release, therefore we recommend to [install the Buildx component](https://docs.docker.com/go/buildx/)
and use BuildKit for your builds, or opt-out of using BuildKit with `DOCKER_BUILDKIT=0`.
If you opted-in to use BuildKit (`DOCKER_BUILDKIT=1`), but the Buildx component
is missing, an error is printed instead, and the `docker build` command fails:
```
ERROR: BuildKit is enabled but the buildx component is missing or broken.
Install the buildx component to build images with BuildKit:
https://docs.docker.com/go/buildx/
```
We recommend to [install the Buildx component](https://docs.docker.com/go/buildx/)
to continue using BuildKit for your builds, but alternatively, users can either
unset the `DOCKER_BUILDKIT` environment variable to fall back to the legacy builder,
or opt-out of using BuildKit with `DOCKER_BUILDKIT=0`.
Be aware that the [classic builder is deprecated](#legacy-builder-for-linux-images)
so both the automatic fallback and opting-out of using BuildKit will no longer
be possible in a future release.
builder: fallback to legacy Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
2022-01-27 13:30:06 -05:00
deprecation: mark btrfs driver as deprecated for CentOS 7 and RHEL7 Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-01-09 08:31:33 -05:00
### Btrfs storage driver on CentOS 7 and RHEL 7
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
**Removed in Release: v23.0**
deprecation: mark btrfs driver as deprecated for CentOS 7 and RHEL7 Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-01-09 08:31:33 -05:00
The `btrfs` storage driver on CentOS and RHEL was provided as a technology preview
by CentOS and RHEL, but has been deprecated since the [Red Hat Enterprise Linux 7.4 release](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/ch-btrfs),
and removed in CentOS 8 and RHEL 8. Users of the `btrfs` storage driver on CentOS
are recommended to migrate to a different storage driver, such as `overlay2`, which
is now the default storage driver. Docker 23.0 continues to provide the `btrfs`
storage driver to allow users to migrate to an alternative driver. The next release
of Docker will no longer provide this driver.
context: deprecate support for encrypted TLS private keys > Legacy PEM encryption as specified in RFC 1423 is insecure by design. Since > it does not authenticate the ciphertext, it is vulnerable to padding oracle > attacks that can let an attacker recover the plaintext From https://go-review.googlesource.com/c/go/+/264159 > It's unfortunate that we don't implement PKCS#8 encryption so we can't > recommend an alternative but PEM encryption is so broken that it's worth > deprecating outright. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2021-07-28 06:45:09 -04:00
### Support for encrypted TLS private keys
**Deprecated in Release: v20.10**
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
**Removed in Release: v23.0**
Remove support for encrypted TLS private keys > Legacy PEM encryption as specified in RFC 1423 is insecure by design. Since > it does not authenticate the ciphertext, it is vulnerable to padding oracle > attacks that can let an attacker recover the plaintext From https://go-review.googlesource.com/c/go/+/264159 > It's unfortunate that we don't implement PKCS#8 encryption so we can't > recommend an alternative but PEM encryption is so broken that it's worth > deprecating outright. This feature allowed using an encrypted private key with a supplied password, but did not provide additional security as the encryption is known to be broken, and the key is sitting next to the password in the filesystem. Users are recommended to decrypt the private key, and store it un-encrypted to continue using it. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2021-07-28 10:08:09 -04:00
Use of encrypted TLS private keys has been deprecated, and has been removed.
Golang has deprecated support for legacy PEM encryption (as specified in
[RFC 1423](https://datatracker.ietf.org/doc/html/rfc1423)), as it is insecure by
design (see [https://go-review.googlesource.com/c/go/+/264159](https://go-review.googlesource.com/c/go/+/264159)).
This feature allowed using an encrypted private key with a supplied password,
but did not provide additional security as the encryption is known to be broken,
and the key is sitting next to the password in the filesystem. Users are recommended
to decrypt the private key, and store it un-encrypted to continue using it.
context: deprecate support for encrypted TLS private keys > Legacy PEM encryption as specified in RFC 1423 is insecure by design. Since > it does not authenticate the ciphertext, it is vulnerable to padding oracle > attacks that can let an attacker recover the plaintext From https://go-review.googlesource.com/c/go/+/264159 > It's unfortunate that we don't implement PKCS#8 encryption so we can't > recommend an alternative but PEM encryption is so broken that it's worth > deprecating outright. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2021-07-28 06:45:09 -04:00
Deprecate Kubernetes context support Signed-off-by: Mathieu Champlon <mathieu.champlon@docker.com>
2021-07-01 02:59:10 -04:00
### Kubernetes stack and context support
Deprecate Kubernetes stack support Signed-off-by: Mathieu Champlon <mathieu.champlon@docker.com>
2021-06-28 08:57:15 -04:00
**Deprecated in Release: v20.10**
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
**Removed in Release: v23.0**
docs: add more details to stack kubernetes deprecation Explicitly mention flags and environment variables that were removed, to make the deprecation more discoverable. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-02-24 05:13:50 -05:00
Following the deprecation of [Compose on Kubernetes](https://github.com/docker/compose-on-kubernetes),
support for Kubernetes in the `stack` and `context` commands has been removed from
the cli, and options related to this functionality are now either ignored, or may
produce an error.
The following command-line flags are removed from the `docker context` subcommands:
- `--default-stack-orchestrator` - swarm is now the only (and default) orchestrator for stacks.
- `--kubernetes` - the kubernetes endpoint can no longer be stored in `docker context`.
- `--kubeconfig` - exporting a context as a kubeconfig file is no longer supported.
The output produced by the `docker context inspect` subcommand no longer contains
information about `StackOrchestrator` and `Kubernetes` endpoints for new contexts.
The following command-line flags are removed from the `docker stack` subcommands:
- `--kubeconfig` - using a kubeconfig file as context is no longer supported.
- `--namespace` - configuring the kubernetes namespace for stacks is no longer supported.
- `--orchestrator` - swarm is now the only (and default) orchestrator for stacks.
Deprecate Kubernetes stack support Signed-off-by: Mathieu Champlon <mathieu.champlon@docker.com>
2021-06-28 08:57:15 -04:00
docs: add more details to stack kubernetes deprecation Explicitly mention flags and environment variables that were removed, to make the deprecation more discoverable. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-02-24 05:13:50 -05:00
The `DOCKER_STACK_ORCHESTRATOR`, `DOCKER_ORCHESTRATOR`, and `KUBECONFIG` environment
config: mark stackOrchestrator option as deprecated Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-02-24 07:35:03 -05:00
variables, as well as the `stackOrchestrator` option in the `~/.docker/config.json`
cli configuration file are no longer used, and ignored.
Deprecate Kubernetes stack support Signed-off-by: Mathieu Champlon <mathieu.champlon@docker.com>
2021-06-28 08:57:15 -04:00
Add deprecation note for non-compliant registries Docker Engine v20.10 and up includes optimizations to verify if images in the local image cache need updating before pulling, preventing the Docker Engine from making unnecessary API requests. These optimizations require the container image registry to conform to the Open Container Initiative Distribution Specification (https://github.com/opencontainers/distribution-spec). While most registries conform to the specification, we encountered some registries to be non-compliant, resulting in `docker pull` to fail. As a temporary solution, Docker Engine v20.10 includes a fallback mechanism to allow `docker pull` to be functional when using a non-compliant registry. A warning message is printed in this situation: WARNING Failed to pull manifest by the resolved digest. This registry does not appear to conform to the distribution registry specification; falling back to pull by tag. This fallback is DEPRECATED, and will be removed in a future release. The fallback is added to allow users to either migrate their images to a compliant registry, or for these registries to become compliant. Note that this fallback only addresses failures on `docker pull`. Other commands, such as `docker stack deploy`, or pulling images with `containerd` will continue to fail. Given that other functionality is still broken with these registries, we consider this fallback a _temporary_ solution, and will remove the fallback in an upcoming major release. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-12-07 07:34:50 -05:00
### Pulling images from non-compliant image registries
**Deprecated in Release: v20.10**
Docker Engine v20.10 and up includes optimizations to verify if images in the
local image cache need updating before pulling, preventing the Docker Engine
from making unnecessary API requests. These optimizations require the container
image registry to conform to the [Open Container Initiative Distribution Specification](https://github.com/opencontainers/distribution-spec).
While most registries conform to the specification, we encountered some registries
to be non-compliant, resulting in `docker pull` to fail.
As a temporary solution, Docker Engine v20.10 includes a fallback mechanism to
allow `docker pull` to be functional when using a non-compliant registry. A
warning message is printed in this situation:
WARNING Failed to pull manifest by the resolved digest. This registry does not
appear to conform to the distribution registry specification; falling back to
pull by tag. This fallback is DEPRECATED, and will be removed in a future
release.
The fallback is added to allow users to either migrate their images to a compliant
registry, or for these registries to become compliant.
Note that this fallback only addresses failures on `docker pull`. Other commands,
such as `docker stack deploy`, or pulling images with `containerd` will continue
to fail.
Given that other functionality is still broken with these registries, we consider
this fallback a _temporary_ solution, and will remove the fallback in an upcoming
major release.
Deprecate Linux containers on Windows (LCOW) (experimental) The experimental feature to run Linux containers on Windows (LCOW) was introduced as a technical preview in Docker 17.09. While many enhancements were made after its introduction, the feature never reached completeness, and development has now stopped in favor of running docker natively on Linux in WSL2. Developers that need to run Linux workloads on a Windows host are encouraged to use Docker Desktop with WSL2 instead. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-16 04:58:49 -04:00
### Linux containers on Windows (LCOW) (experimental)
**Deprecated in Release: v20.10**
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
**Removed in Release: v23.0**
Deprecate Linux containers on Windows (LCOW) (experimental) The experimental feature to run Linux containers on Windows (LCOW) was introduced as a technical preview in Docker 17.09. While many enhancements were made after its introduction, the feature never reached completeness, and development has now stopped in favor of running docker natively on Linux in WSL2. Developers that need to run Linux workloads on a Windows host are encouraged to use Docker Desktop with WSL2 instead. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-16 04:58:49 -04:00
The experimental feature to run Linux containers on Windows (LCOW) was introduced
as a technical preview in Docker 17.09. While many enhancements were made after
its introduction, the feature never reached completeness, and development has
now stopped in favor of running docker natively on Linux in WSL2.
Developers who want to run Linux workloads on a Windows host are encouraged to use
[Docker Desktop with WSL2](https://docs.docker.com/docker-for-windows/wsl/) instead.
deprecate blkio-weight options with cgroups v1 These options were deprecated and removed in the Linux kernel v5.0 and up in; - https://github.com/torvalds/linux/commit/f382fb0bcef4c37dc049e9f6963e3baf204d815c - https://github.com/torvalds/linux/commit/fb5772cbfe48575711bf789767d561582376f7f1 - https://github.com/torvalds/linux/commit/23aa16489c06e6739c7c99e9fdccf723d2691a5d Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2021-01-04 08:36:25 -05:00
### BLKIO weight options with cgroups v1
**Deprecated in Release: v20.10**
Specifying blkio weight (`docker run --blkio-weight` and `docker run --blkio-weight-device`)
docs: fix typo in deprecated.md Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2021-01-08 10:03:51 -05:00
is now marked as deprecated when using cgroups v1 because the corresponding features
deprecate blkio-weight options with cgroups v1 These options were deprecated and removed in the Linux kernel v5.0 and up in; - https://github.com/torvalds/linux/commit/f382fb0bcef4c37dc049e9f6963e3baf204d815c - https://github.com/torvalds/linux/commit/fb5772cbfe48575711bf789767d561582376f7f1 - https://github.com/torvalds/linux/commit/23aa16489c06e6739c7c99e9fdccf723d2691a5d Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2021-01-04 08:36:25 -05:00
were [removed in Linux kernel v5.0 and up](https://github.com/torvalds/linux/commit/f382fb0bcef4c37dc049e9f6963e3baf204d815c).
When using cgroups v2, the `--blkio-weight` options are implemented using
[`io.weight](https://github.com/torvalds/linux/blob/v5.0/Documentation/admin-guide/cgroup-v2.rst#io).
deprecate `docker run --kernel-memory` `docker run --kernel-memory` is being deprecated in https://github.com/moby/moby/pull/41254 Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
2020-07-24 07:49:00 -04:00
### Kernel memory limit
docs: update 20.03 -> 20.10 in deprecated.md Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-13 03:38:48 -04:00
**Deprecated in Release: v20.10**
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
**Removed in Release: v23.0**
deprecate `docker run --kernel-memory` `docker run --kernel-memory` is being deprecated in https://github.com/moby/moby/pull/41254 Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
2020-07-24 07:49:00 -04:00
update deprecation status of --kernel-memory(-tcp) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-04-07 08:36:11 -04:00
Specifying kernel memory limit (`docker run --kernel-memory`) is no longer supported
because the [Linux kernel deprecated `kmem.limit_in_bytes` in v5.4](https://github.com/torvalds/linux/commit/0158115f702b0ba208ab0b5adf44cae99b3ebcc7).
The OCI runtime specification now marks this option (as well as `--kernel-memory-tcp`)
as ["NOT RECOMMENDED"](https://github.com/opencontainers/runtime-spec/pull/1093),
and OCI runtimes such as `runc` no longer support this option.
Docker API v1.42 and up now ignores this option when set. Older versions of the
API continue to accept the option, but depending on the OCI runtime used, may
take no effect.
> **Note**
>
> While not deprecated (yet) in Docker, the OCI runtime specification also
> deprecated the `memory.kmem.tcp.limit_in_bytes` option. When using `runc` as
> runtime, this option takes no effect. The linux kernel did not explicitly
> deprecate this feature, and there is a tracking ticket in the `runc` issue
> tracker to determine if this option should be reinstated or if this was an
> oversight of the Linux kernel maintainers (see [opencontainers/runc#3174](https://github.com/opencontainers/runc/issues/3174)).
>
> The `memory.kmem.tcp.limit_in_bytes` option is only supported with cgroups v1,
> and not available on installations running with cgroups v2. This option is
> only supported by the API, and not exposed on the `docker` command-line.
deprecate `docker run --kernel-memory` `docker run --kernel-memory` is being deprecated in https://github.com/moby/moby/pull/41254 Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
2020-07-24 07:49:00 -04:00
Deprecate classic Swarm and overlay networks using external k/v stores Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-04-16 09:00:40 -04:00
### Classic Swarm and overlay networks using cluster store
docs: update 20.03 -> 20.10 in deprecated.md Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-13 03:38:48 -04:00
**Deprecated in Release: v20.10**
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
**Removed in Release: v23.0**
Deprecate classic Swarm and overlay networks using external k/v stores Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-04-16 09:00:40 -04:00
Standalone ("classic") Swarm has been deprecated, and with that the use of overlay
networks using an external key/value store. The corresponding`--cluster-advertise`,
docs: update deprecation status of legacy overlay networks Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-04-07 09:14:44 -04:00
`--cluster-store`, and `--cluster-store-opt` daemon options have been removed.
document deprecation of legacy `~/.dockercfg` config-file The docker CLI up until v1.7.0 used the `~/.dockercfg` file to store credentials after authenticating to a registry (`docker login`). Docker v1.7.0 replaced this file with a new CLI configuration file, located in `~/.docker/config.json`. When implementing the new configuration file, the old file (and file-format) was kept as a fall-back, to assist existing users with migrating to the new file. Given that the old file format encourages insecure storage of credentials (credentials are stored unencrypted), and that no version of the CLI since Docker v1.7.0 has created this file, the file is marked deprecated, and support for this file will be removed in a future release. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-05-13 19:27:58 -04:00
### Support for legacy `~/.dockercfg` configuration files
docs: update 20.03 -> 20.10 in deprecated.md Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-13 03:38:48 -04:00
**Deprecated in Release: v20.10**
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
**Removed in Release: v23.0**
document deprecation of legacy `~/.dockercfg` config-file The docker CLI up until v1.7.0 used the `~/.dockercfg` file to store credentials after authenticating to a registry (`docker login`). Docker v1.7.0 replaced this file with a new CLI configuration file, located in `~/.docker/config.json`. When implementing the new configuration file, the old file (and file-format) was kept as a fall-back, to assist existing users with migrating to the new file. Given that the old file format encourages insecure storage of credentials (credentials are stored unencrypted), and that no version of the CLI since Docker v1.7.0 has created this file, the file is marked deprecated, and support for this file will be removed in a future release. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-05-13 19:27:58 -04:00
The docker CLI up until v1.7.0 used the `~/.dockercfg` file to store credentials
after authenticating to a registry (`docker login`). Docker v1.7.0 replaced this
file with a new CLI configuration file, located in `~/.docker/config.json`. When
implementing the new configuration file, the old file (and file-format) was kept
as a fall-back, to assist existing users with migrating to the new file.
Given that the old file format encourages insecure storage of credentials
(credentials are stored unencrypted), and that no version of the CLI since
Deprecation: config: remove support for old ~/.dockercfg The `~/.dockercfg` file was replaced by `~/.docker/config.json` in 2015 (github.com/docker/docker/commit/18c9b6c6455f116ae59cde8544413b3d7d294a5e), but the CLI still falls back to checking if this file exists if no current (`~/.docker/config.json`) file was found. Given that no version of the CLI since Docker v1.7.0 has created this file, and if such a file exists, it means someone hasn't re-authenticated for 5 years, it's probably safe to remove this fallback. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-05-07 13:37:16 -04:00
Docker v1.7.0 has created this file, support for this file, and its format has
been removed.
docs: deprecate CLI options for experimental CLI features Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-02 08:10:27 -04:00
### Configuration options for experimental CLI features
docs: update deprecation status of "experimental" cli Change future tense to current tense. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-04-07 16:10:24 -04:00
**Deprecated in Release: v19.03**
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
**Removed in Release: v23.0**
docs: update deprecation status of "experimental" cli Change future tense to current tense. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-04-07 16:10:24 -04:00
docs: deprecate CLI options for experimental CLI features Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-02 08:10:27 -04:00
The `DOCKER_CLI_EXPERIMENTAL` environment variable and the corresponding `experimental`
docs: update deprecation status of "experimental" cli Change future tense to current tense. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-04-07 16:10:24 -04:00
field in the CLI configuration file are deprecated. Experimental features are
enabled by default, and these configuration options are no longer functional.
docs: deprecate CLI options for experimental CLI features Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-02 08:10:27 -04:00
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
Starting with v23.0, the Docker CLI no longer prints `Experimental` for the client
remove "Experimental" client field from "docker version" Configuration (enabling/disabling) of Experimental client features was deprecated in Docker 19.03, and removed in 20.10. Experimental CLI features are now always enabled. In Docker 20.10, the Experimental field in `docker version` was kept (but always true). This patch removes the field from the output (both "pretty" output and the JSON struct). Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-04-07 16:14:25 -04:00
in the output of `docker version`, and the field has been removed from the JSON
format.
Removing CLI plugins API documentation from official documentation as it is now deprecated. Adding depreciation notice. Signed-off-by: Silvin Lubecki <silvin.lubecki@docker.com>
2020-05-12 04:33:16 -04:00
### CLI plugins support
docs: update 20.03 -> 20.10 in deprecated.md Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-13 03:38:48 -04:00
**Deprecated in Release: v20.10**
Removing CLI plugins API documentation from official documentation as it is now deprecated. Adding depreciation notice. Signed-off-by: Silvin Lubecki <silvin.lubecki@docker.com>
2020-05-12 04:33:16 -04:00
CLI Plugin API is now marked as deprecated.
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
deprecate Dockerfile legacy 'ENV name value' syntax The Dockerfile `ENV` instruction allows values to be set using either `ENV name=value` or `ENV name value`. The latter (`ENV name value`) form can be ambiguous, for example, the following defines a single env-variable (`ONE`) with value `"TWO= THREE=world"`, but may have intended to be setting three env-vars: ENV ONE TWO= THREE=world This format also does not allow setting multiple environment-variables in a single `ENV` line in the Dockerfile. Use of the `ENV name value` syntax is discouraged, and may be removed in a future release. Users are encouraged to update their Dockerfiles to use the `ENV name=value` syntax, for example: ENV ONE="" TWO="" THREE="world" Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-09-23 14:48:26 -04:00
### Dockerfile legacy `ENV name value` syntax
docs: update 20.03 -> 20.10 in deprecated.md Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-13 03:38:48 -04:00
**Deprecated in Release: v20.10**
deprecate Dockerfile legacy 'ENV name value' syntax The Dockerfile `ENV` instruction allows values to be set using either `ENV name=value` or `ENV name value`. The latter (`ENV name value`) form can be ambiguous, for example, the following defines a single env-variable (`ONE`) with value `"TWO= THREE=world"`, but may have intended to be setting three env-vars: ENV ONE TWO= THREE=world This format also does not allow setting multiple environment-variables in a single `ENV` line in the Dockerfile. Use of the `ENV name value` syntax is discouraged, and may be removed in a future release. Users are encouraged to update their Dockerfiles to use the `ENV name=value` syntax, for example: ENV ONE="" TWO="" THREE="world" Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-09-23 14:48:26 -04:00
The Dockerfile `ENV` instruction allows values to be set using either `ENV name=value`
or `ENV name value`. The latter (`ENV name value`) form can be ambiguous, for example,
the following defines a single env-variable (`ONE`) with value `"TWO= THREE=world"`,
but may have intended to be setting three env-vars:
```dockerfile
ENV ONE TWO= THREE=world
```
This format also does not allow setting multiple environment-variables in a single
`ENV` line in the Dockerfile.
Use of the `ENV name value` syntax is discouraged, and may be removed in a future
release. Users are encouraged to update their Dockerfiles to use the `ENV name=value`
syntax, for example:
```dockerfile
ENV ONE="" TWO="" THREE="world"
```
Deprecation: add experimental docker build --stream option Docker v17.07 introduced an experimental `--stream` flag on `docker build` which allowed the build-context to be incrementally sent to the daemon, instead of unconditionally sending the whole build-context. This functionality has been reimplemented as part of BuildKit, which uses streaming by default and the `--stream` option will be ignored when using the classic builder, printing a deprecation warning instead. Users that want to use this feature are encouraged to enable BuildKit by setting the `DOCKER_BUILDKIT=1` environment variable or through the daemon or CLI configuration files. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-23 19:03:47 -04:00
### `docker build --stream` flag (experimental)
**Deprecated in Release: v20.10**
**Removed in Release: v20.10**
Docker v17.07 introduced an experimental `--stream` flag on `docker build` which
allowed the build-context to be incrementally sent to the daemon, instead of
unconditionally sending the whole build-context.
This functionality has been reimplemented as part of BuildKit, which uses streaming
by default and the `--stream` option will be ignored when using the classic builder,
printing a deprecation warning instead.
Users that want to use this feature are encouraged to enable BuildKit by setting
the `DOCKER_BUILDKIT=1` environment variable or through the daemon or CLI configuration
files.
docs: deprecated: add entry for "fluent-async-connect" log-opt This option was deperecated in the upstream fluentd logging driver v1.4.0, and while we documented it as deprecated in the API changelog, there was no mention yet in the deprecated docs. relates to: - https://github.com/fluent/fluent-logger-golang/pull/56 - https://github.com/moby/moby/pull/39086 Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-04-10 05:55:30 -04:00
### `fluentd-async-connect` log opt
**Deprecated in Release: v20.10**
The `--log-opt fluentd-async-connect` option for the fluentd logging driver is
[deprecated in favor of `--log-opt fluentd-async`](https://github.com/moby/moby/pull/39086).
A deprecation message is logged in the daemon logs if the old option is used:
```console
fluent#New: AsyncConnect is now deprecated, please use Async instead
```
Users are encouraged to use the `fluentd-async` option going forward, as support
for the old option will be removed in a future release.
deprecate registry v2 schema 1 Co-Authored-By: Sebastiaan van Stijn <github@gone.nl> Signed-off-by: Andrew Hsu <andrewhsu@docker.com> Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2019-06-18 14:51:19 -04:00
### Pushing and pulling with image manifest v2 schema 1
docs/deprecated: remove minor versions Some deprecations are ammended during a major (YY.MM) release, to inform users as early as possible about deprecations. Removing the minor version from this overview clarifies that features are marked deprecated during which major release's lifecycle. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-02 08:15:42 -04:00
**Deprecated in Release: v19.03**
deprecate registry v2 schema 1 Co-Authored-By: Sebastiaan van Stijn <github@gone.nl> Signed-off-by: Andrew Hsu <andrewhsu@docker.com> Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2019-06-18 14:51:19 -04:00
deprecate legacy image formats Mark pulling legacy image formats as deprecated, and describe the DOCKER_ENABLE_DEPRECATED_PULL_SCHEMA_1_IMAGE environment variable. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2024-03-04 03:14:25 -05:00
**Disabled by default in Release: v26.0**
deprecate registry v2 schema 1 Co-Authored-By: Sebastiaan van Stijn <github@gone.nl> Signed-off-by: Andrew Hsu <andrewhsu@docker.com> Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2019-06-18 14:51:19 -04:00
deprecate legacy image formats Mark pulling legacy image formats as deprecated, and describe the DOCKER_ENABLE_DEPRECATED_PULL_SCHEMA_1_IMAGE environment variable. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2024-03-04 03:14:25 -05:00
**Target For Removal In Release: v27.0**
deprecate registry v2 schema 1 Co-Authored-By: Sebastiaan van Stijn <github@gone.nl> Signed-off-by: Andrew Hsu <andrewhsu@docker.com> Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2019-06-18 14:51:19 -04:00
deprecate legacy image formats Mark pulling legacy image formats as deprecated, and describe the DOCKER_ENABLE_DEPRECATED_PULL_SCHEMA_1_IMAGE environment variable. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2024-03-04 03:14:25 -05:00
The image manifest [v2 schema 1](https://distribution.github.io/distribution/spec/deprecated-schema-v1/)
and "Docker Image v1" formats were deprecated in favor of the
[v2 schema 2](https://distribution.github.io/distribution/spec/manifest-v2-2/)
and [OCI image spec](https://github.com/opencontainers/image-spec/tree/v1.1.0)
formats.
deprecate registry v2 schema 1 Co-Authored-By: Sebastiaan van Stijn <github@gone.nl> Signed-off-by: Andrew Hsu <andrewhsu@docker.com> Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2019-06-18 14:51:19 -04:00
deprecate legacy image formats Mark pulling legacy image formats as deprecated, and describe the DOCKER_ENABLE_DEPRECATED_PULL_SCHEMA_1_IMAGE environment variable. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2024-03-04 03:14:25 -05:00
These legacy formats should no longer be used, and users are recommended to
update images to use current formats, or to upgrade to more current images.
Starting with Docker v26.0, pulling these images is disabled by default, and
produces an error when attempting to pull the image:
```console
$ docker pull ubuntu:10.04
Error response from daemon:
[DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release.
Suggest the author of docker.io/library/ubuntu:10.04 to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2.
More information at https://docs.docker.com/go/deprecated-image-specs/
```
An environment variable (`DOCKER_ENABLE_DEPRECATED_PULL_SCHEMA_1_IMAGE`) is
added in Docker v26.0 that allows re-enabling support for these image formats
in the daemon. This environment variable must be set to a non-empty value in
the daemon's environment (for example, through a [systemd override file](https://docs.docker.com/config/daemon/systemd/)).
Support for the `DOCKER_ENABLE_DEPRECATED_PULL_SCHEMA_1_IMAGE` environment-variable
will be removed in Docker v27.0 after which this functionality is removed permanently.
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
docs: mark deprecation of "docker engine" subcommands Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 08:31:17 -05:00
### `docker engine` subcommands
docs/deprecated: remove minor versions Some deprecations are ammended during a major (YY.MM) release, to inform users as early as possible about deprecations. Removing the minor version from this overview clarifies that features are marked deprecated during which major release's lifecycle. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-02 08:15:42 -04:00
**Deprecated in Release: v19.03**
docs: mark deprecation of "docker engine" subcommands Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 08:31:17 -05:00
docs: update 20.03 -> 20.10 in deprecated.md Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-13 03:38:48 -04:00
**Removed in Release: v20.10**
docs: mark deprecation of "docker engine" subcommands Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 08:31:17 -05:00
The `docker engine activate`, `docker engine check`, and `docker engine update`
provided an alternative installation method to upgrade Docker Community engines
to Docker Enterprise, using an image-based distribution of the Docker Engine.
This feature was only available on Linux, and only when executed on a local node.
Given the limitations of this feature, and the feature not getting widely adopted,
the `docker engine` subcommands will be removed, in favor of installation through
standard package managers.
docs: mark deprecation of "dab" files and top-level "deploy" subcommand Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 08:30:24 -05:00
### Top-level `docker deploy` subcommand (experimental)
docs/deprecated: remove minor versions Some deprecations are ammended during a major (YY.MM) release, to inform users as early as possible about deprecations. Removing the minor version from this overview clarifies that features are marked deprecated during which major release's lifecycle. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-02 08:15:42 -04:00
**Deprecated in Release: v19.03**
docs: mark deprecation of "dab" files and top-level "deploy" subcommand Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 08:30:24 -05:00
docs: update 20.03 -> 20.10 in deprecated.md Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-13 03:38:48 -04:00
**Removed in Release: v20.10**
docs: mark deprecation of "dab" files and top-level "deploy" subcommand Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 08:30:24 -05:00
The top-level `docker deploy` command (using the "Docker Application Bundle"
(.dab) file format was introduced as an experimental feature in Docker 1.13 /
17.03, but superseded by support for Docker Compose files using the `docker stack deploy`
subcommand.
### `docker stack deploy` using "dab" files (experimental)
docs/deprecated: remove minor versions Some deprecations are ammended during a major (YY.MM) release, to inform users as early as possible about deprecations. Removing the minor version from this overview clarifies that features are marked deprecated during which major release's lifecycle. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-02 08:15:42 -04:00
**Deprecated in Release: v19.03**
docs: mark deprecation of "dab" files and top-level "deploy" subcommand Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 08:30:24 -05:00
docs: update 20.03 -> 20.10 in deprecated.md Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-13 03:38:48 -04:00
**Removed in Release: v20.10**
docs: mark deprecation of "dab" files and top-level "deploy" subcommand Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 08:30:24 -05:00
With no development being done on this feature, and no active use of the file
format, support for the DAB file format and the top-level docker deploy command
(hidden by default in 19.03), will be removed, in favour of `docker stack deploy`
using compose files.
docs: update deprecation status for "overlay2.override_kernel_check" Commit https://github.com/docker/docker/commit/955c1f881ac94af19c99f0f7d5635e6a574789f2 (v17.12.0) replaced detection of support for multiple lowerdirs (as required by overlay2) to not depend on the kernel version. The `overlay2.override_kernel_check` was still used to print a warning that older kernel versions may not have full support. After this, https://github.com/docker/docker/commit/e226aea280efdc18f887e853b5eefd763b602937 (v20.10, but backported to v19.03.7) removed uses of the option altogether. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-10-10 08:28:12 -04:00
### Support for the `overlay2.override_kernel_check` storage option
**Deprecated in Release: v19.03**
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
**Removed in Release: v24.0**
docs: update deprecation status for "overlay2.override_kernel_check" Commit https://github.com/docker/docker/commit/955c1f881ac94af19c99f0f7d5635e6a574789f2 (v17.12.0) replaced detection of support for multiple lowerdirs (as required by overlay2) to not depend on the kernel version. The `overlay2.override_kernel_check` was still used to print a warning that older kernel versions may not have full support. After this, https://github.com/docker/docker/commit/e226aea280efdc18f887e853b5eefd763b602937 (v20.10, but backported to v19.03.7) removed uses of the option altogether. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-10-10 08:28:12 -04:00
This daemon configuration option disabled the Linux kernel version check used
to detect if the kernel supported OverlayFS with multiple lower dirs, which is
required for the overlay2 storage driver. Starting with Docker v19.03.7, the
detection was improved to no longer depend on the kernel _version_, so this
option was no longer used.
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
### AuFS storage driver
docs/deprecated: remove minor versions Some deprecations are ammended during a major (YY.MM) release, to inform users as early as possible about deprecations. Removing the minor version from this overview clarifies that features are marked deprecated during which major release's lifecycle. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-02 08:15:42 -04:00
**Deprecated in Release: v19.03**
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
**Removed in Release: v24.0**
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
docs/deprecated: remove "disabled by default" for AuFS, overlay These drivers have been removed in docker 24.0, so it's no longer possible to enable them. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 19:10:17 -04:00
The `aufs` storage driver is deprecated in favor of `overlay2`, and has been
removed in a Docker Engine v24.0. Users of the `aufs` storage driver must
migrate to a different storage driver, such as `overlay2`, before upgrading
to Docker Engine v24.0.
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
docs/deprecated: remove "disabled by default" for AuFS, overlay These drivers have been removed in docker 24.0, so it's no longer possible to enable them. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 19:10:17 -04:00
The `aufs` storage driver facilitated running Docker on distros that have no
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
support for OverlayFS, such as Ubuntu 14.04 LTS, which originally shipped with
a 3.14 kernel.
Now that Ubuntu 14.04 is no longer a supported distro for Docker, and `overlay2`
is available to all supported distros (as they are either on kernel 4.x, or have
support for multiple lowerdirs backported), there is no reason to continue
maintenance of the `aufs` storage driver.
docs: update deprecation status of "overlay" and "AuFS" These drivers have been removed in Docker Engine 24.0.0 Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-04-20 17:47:37 -04:00
### Legacy overlay storage driver
Deprecate legacy overlay storage driver The `overlay` storage driver is deprecated in favor of the `overlay2` storage driver, which has all the benefits of `overlay`, without its limitations (excessive inode consumption). The legacy `overlay` storage driver will be removed in a future release. Users of the `overlay` storage driver should migrate to the `overlay2` storage driver. The legacy `overlay` storage driver allowed using overlayFS-backed filesystems on pre 4.x kernels. Now that all supported distributions are able to run `overlay2` (as they are either on kernel 4.x, or have support for multiple lowerdirs backported), there is no reason to keep maintaining the `overlay` storage driver. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2018-10-09 12:27:42 -04:00
docs/deprecated: remove minor versions Some deprecations are ammended during a major (YY.MM) release, to inform users as early as possible about deprecations. Removing the minor version from this overview clarifies that features are marked deprecated during which major release's lifecycle. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-02 08:15:42 -04:00
**Deprecated in Release: v18.09**
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
**Removed in Release: v24.0**
Deprecate legacy overlay storage driver The `overlay` storage driver is deprecated in favor of the `overlay2` storage driver, which has all the benefits of `overlay`, without its limitations (excessive inode consumption). The legacy `overlay` storage driver will be removed in a future release. Users of the `overlay` storage driver should migrate to the `overlay2` storage driver. The legacy `overlay` storage driver allowed using overlayFS-backed filesystems on pre 4.x kernels. Now that all supported distributions are able to run `overlay2` (as they are either on kernel 4.x, or have support for multiple lowerdirs backported), there is no reason to keep maintaining the `overlay` storage driver. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2018-10-09 12:27:42 -04:00
The `overlay` storage driver is deprecated in favor of the `overlay2` storage
driver, which has all the benefits of `overlay`, without its limitations (excessive
docs/deprecated: remove "disabled by default" for AuFS, overlay These drivers have been removed in docker 24.0, so it's no longer possible to enable them. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 19:10:17 -04:00
inode consumption). The legacy `overlay` storage driver has been removed in
Docker Engine v24.0. Users of the `overlay` storage driver should migrate to the
`overlay2` storage driver before upgrading to Docker Engine v24.0.
Deprecate legacy overlay storage driver The `overlay` storage driver is deprecated in favor of the `overlay2` storage driver, which has all the benefits of `overlay`, without its limitations (excessive inode consumption). The legacy `overlay` storage driver will be removed in a future release. Users of the `overlay` storage driver should migrate to the `overlay2` storage driver. The legacy `overlay` storage driver allowed using overlayFS-backed filesystems on pre 4.x kernels. Now that all supported distributions are able to run `overlay2` (as they are either on kernel 4.x, or have support for multiple lowerdirs backported), there is no reason to keep maintaining the `overlay` storage driver. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2018-10-09 12:27:42 -04:00
The legacy `overlay` storage driver allowed using overlayFS-backed filesystems
on pre 4.x kernels. Now that all supported distributions are able to run `overlay2`
(as they are either on kernel 4.x, or have support for multiple lowerdirs
backported), there is no reason to keep maintaining the `overlay` storage driver.
docs: minor touch-ups in "deprecated.md" Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 08:27:22 -05:00
### Device mapper storage driver
Deprecate "devicemapper" storage driver. The `devicemapper` storage driver is deprecated in favor of `overlay2`, and will be removed in a future release. Users of the `devicemapper` storage driver are recommended to migrate to a different storage driver, such as `overlay2`, which is now the default storage driver. The `devicemapper` storage driver facilitates running Docker on older (3.x) kernels that have no support for other storage drivers (such as overlay2, or AUFS). Now that support for `overlay2` is added to all supported distros (as they are either on kernel 4.x, or have support for multiple lowerdirs backported), there is no reason to continue maintenance of the `devicemapper` storage driver. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2018-10-09 12:51:13 -04:00
docs/deprecated: remove minor versions Some deprecations are ammended during a major (YY.MM) release, to inform users as early as possible about deprecations. Removing the minor version from this overview clarifies that features are marked deprecated during which major release's lifecycle. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-02 08:15:42 -04:00
**Deprecated in Release: v18.09**
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
**Disabled by default in Release: v23.0**
docs: remove devicemapper Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 19:42:52 -04:00
**Removed in Release: v25.0**
Deprecate "devicemapper" storage driver. The `devicemapper` storage driver is deprecated in favor of `overlay2`, and will be removed in a future release. Users of the `devicemapper` storage driver are recommended to migrate to a different storage driver, such as `overlay2`, which is now the default storage driver. The `devicemapper` storage driver facilitates running Docker on older (3.x) kernels that have no support for other storage drivers (such as overlay2, or AUFS). Now that support for `overlay2` is added to all supported distros (as they are either on kernel 4.x, or have support for multiple lowerdirs backported), there is no reason to continue maintenance of the `devicemapper` storage driver. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2018-10-09 12:51:13 -04:00
docs: remove devicemapper Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 19:42:52 -04:00
The `devicemapper` storage driver is deprecated in favor of `overlay2`, and has
been removed in Docker Engine v25.0. Users of the `devicemapper` storage driver
must migrate to a different storage driver, such as `overlay2`, before upgrading
to Docker Engine v25.0.
Deprecate "devicemapper" storage driver. The `devicemapper` storage driver is deprecated in favor of `overlay2`, and will be removed in a future release. Users of the `devicemapper` storage driver are recommended to migrate to a different storage driver, such as `overlay2`, which is now the default storage driver. The `devicemapper` storage driver facilitates running Docker on older (3.x) kernels that have no support for other storage drivers (such as overlay2, or AUFS). Now that support for `overlay2` is added to all supported distros (as they are either on kernel 4.x, or have support for multiple lowerdirs backported), there is no reason to continue maintenance of the `devicemapper` storage driver. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2018-10-09 12:51:13 -04:00
The `devicemapper` storage driver facilitates running Docker on older (3.x) kernels
docs/deprecated: remove "disabled by default" for AuFS, overlay These drivers have been removed in docker 24.0, so it's no longer possible to enable them. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 19:10:17 -04:00
that have no support for other storage drivers (such as overlay2, or btrfs).
Deprecate "devicemapper" storage driver. The `devicemapper` storage driver is deprecated in favor of `overlay2`, and will be removed in a future release. Users of the `devicemapper` storage driver are recommended to migrate to a different storage driver, such as `overlay2`, which is now the default storage driver. The `devicemapper` storage driver facilitates running Docker on older (3.x) kernels that have no support for other storage drivers (such as overlay2, or AUFS). Now that support for `overlay2` is added to all supported distros (as they are either on kernel 4.x, or have support for multiple lowerdirs backported), there is no reason to continue maintenance of the `devicemapper` storage driver. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2018-10-09 12:51:13 -04:00
Now that support for `overlay2` is added to all supported distros (as they are
either on kernel 4.x, or have support for multiple lowerdirs backported), there
is no reason to continue maintenance of the `devicemapper` storage driver.
Deprecate legacy overlay storage driver The `overlay` storage driver is deprecated in favor of the `overlay2` storage driver, which has all the benefits of `overlay`, without its limitations (excessive inode consumption). The legacy `overlay` storage driver will be removed in a future release. Users of the `overlay` storage driver should migrate to the `overlay2` storage driver. The legacy `overlay` storage driver allowed using overlayFS-backed filesystems on pre 4.x kernels. Now that all supported distributions are able to run `overlay2` (as they are either on kernel 4.x, or have support for multiple lowerdirs backported), there is no reason to keep maintaining the `overlay` storage driver. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2018-10-09 12:27:42 -04:00
deprecated: use of reserved namespaces for engine labels Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-11 11:06:55 -05:00
### Use of reserved namespaces in engine labels
Document that reserved namespaces org.docker.*, io.docker.*, and org.dockerproject.* in engine labels are now deprecated. Signed-off-by: Ying Li <ying.li@docker.com>
2018-05-07 14:10:13 -04:00
docs/deprecated: remove minor versions Some deprecations are ammended during a major (YY.MM) release, to inform users as early as possible about deprecations. Removing the minor version from this overview clarifies that features are marked deprecated during which major release's lifecycle. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-02 08:15:42 -04:00
**Deprecated in Release: v18.06**
Document that reserved namespaces org.docker.*, io.docker.*, and org.dockerproject.* in engine labels are now deprecated. Signed-off-by: Ying Li <ying.li@docker.com>
2018-05-07 14:10:13 -04:00
docs: update 20.03 -> 20.10 in deprecated.md Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-13 03:38:48 -04:00
**Removed In Release: v20.10**
deprecated: use of reserved namespaces for engine labels Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-11 11:06:55 -05:00
Document that reserved namespaces org.docker.*, io.docker.*, and org.dockerproject.* in engine labels are now deprecated. Signed-off-by: Ying Li <ying.li@docker.com>
2018-05-07 14:10:13 -04:00
The namespaces `com.docker.*`, `io.docker.*`, and `org.dockerproject.*` in engine labels
were always documented to be reserved, but there was never any enforcement.
Usage of these namespaces will now cause a warning in the engine logs to discourage their
docs: update 20.03 -> 20.10 in deprecated.md Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-13 03:38:48 -04:00
use, and will error instead in v20.10 and above.
Document that reserved namespaces org.docker.*, io.docker.*, and org.dockerproject.* in engine labels are now deprecated. Signed-off-by: Ying Li <ying.li@docker.com>
2018-05-07 14:10:13 -04:00
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
### `--disable-legacy-registry` override daemon option
**Disabled In Release: v17.12**
docs: update deprecated status for --disable-legacy-registry Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 10:52:21 -05:00
**Removed In Release: v19.03**
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
The `--disable-legacy-registry` flag was disabled in Docker 17.12 and will print
an error when used. For this error to be printed, the flag itself is still present,
docs: update deprecated status for --disable-legacy-registry Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 10:52:21 -05:00
but hidden. The flag has been removed in Docker 19.03.
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
### Interacting with V1 registries
**Disabled By Default In Release: v17.06**
**Removed In Release: v17.12**
Version 1.8.3 added a flag (`--disable-legacy-registry=false`) which prevents the
docker daemon from `pull`, `push`, and `login` operations against v1
registries. Though enabled by default, this signals the intent to deprecate
the v1 protocol.
Support for the v1 protocol to the public registry was removed in 1.13. Any
mirror configurations using v1 should be updated to use a
[v2 registry mirror](https://docs.docker.com/registry/recipes/mirror/).
Starting with Docker 17.12, support for V1 registries has been removed, and the
`--disable-legacy-registry` flag can no longer be used, and `dockerd` will fail to
start when set.
docs: minor touch-ups in "deprecated.md" Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 08:27:22 -05:00
### Asynchronous `service create` and `service update` as default
Deprecate "asynchronous" service create and service update Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2017-04-11 06:15:18 -04:00
docs/deprecated: remove minor versions Some deprecations are ammended during a major (YY.MM) release, to inform users as early as possible about deprecations. Removing the minor version from this overview clarifies that features are marked deprecated during which major release's lifecycle. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-02 08:15:42 -04:00
**Deprecated In Release: v17.05**
Deprecate "asynchronous" service create and service update Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2017-04-11 06:15:18 -04:00
Update deprecation for synchronous service updates - The default was not changed in 17.09 but will be in 17.10 - `service scale` and `service rollback` are also affected. Signed-off-by: Harald Albers <github@albersweb.de>
2017-10-07 08:28:56 -04:00
**Disabled by default in release: [v17.10](https://github.com/docker/docker-ce/releases/tag/v17.10.0-ce)**
Deprecate "asynchronous" service create and service update Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2017-04-11 06:15:18 -04:00
docs/deprecated: remove minor versions Some deprecations are ammended during a major (YY.MM) release, to inform users as early as possible about deprecations. Removing the minor version from this overview clarifies that features are marked deprecated during which major release's lifecycle. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-02 08:15:42 -04:00
Docker 17.05 added an optional `--detach=false` option to make the
Deprecate "asynchronous" service create and service update Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2017-04-11 06:15:18 -04:00
`docker service create` and `docker service update` work synchronously. This
Update deprecation for synchronous service updates - The default was not changed in 17.09 but will be in 17.10 - `service scale` and `service rollback` are also affected. Signed-off-by: Harald Albers <github@albersweb.de>
2017-10-07 08:28:56 -04:00
option will be enabled by default in Docker 17.10, at which point the `--detach`
Deprecate "asynchronous" service create and service update Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2017-04-11 06:15:18 -04:00
flag can be used to use the previous (asynchronous) behavior.
Update deprecation for synchronous service updates - The default was not changed in 17.09 but will be in 17.10 - `service scale` and `service rollback` are also affected. Signed-off-by: Harald Albers <github@albersweb.de>
2017-10-07 08:28:56 -04:00
The default for this option will also be changed accordingly for `docker service rollback`
and `docker service scale` in Docker 17.10.
Deprecate --graph flag; Replace with --data-root Docker-DCO-1.1-Signed-off-by: Josh Hawn <josh.hawn@docker.com> (github: jlhawn)
2016-11-22 01:17:24 -05:00
### `-g` and `--graph` flags on `dockerd`
docs/deprecated: remove minor versions Some deprecations are ammended during a major (YY.MM) release, to inform users as early as possible about deprecations. Removing the minor version from this overview clarifies that features are marked deprecated during which major release's lifecycle. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-02 08:15:42 -04:00
**Deprecated In Release: v17.05**
Deprecate --graph flag; Replace with --data-root Docker-DCO-1.1-Signed-off-by: Josh Hawn <josh.hawn@docker.com> (github: jlhawn)
2016-11-22 01:17:24 -05:00
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
**Removed In Release: v23.0**
complete the "-g" / "--graph" daemon option deprecation These options were soft-deprecated in Docker 17.05, and at the time considered to not be removed. However, with the move towards containerd snapshotters, having these options around adds additional complexity to handle fallbacks for deprecated (and hidden) flags, so completing the deprecation. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-08-18 04:44:00 -04:00
Deprecate --graph flag; Replace with --data-root Docker-DCO-1.1-Signed-off-by: Josh Hawn <josh.hawn@docker.com> (github: jlhawn)
2016-11-22 01:17:24 -05:00
The `-g` or `--graph` flag for the `dockerd` or `docker daemon` command was
used to indicate the directory in which to store persistent data and resource
configuration and has been replaced with the more descriptive `--data-root`
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
flag. These flags were deprecated and hidden in v17.05, and removed in v23.0.
Add conflict check for flags, and update deprecation versions Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2017-03-28 10:19:35 -04:00
deprecate "top-level" network information in NetworkSettings When inspecting a container, `NetworkSettings` contains top-level information about the default ("bridge") network; `EndpointID`, `Gateway`, `GlobalIPv6Address`, `GlobalIPv6PrefixLen`, `IPAddress`, `IPPrefixLen`, `IPv6Gateway`, and `MacAddress`. These properties are deprecated in favor of per-network properties in `NetworkSettings.Networks`. These properties were already "deprecated" in docker 1.9, but kept around for backward compatibility. Refer to [#17538](https://github.com/docker/docker/pull/17538) for further information. This officially deprecates these properties, and marks them for removal in 1.16 Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2016-11-15 09:41:52 -05:00
### Top-level network properties in NetworkSettings
Add missing link in deprecated.md This fix adds a missing link in deprecated.md ``` Deprecated In Release: [v1.13.0]... ``` Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
2017-02-12 18:15:15 -05:00
**Deprecated In Release: [v1.13.0](https://github.com/docker/docker/releases/tag/v1.13.0)**
deprecate "top-level" network information in NetworkSettings When inspecting a container, `NetworkSettings` contains top-level information about the default ("bridge") network; `EndpointID`, `Gateway`, `GlobalIPv6Address`, `GlobalIPv6PrefixLen`, `IPAddress`, `IPPrefixLen`, `IPv6Gateway`, and `MacAddress`. These properties are deprecated in favor of per-network properties in `NetworkSettings.Networks`. These properties were already "deprecated" in docker 1.9, but kept around for backward compatibility. Refer to [#17538](https://github.com/docker/docker/pull/17538) for further information. This officially deprecates these properties, and marks them for removal in 1.16 Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2016-11-15 09:41:52 -05:00
update deprecation dates Signed-off-by: Victor Vieux <victorvieux@gmail.com>
2017-02-27 20:16:47 -05:00
**Target For Removal In Release: v17.12**
deprecate "top-level" network information in NetworkSettings When inspecting a container, `NetworkSettings` contains top-level information about the default ("bridge") network; `EndpointID`, `Gateway`, `GlobalIPv6Address`, `GlobalIPv6PrefixLen`, `IPAddress`, `IPPrefixLen`, `IPv6Gateway`, and `MacAddress`. These properties are deprecated in favor of per-network properties in `NetworkSettings.Networks`. These properties were already "deprecated" in docker 1.9, but kept around for backward compatibility. Refer to [#17538](https://github.com/docker/docker/pull/17538) for further information. This officially deprecates these properties, and marks them for removal in 1.16 Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2016-11-15 09:41:52 -05:00
When inspecting a container, `NetworkSettings` contains top-level information
about the default ("bridge") network;
`EndpointID`, `Gateway`, `GlobalIPv6Address`, `GlobalIPv6PrefixLen`, `IPAddress`,
`IPPrefixLen`, `IPv6Gateway`, and `MacAddress`.
These properties are deprecated in favor of per-network properties in
`NetworkSettings.Networks`. These properties were already "deprecated" in
docker 1.9, but kept around for backward compatibility.
Refer to [#17538](https://github.com/docker/docker/pull/17538) for further
information.
Fix indenting in table of contents Fixes #30841. The "filter" section had the wrong header size, which caused sections following it to have the wrong indentation in the right-side table of contents. Signed-off-by: Greg Pflaum <gpflaum@users.noreply.github.com>
2017-03-22 22:48:34 -04:00
### `filter` param for `/images/json` endpoint
fix some version information Signed-off-by: Qinglan Peng <qinglanpeng@zju.edu.cn>
2016-12-08 06:03:46 -05:00
**Deprecated In Release: [v1.13.0](https://github.com/docker/docker/releases/tag/v1.13.0)**
Add reference filter and deprecated filter param… … for `docker images`. This deprecates the `filter` param for the `/images` endpoint and make a new filter called `reference` to replace it. It does change the CLI side (still possible to do `docker images busybox:musl`) but changes the cli code to use the filter instead (so that `docker images --filter busybox:musl` and `docker images busybox:musl` act the same). Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2016-11-11 09:34:01 -05:00
docs: update 20.03 -> 20.10 in deprecated.md Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-13 03:38:48 -04:00
**Removed In Release: v20.10**
Add reference filter and deprecated filter param… … for `docker images`. This deprecates the `filter` param for the `/images` endpoint and make a new filter called `reference` to replace it. It does change the CLI side (still possible to do `docker images busybox:musl`) but changes the cli code to use the filter instead (so that `docker images --filter busybox:musl` and `docker images busybox:musl` act the same). Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2016-11-11 09:34:01 -05:00
docs: update deprecation status of "filter" option Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 11:24:52 -05:00
The `filter` param to filter the list of image by reference (name or name:tag)
is now implemented as a regular filter, named `reference`.
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
### `repository:shortid` image references
fix some version information Signed-off-by: Qinglan Peng <qinglanpeng@zju.edu.cn>
2016-12-08 06:03:46 -05:00
**Deprecated In Release: [v1.13.0](https://github.com/docker/docker/releases/tag/v1.13.0)**
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
Updated deprecation status for "repository:shortid" The `repository:shortid` syntax for referencing images is very little used, collides with with tag references can be confused with digest references. The `repository:shortid` notation was deprecated in Docker 1.13, and scheduled for removal in Docker 17.12. This patch updates the deprecation status for this feature. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2017-12-13 17:16:46 -05:00
**Removed In Release: v17.12**
The `repository:shortid` syntax for referencing images is very little used,
collides with tag references, and can be confused with digest references.
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
Updated deprecation status for "repository:shortid" The `repository:shortid` syntax for referencing images is very little used, collides with with tag references can be confused with digest references. The `repository:shortid` notation was deprecated in Docker 1.13, and scheduled for removal in Docker 17.12. This patch updates the deprecation status for this feature. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2017-12-13 17:16:46 -05:00
Support for the `repository:shortid` notation to reference images was removed
in Docker 17.12.
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
### `docker daemon` subcommand
fix some version information Signed-off-by: Qinglan Peng <qinglanpeng@zju.edu.cn>
2016-12-08 06:03:46 -05:00
**Deprecated In Release: [v1.13.0](https://github.com/docker/docker/releases/tag/v1.13.0)**
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
Remove deprecated "daemon" subcommand The `docker daemon` subcommand was only present for backward compatibility, but deprecated in v1.13, and scheduled for removal in v17.12 Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2017-11-12 19:26:09 -05:00
**Removed In Release: v17.12**
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
The daemon is moved to a separate binary (`dockerd`), and should be used instead.
Remove duplicate keys in labels of `docker info` This fix tries to address the issue raised in 24392 where labels with duplicate keys exist in `docker info`, which contradicts with the specifications in the docs. The reason for duplicate keys is that labels are stored as slice of strings in the format of `A=B` (and the input/output). This fix tries to address this issue by checking conflict labels when daemon started, and remove duplicate labels (K-V). The existing `/info` API has not been changed. An additional integration test has been added to cover the changes in this fix. This fix fixes 24392. Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
2016-07-12 08:08:05 -04:00
### Duplicate keys with conflicting values in engine labels
fix some version information Signed-off-by: Qinglan Peng <qinglanpeng@zju.edu.cn>
2016-12-08 06:03:46 -05:00
**Deprecated In Release: [v1.13.0](https://github.com/docker/docker/releases/tag/v1.13.0)**
Remove duplicate keys in labels of `docker info` This fix tries to address the issue raised in 24392 where labels with duplicate keys exist in `docker info`, which contradicts with the specifications in the docs. The reason for duplicate keys is that labels are stored as slice of strings in the format of `A=B` (and the input/output). This fix tries to address this issue by checking conflict labels when daemon started, and remove duplicate labels (K-V). The existing `/info` API has not been changed. An additional integration test has been added to cover the changes in this fix. This fix fixes 24392. Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
2016-07-12 08:08:05 -04:00
Update docs and completion-scripts for deprecated features - the `--disable-legacy-registry` daemon flag was removed - duplicate keys with conflicting values for engine labels now produce an error instead of a warning. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2017-12-12 20:09:38 -05:00
**Removed In Release: v17.12**
Remove duplicate keys in labels of `docker info` This fix tries to address the issue raised in 24392 where labels with duplicate keys exist in `docker info`, which contradicts with the specifications in the docs. The reason for duplicate keys is that labels are stored as slice of strings in the format of `A=B` (and the input/output). This fix tries to address this issue by checking conflict labels when daemon started, and remove duplicate labels (K-V). The existing `/info` API has not been changed. An additional integration test has been added to cover the changes in this fix. This fix fixes 24392. Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
2016-07-12 08:08:05 -04:00
Update docs and completion-scripts for deprecated features - the `--disable-legacy-registry` daemon flag was removed - duplicate keys with conflicting values for engine labels now produce an error instead of a warning. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2017-12-12 20:09:38 -05:00
When setting duplicate keys with conflicting values, an error will be produced, and the daemon
will fail to start.
Remove duplicate keys in labels of `docker info` This fix tries to address the issue raised in 24392 where labels with duplicate keys exist in `docker info`, which contradicts with the specifications in the docs. The reason for duplicate keys is that labels are stored as slice of strings in the format of `A=B` (and the input/output). This fix tries to address this issue by checking conflict labels when daemon started, and remove duplicate labels (K-V). The existing `/info` API has not been changed. An additional integration test has been added to cover the changes in this fix. This fix fixes 24392. Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
2016-07-12 08:08:05 -04:00
Update docs/deprecated.md for 1.13 Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp>
2016-11-11 04:23:02 -05:00
### `MAINTAINER` in Dockerfile
fix some version information Signed-off-by: Qinglan Peng <qinglanpeng@zju.edu.cn>
2016-12-08 06:03:46 -05:00
**Deprecated In Release: [v1.13.0](https://github.com/docker/docker/releases/tag/v1.13.0)**
Update docs/deprecated.md for 1.13 Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp>
2016-11-11 04:23:02 -05:00
`MAINTAINER` was an early very limited form of `LABEL` which should be used instead.
### API calls without a version
fix some version information Signed-off-by: Qinglan Peng <qinglanpeng@zju.edu.cn>
2016-12-08 06:03:46 -05:00
**Deprecated In Release: [v1.13.0](https://github.com/docker/docker/releases/tag/v1.13.0)**
Update docs/deprecated.md for 1.13 Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp>
2016-11-11 04:23:02 -05:00
update deprecation dates Signed-off-by: Victor Vieux <victorvieux@gmail.com>
2017-02-27 20:16:47 -05:00
**Target For Removal In Release: v17.12**
Update docs/deprecated.md for 1.13 Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp>
2016-11-11 04:23:02 -05:00
API versions should be supplied to all API calls to ensure compatibility with
future Engine versions. Instead of just requesting, for example, the URL
`/containers/json`, you must now request `/v1.25/containers/json`.
### Backing filesystem without `d_type` support for overlay/overlay2
fix some version information Signed-off-by: Qinglan Peng <qinglanpeng@zju.edu.cn>
2016-12-08 06:03:46 -05:00
**Deprecated In Release: [v1.13.0](https://github.com/docker/docker/releases/tag/v1.13.0)**
Update docs/deprecated.md for 1.13 Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp>
2016-11-11 04:23:02 -05:00
Update docs and completion-scripts for deprecated features - the `--disable-legacy-registry` daemon flag was removed - duplicate keys with conflicting values for engine labels now produce an error instead of a warning. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2017-12-12 20:09:38 -05:00
**Removed In Release: v17.12**
Update docs/deprecated.md for 1.13 Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp>
2016-11-11 04:23:02 -05:00
The overlay and overlay2 storage driver does not work as expected if the backing
filesystem does not support `d_type`. For example, XFS does not support `d_type`
if it is formatted with the `ftype=0` option.
docs/deprecated: remove .patch release from deprecation status commit de8b696ed6cabdfa6f02516f875f4ed056f65efa removed the patch releases from the deprecation doc, but when we switched to the SemVer(ish) format for v23.0, we accidentally added them back. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-05-18 16:40:45 -04:00
Support for these setups has been removed, and Docker v23.0 and up now fails to
docs: update deprecation status for overlay(2) on backingfs without d_type Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-04-07 11:44:46 -04:00
start when attempting to use the `overlay2` or `overlay` storage driver on a
backing filesystem without `d_type` support.
Update docs and completion-scripts for deprecated features - the `--disable-legacy-registry` daemon flag was removed - duplicate keys with conflicting values for engine labels now produce an error instead of a warning. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2017-12-12 20:09:38 -05:00
docs: update deprecation status for overlay(2) on backingfs without d_type Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-04-07 11:44:46 -04:00
Refer to [#27358](https://github.com/docker/docker/issues/27358) for details.
Update docs/deprecated.md for 1.13 Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp>
2016-11-11 04:23:02 -05:00
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
### `--automated` and `--stars` flags on `docker search`
**Deprecated in Release: [v1.12.0](https://github.com/docker/docker/releases/tag/v1.12.0)**
docs: update 20.03 -> 20.10 in deprecated.md Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-10-13 03:38:48 -04:00
**Removed In Release: v20.10**
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
The `docker search --automated` and `docker search --stars` options are deprecated.
Remove deprecated docker search --automated and --stars flags The `docker search --automated` and `docker search --stars` options were deprecated in release v1.12.0, and scheduled for removal in v17.09. This patch removes the deprecated flags, in favor of their equivalent `--filter` options (`docker search --filter=is-automated=<true|false>` and `docker search --filter=stars=...`). Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-13 11:18:10 -05:00
Use `docker search --filter=is-automated=<true|false>` and `docker search --filter=stars=...` instead.
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
### `-h` shorthand for `--help`
**Deprecated In Release: [v1.12.0](https://github.com/docker/docker/releases/tag/v1.12.0)**
update deprecation dates Signed-off-by: Victor Vieux <victorvieux@gmail.com>
2017-02-27 20:16:47 -05:00
**Target For Removal In Release: v17.09**
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
The shorthand (`-h`) is less common than `--help` on Linux and cannot be used
on all subcommands (due to it conflicting with, e.g. `-h` / `--hostname` on
`docker create`). For this reason, the `-h` shorthand was not printed in the
"usage" output of subcommands, nor documented, and is now marked "deprecated".
### `-e` and `--email` flags on `docker login`
**Deprecated In Release: [v1.11.0](https://github.com/docker/docker/releases/tag/v1.11.0)**
Update deprecated.md for removal of --email flag Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit 43239f62bedc4721d27744d21c122622988bb3ae) Signed-off-by: Tibor Vass <tibor@docker.com>
2017-06-01 11:05:42 -04:00
**Removed In Release: [v17.06](https://github.com/docker/docker-ce/releases/tag/v17.06.0-ce)**
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
The docker login command is removing the ability to automatically register for an account with the target registry if the given username doesn't exist. Due to this change, the email flag is no longer required, and will be deprecated.
### Separator (`:`) of `--security-opt` flag on `docker run`
**Deprecated In Release: [v1.11.0](https://github.com/docker/docker/releases/tag/v1.11.0)**
update deprecation dates Signed-off-by: Victor Vieux <victorvieux@gmail.com>
2017-02-27 20:16:47 -05:00
**Target For Removal In Release: v17.06**
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
Docs: Add Spaces Around Parenthesis Where Needed Signed-off-by: Alex Mayer <amayer5125@gmail.com>
2018-09-28 17:40:22 -04:00
The flag `--security-opt` doesn't use the colon separator (`:`) anymore to divide keys and values, it uses the equal symbol (`=`) for consistency with other similar flags, like `--storage-opt`.
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
### Ambiguous event fields in API
**Deprecated In Release: [v1.10.0](https://github.com/docker/docker/releases/tag/v1.10.0)**
The fields `ID`, `Status` and `From` in the events API have been deprecated in favor of a more rich structure.
See the events API documentation for the new format.
### `-f` flag on `docker tag`
**Deprecated In Release: [v1.10.0](https://github.com/docker/docker/releases/tag/v1.10.0)**
**Removed In Release: [v1.12.0](https://github.com/docker/docker/releases/tag/v1.12.0)**
Update deprecated.md Signed-off-by: Dmitriy Fishman <fishman.code@gmail.com>
2021-09-30 11:12:46 -04:00
To make tagging consistent across the various `docker` commands, the `-f` flag on the `docker tag` command is deprecated. It is no longer necessary to specify `-f` to move a tag from one image to another. Nor will `docker` generate an error if the `-f` flag is missing and the specified tag is already in use.
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
### HostConfig at API container start
**Deprecated In Release: [v1.10.0](https://github.com/docker/docker/releases/tag/v1.10.0)**
**Removed In Release: [v1.12.0](https://github.com/docker/docker/releases/tag/v1.12.0)**
Passing an `HostConfig` to `POST /containers/{name}/start` is deprecated in favor of
defining it at container creation (`POST /containers/create`).
fix some version information Signed-off-by: Qinglan Peng <qinglanpeng@zju.edu.cn>
2016-12-08 06:03:46 -05:00
### `--before` and `--since` flags on `docker ps`
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
**Deprecated In Release: [v1.10.0](https://github.com/docker/docker/releases/tag/v1.10.0)**
**Removed In Release: [v1.12.0](https://github.com/docker/docker/releases/tag/v1.12.0)**
The `docker ps --before` and `docker ps --since` options are deprecated.
Use `docker ps --filter=before=...` and `docker ps --filter=since=...` instead.
docs: minor touch-ups in "deprecated.md" Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 08:27:22 -05:00
### Driver-specific log tags
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
**Deprecated In Release: [v1.9.0](https://github.com/docker/docker/releases/tag/v1.9.0)**
**Removed In Release: [v1.12.0](https://github.com/docker/docker/releases/tag/v1.12.0)**
Log tags are now generated in a standard way across different logging drivers.
Because of which, the driver specific log tag options `syslog-tag`, `gelf-tag` and
`fluentd-tag` have been deprecated in favor of the generic `tag` option.
docs: use "console" code-hint for shell examples This replaces the use of bash where suitable, to allow easier copy/pasting of shell examples without copying the prompt or process output. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2021-08-21 08:54:14 -04:00
```console
$ docker --log-driver=syslog --log-opt tag="{{.ImageName}}/{{.Name}}/{{.ID}}"
Fix some Liquid errors Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2017-02-14 19:40:15 -05:00
```
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
### Docker Content Trust ENV passphrase variables name change
**Deprecated In Release: [v1.9.0](https://github.com/docker/docker/releases/tag/v1.9.0)**
**Removed In Release: [v1.12.0](https://github.com/docker/docker/releases/tag/v1.12.0)**
Since 1.9, Docker Content Trust Offline key has been renamed to Root key and the Tagging key has been renamed to Repository key. Due to this renaming, we're also changing the corresponding environment variables
- DOCKER_CONTENT_TRUST_OFFLINE_PASSPHRASE is now named DOCKER_CONTENT_TRUST_ROOT_PASSPHRASE
- DOCKER_CONTENT_TRUST_TAGGING_PASSPHRASE is now named DOCKER_CONTENT_TRUST_REPOSITORY_PASSPHRASE
### `/containers/(id or name)/copy` endpoint
**Deprecated In Release: [v1.8.0](https://github.com/docker/docker/releases/tag/v1.8.0)**
**Removed In Release: [v1.12.0](https://github.com/docker/docker/releases/tag/v1.12.0)**
The endpoint `/containers/(id or name)/copy` is deprecated in favor of `/containers/(id or name)/archive`.
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
### LXC built-in exec driver
**Deprecated In Release: [v1.8.0](https://github.com/docker/docker/releases/tag/v1.8.0)**
**Removed In Release: [v1.10.0](https://github.com/docker/docker/releases/tag/v1.10.0)**
The built-in LXC execution driver, the lxc-conf flag, and API fields have been removed.
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
### Old Command Line Options
**Deprecated In Release: [v1.8.0](https://github.com/docker/docker/releases/tag/v1.8.0)**
**Removed In Release: [v1.10.0](https://github.com/docker/docker/releases/tag/v1.10.0)**
The flags `-d` and `--daemon` are deprecated in favor of the `daemon` subcommand:
docker daemon -H ...
The following single-dash (`-opt`) variant of certain command line options
are deprecated and replaced with double-dash options (`--opt`):
docker attach -nostdin
docker attach -sig-proxy
docker build -no-cache
docker build -rm
docker commit -author
docker commit -run
docker events -since
docker history -notrunc
docker images -notrunc
docker inspect -format
docker ps -beforeId
docker ps -notrunc
docker ps -sinceId
docker rm -link
docker run -cidfile
docker run -dns
docker run -entrypoint
docker run -expose
docker run -link
docker run -lxc-conf
docker run -n
docker run -privileged
docker run -volumes-from
docker search -notrunc
docker search -stars
docker search -t
docker search -trusted
docker tag -force
The following double-dash options are deprecated and have no replacement:
docker run --cpuset
docker run --networking
docker ps --since-id
docker ps --before-id
docker search --trusted
**Deprecated In Release: [v1.5.0](https://github.com/docker/docker/releases/tag/v1.5.0)**
**Removed In Release: [v1.12.0](https://github.com/docker/docker/releases/tag/v1.12.0)**
The single-dash (`-help`) was removed, in favor of the double-dash `--help`
docker -help
docker [COMMAND] -help
Update deprecation notes about v1 registry Adds section about the hub deprecating the v1 protocol. Adds note about intent to disable by default and remove support. Signed-off-by: Derek McGowan <derek@mcgstyle.net> (github: dmcgowan)
2016-11-21 12:39:48 -05:00
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
### `--api-enable-cors` flag on dockerd
Update deprecation notes about v1 registry Adds section about the hub deprecating the v1 protocol. Adds note about intent to disable by default and remove support. Signed-off-by: Derek McGowan <derek@mcgstyle.net> (github: dmcgowan)
2016-11-21 12:39:48 -05:00
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
**Deprecated In Release: [v1.6.0](https://github.com/docker/docker/releases/tag/v1.6.0)**
Update deprecation notes about v1 registry Adds section about the hub deprecating the v1 protocol. Adds note about intent to disable by default and remove support. Signed-off-by: Derek McGowan <derek@mcgstyle.net> (github: dmcgowan)
2016-11-21 12:39:48 -05:00
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
**Removed In Release: [v17.09](https://github.com/docker/docker-ce/releases/tag/v17.09.0-ce)**
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
The flag `--api-enable-cors` is deprecated since v1.6.0. Use the flag
`--api-cors-header` instead.
Update docs and completion-scripts for deprecated features - the `--disable-legacy-registry` daemon flag was removed - duplicate keys with conflicting values for engine labels now produce an error instead of a warning. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2017-12-12 20:09:38 -05:00
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
### `--run` flag on docker commit
Update docs and completion-scripts for deprecated features - the `--disable-legacy-registry` daemon flag was removed - duplicate keys with conflicting values for engine labels now produce an error instead of a warning. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2017-12-12 20:09:38 -05:00
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
**Deprecated In Release: [v0.10.0](https://github.com/docker/docker/releases/tag/v0.10.0)**
Update docs and completion-scripts for deprecated features - the `--disable-legacy-registry` daemon flag was removed - duplicate keys with conflicting values for engine labels now produce an error instead of a warning. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2017-12-12 20:09:38 -05:00
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
**Removed In Release: [v1.13.0](https://github.com/docker/docker/releases/tag/v1.13.0)**
Update docs and completion-scripts for deprecated features - the `--disable-legacy-registry` daemon flag was removed - duplicate keys with conflicting values for engine labels now produce an error instead of a warning. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2017-12-12 20:09:38 -05:00
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
The flag `--run` of the docker commit (and its short version `-run`) were deprecated in favor
of the `--changes` flag that allows to pass `Dockerfile` commands.
Update docs and completion-scripts for deprecated features - the `--disable-legacy-registry` daemon flag was removed - duplicate keys with conflicting values for engine labels now produce an error instead of a warning. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2017-12-12 20:09:38 -05:00
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
### Three arguments form in `docker import`
**Deprecated In Release: [v0.6.7](https://github.com/docker/docker/releases/tag/v0.6.7)**
Add a link to the new build instructions Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2016-10-12 19:23:01 -04:00
**Removed In Release: [v1.12.0](https://github.com/docker/docker/releases/tag/v1.12.0)**
docs: sort "deprecated.md" by deprecation release Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-10 09:03:42 -05:00
The `docker import` command format `file|URL|- [REPOSITORY [TAG]]` is deprecated since November 2013. It's no more supported.