1 files changed, 82 insertions, 0 deletions
diff --git a/devdocs/docker/engine%2Fdeprecated%2Findex.html b/devdocs/docker/engine%2Fdeprecated%2Findex.html
new file mode 100644
index 00000000..559fb679
--- /dev/null
+++ b/devdocs/docker/engine%2Fdeprecated%2Findex.html
@@ -0,0 +1,82 @@
+ <h1 id="deprecated-engine-features">Deprecated Engine Features</h1> <p>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 <a href="../release-notes/index">release notes</a>.</p> <h2 id="feature-deprecation-policy">Feature Deprecation Policy</h2> <p>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 at least one stable release unless specified explicitly otherwise. After that time it may be removed.</p> <p>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.</p> <h2 id="deprecated-engine-features-1">Deprecated Engine Features</h2> <p>The table below provides an overview of the current status of deprecated features:</p> <ul> <li>
+<strong>Deprecated</strong>: 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 <em>“Deprecated”</em> column contains the release in which the feature was marked deprecated, whereas the <em>“Remove”</em> column contains a tentative release in which the feature is to be removed. If no release is included in the <em>“Remove”</em> column, the release is yet to be decided on.</li> <li>
+<strong>Removed</strong>: 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.</li> </ul> <table> <thead> <tr> <th>Status</th> <th>Feature</th> <th>Deprecated</th> <th>Remove</th> </tr> </thead> <tbody> <tr> <td>Deprecated</td> <td><a href="#support-for-encrypted-tls-private-keys">Support for encrypted TLS private keys</a></td> <td>v20.10</td> <td>-</td> </tr> <tr> <td>Deprecated</td> <td><a href="#kubernetes-stack-and-context-support">Kubernetes stack and context support</a></td> <td>v20.10</td> <td>-</td> </tr> <tr> <td>Deprecated</td> <td><a href="#pulling-images-from-non-compliant-image-registries">Pulling images from non-compliant image registries</a></td> <td>v20.10</td> <td>-</td> </tr> <tr> <td>Deprecated</td> <td><a href="#linux-containers-on-windows-lcow-experimental">Linux containers on Windows (LCOW)</a></td> <td>v20.10</td> <td>-</td> </tr> <tr> <td>Deprecated</td> <td><a href="#blkio-weight-options-with-cgroups-v1">BLKIO weight options with cgroups v1</a></td> <td>v20.10</td> <td>-</td> </tr> <tr> <td>Deprecated</td> <td><a href="#kernel-memory-limit">Kernel memory limit</a></td> <td>v20.10</td> <td>-</td> </tr> <tr> <td>Deprecated</td> <td><a href="#classic-swarm-and-overlay-networks-using-cluster-store">Classic Swarm and overlay networks using external key/value stores</a></td> <td>v20.10</td> <td>-</td> </tr> <tr> <td>Deprecated</td> <td><a href="#support-for-legacy-dockercfg-configuration-files">Support for the legacy <code class="language-plaintext highlighter-rouge">~/.dockercfg</code> configuration file for authentication</a></td> <td>v20.10</td> <td>-</td> </tr> <tr> <td>Deprecated</td> <td><a href="#cli-plugins-support">CLI plugins support</a></td> <td>v20.10</td> <td>-</td> </tr> <tr> <td>Deprecated</td> <td><a href="#dockerfile-legacy-env-name-value-syntax">Dockerfile legacy <code class="language-plaintext highlighter-rouge">ENV name value</code> syntax</a></td> <td>v20.10</td> <td>-</td> </tr> <tr> <td>Removed</td> <td><a href="#docker-build---stream-flag-experimental"><code class="language-plaintext highlighter-rouge">docker build --stream</code> flag (experimental)</a></td> <td>v20.10</td> <td>v20.10</td> </tr> <tr> <td>Deprecated</td> <td><a href="#fluentd-async-connect-log-opt"><code class="language-plaintext highlighter-rouge">fluentd-async-connect</code> log opt</a></td> <td>v20.10</td> <td>-</td> </tr> <tr> <td>Deprecated</td> <td><a href="#configuration-options-for-experimental-cli-features">Configuration options for experimental CLI features</a></td> <td>v19.03</td> <td>v20.10</td> </tr> <tr> <td>Deprecated</td> <td><a href="#pushing-and-pulling-with-image-manifest-v2-schema-1">Pushing and pulling with image manifest v2 schema 1</a></td> <td>v19.03</td> <td>v20.10</td> </tr> <tr> <td>Removed</td> <td><a href="#docker-engine-subcommands"><code class="language-plaintext highlighter-rouge">docker engine</code> subcommands</a></td> <td>v19.03</td> <td>v20.10</td> </tr> <tr> <td>Removed</td> <td><a href="#top-level-docker-deploy-subcommand-experimental">Top-level <code class="language-plaintext highlighter-rouge">docker deploy</code> subcommand (experimental)</a></td> <td>v19.03</td> <td>v20.10</td> </tr> <tr> <td>Removed</td> <td><a href="#docker-stack-deploy-using-dab-files-experimental"><code class="language-plaintext highlighter-rouge">docker stack deploy</code> using “dab” files (experimental)</a></td> <td>v19.03</td> <td>v20.10</td> </tr> <tr> <td>Deprecated</td> <td><a href="#aufs-storage-driver">AuFS storage driver</a></td> <td>v19.03</td> <td>-</td> </tr> <tr> <td>Deprecated</td> <td><a href="#legacy-overlay-storage-driver">Legacy “overlay” storage driver</a></td> <td>v18.09</td> <td>-</td> </tr> <tr> <td>Deprecated</td> <td><a href="#device-mapper-storage-driver">Device mapper storage driver</a></td> <td>v18.09</td> <td>-</td> </tr> <tr> <td>Removed</td> <td><a href="#use-of-reserved-namespaces-in-engine-labels">Use of reserved namespaces in engine labels</a></td> <td>v18.06</td> <td>v20.10</td> </tr> <tr> <td>Removed</td> <td><a href="#--disable-legacy-registry-override-daemon-option"><code class="language-plaintext highlighter-rouge">--disable-legacy-registry</code> override daemon option</a></td> <td>v17.12</td> <td>v19.03</td> </tr> <tr> <td>Removed</td> <td><a href="#interacting-with-v1-registries">Interacting with V1 registries</a></td> <td>v17.06</td> <td>v17.12</td> </tr> <tr> <td>Removed</td> <td><a href="#asynchronous-service-create-and-service-update-as-default">Asynchronous <code class="language-plaintext highlighter-rouge">service create</code> and <code class="language-plaintext highlighter-rouge">service update</code> as default</a></td> <td>v17.05</td> <td>v17.10</td> </tr> <tr> <td>Removed</td> <td><a href="#-g-and---graph-flags-on-dockerd"><code class="language-plaintext highlighter-rouge">-g</code> and <code class="language-plaintext highlighter-rouge">--graph</code> flags on <code class="language-plaintext highlighter-rouge">dockerd</code></a></td> <td>v17.05</td> <td>-</td> </tr> <tr> <td>Deprecated</td> <td><a href="#top-level-network-properties-in-networksettings">Top-level network properties in NetworkSettings</a></td> <td>v1.13</td> <td>v17.12</td> </tr> <tr> <td>Removed</td> <td><a href="#filter-param-for-imagesjson-endpoint"><code class="language-plaintext highlighter-rouge">filter</code> param for <code class="language-plaintext highlighter-rouge">/images/json</code> endpoint</a></td> <td>v1.13</td> <td>v20.10</td> </tr> <tr> <td>Removed</td> <td><a href="#repositoryshortid-image-references"><code class="language-plaintext highlighter-rouge">repository:shortid</code> image references</a></td> <td>v1.13</td> <td>v17.12</td> </tr> <tr> <td>Removed</td> <td><a href="#docker-daemon-subcommand"><code class="language-plaintext highlighter-rouge">docker daemon</code> subcommand</a></td> <td>v1.13</td> <td>v17.12</td> </tr> <tr> <td>Removed</td> <td><a href="#duplicate-keys-with-conflicting-values-in-engine-labels">Duplicate keys with conflicting values in engine labels</a></td> <td>v1.13</td> <td>v17.12</td> </tr> <tr> <td>Deprecated</td> <td><a href="#maintainer-in-dockerfile"><code class="language-plaintext highlighter-rouge">MAINTAINER</code> in Dockerfile</a></td> <td>v1.13</td> <td>-</td> </tr> <tr> <td>Deprecated</td> <td><a href="#api-calls-without-a-version">API calls without a version</a></td> <td>v1.13</td> <td>v17.12</td> </tr> <tr> <td>Removed</td> <td><a href="#backing-filesystem-without-d_type-support-for-overlayoverlay2">Backing filesystem without <code class="language-plaintext highlighter-rouge">d_type</code> support for overlay/overlay2</a></td> <td>v1.13</td> <td>v17.12</td> </tr> <tr> <td>Removed</td> <td><a href="#--automated-and---stars-flags-on-docker-search"><code class="language-plaintext highlighter-rouge">--automated</code> and <code class="language-plaintext highlighter-rouge">--stars</code> flags on <code class="language-plaintext highlighter-rouge">docker search</code></a></td> <td>v1.12</td> <td>v20.10</td> </tr> <tr> <td>Deprecated</td> <td><a href="#-h-shorthand-for---help"><code class="language-plaintext highlighter-rouge">-h</code> shorthand for <code class="language-plaintext highlighter-rouge">--help</code></a></td> <td>v1.12</td> <td>v17.09</td> </tr> <tr> <td>Removed</td> <td><a href="#-e-and---email-flags-on-docker-login"><code class="language-plaintext highlighter-rouge">-e</code> and <code class="language-plaintext highlighter-rouge">--email</code> flags on <code class="language-plaintext highlighter-rouge">docker login</code></a></td> <td>v1.11</td> <td>v17.06</td> </tr> <tr> <td>Deprecated</td> <td><a href="#separator--of---security-opt-flag-on-docker-run">Separator (<code class="language-plaintext highlighter-rouge">:</code>) of <code class="language-plaintext highlighter-rouge">--security-opt</code> flag on <code class="language-plaintext highlighter-rouge">docker run</code></a></td> <td>v1.11</td> <td>v17.06</td> </tr> <tr> <td>Deprecated</td> <td><a href="#ambiguous-event-fields-in-api">Ambiguous event fields in API</a></td> <td>v1.10</td> <td>-</td> </tr> <tr> <td>Removed</td> <td><a href="#-f-flag-on-docker-tag"><code class="language-plaintext highlighter-rouge">-f</code> flag on <code class="language-plaintext highlighter-rouge">docker tag</code></a></td> <td>v1.10</td> <td>v1.12</td> </tr> <tr> <td>Removed</td> <td><a href="#hostconfig-at-api-container-start">HostConfig at API container start</a></td> <td>v1.10</td> <td>v1.12</td> </tr> <tr> <td>Removed</td> <td><a href="#--before-and---since-flags-on-docker-ps"><code class="language-plaintext highlighter-rouge">--before</code> and <code class="language-plaintext highlighter-rouge">--since</code> flags on <code class="language-plaintext highlighter-rouge">docker ps</code></a></td> <td>v1.10</td> <td>v1.12</td> </tr> <tr> <td>Removed</td> <td><a href="#driver-specific-log-tags">Driver-specific log tags</a></td> <td>v1.9</td> <td>v1.12</td> </tr> <tr> <td>Removed</td> <td><a href="#docker-content-trust-env-passphrase-variables-name-change">Docker Content Trust <code class="language-plaintext highlighter-rouge">ENV</code> passphrase variables name change</a></td> <td>v1.9</td> <td>v1.12</td> </tr> <tr> <td>Removed</td> <td><a href="#containersid-or-namecopy-endpoint"><code class="language-plaintext highlighter-rouge">/containers/(id or name)/copy</code> endpoint</a></td> <td>v1.8</td> <td>v1.12</td> </tr> <tr> <td>Removed</td> <td><a href="#lxc-built-in-exec-driver">LXC built-in exec driver</a></td> <td>v1.8</td> <td>v1.10</td> </tr> <tr> <td>Removed</td> <td><a href="#old-command-line-options">Old Command Line Options</a></td> <td>v1.8</td> <td>v1.10</td> </tr> <tr> <td>Removed</td> <td><a href="#--api-enable-cors-flag-on-dockerd"><code class="language-plaintext highlighter-rouge">--api-enable-cors</code> flag on <code class="language-plaintext highlighter-rouge">dockerd</code></a></td> <td>v1.6</td> <td>v17.09</td> </tr> <tr> <td>Removed</td> <td><a href="#--run-flag-on-docker-commit"><code class="language-plaintext highlighter-rouge">--run</code> flag on <code class="language-plaintext highlighter-rouge">docker commit</code></a></td> <td>v0.10</td> <td>v1.13</td> </tr> <tr> <td>Removed</td> <td><a href="#three-arguments-form-in-docker-import">Three arguments form in <code class="language-plaintext highlighter-rouge">docker import</code></a></td> <td>v0.6.7</td> <td>v1.12</td> </tr> </tbody> </table> <h3 id="support-for-encrypted-tls-private-keys">Support for encrypted TLS private keys</h3> <p><strong>Deprecated in Release: v20.10</strong></p> <p>Use of encrypted TLS private keys has been deprecated, and will be removed in a future release. Golang has deprecated support for legacy PEM encryption (as specified in <a href="https://datatracker.ietf.org/doc/html/rfc1423">RFC 1423</a>), as it is insecure by design (see <a href="https://go-review.googlesource.com/c/go/+/264159">https://go-review.googlesource.com/c/go/+/264159</a>).</p> <h3 id="kubernetes-stack-and-context-support">Kubernetes stack and context support</h3> <p><strong>Deprecated in Release: v20.10</strong></p> <p>Following the deprecation of <a href="https://github.com/docker/compose-on-kubernetes">Compose on Kubernetes</a>, support for Kubernetes in the <code class="language-plaintext highlighter-rouge">stack</code> and <code class="language-plaintext highlighter-rouge">context</code> commands in the docker CLI is now marked as deprecated as well.</p> <h3 id="pulling-images-from-non-compliant-image-registries">Pulling images from non-compliant image registries</h3> <p><strong>Deprecated in Release: v20.10</strong></p> <p>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 <a href="https://github.com/opencontainers/distribution-spec">Open Container Initiative Distribution Specification</a>.</p> <p>While most registries conform to the specification, we encountered some registries to be non-compliant, resulting in <code class="language-plaintext highlighter-rouge">docker pull</code> to fail.</p> <p>As a temporary solution, Docker Engine v20.10 includes a fallback mechanism to allow <code class="language-plaintext highlighter-rouge">docker pull</code> to be functional when using a non-compliant registry. A warning message is printed in this situation:</p> <div class="highlight"><pre class="highlight" data-language="">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.
+</pre></div> <p>The fallback is added to allow users to either migrate their images to a compliant registry, or for these registries to become compliant.</p> <p>Note that this fallback only addresses failures on <code class="language-plaintext highlighter-rouge">docker pull</code>. Other commands, such as <code class="language-plaintext highlighter-rouge">docker stack deploy</code>, or pulling images with <code class="language-plaintext highlighter-rouge">containerd</code> will continue to fail.</p> <p>Given that other functionality is still broken with these registries, we consider this fallback a <em>temporary</em> solution, and will remove the fallback in an upcoming major release.</p> <h3 id="linux-containers-on-windows-lcow-experimental">Linux containers on Windows (LCOW) (experimental)</h3> <p><strong>Deprecated in Release: v20.10</strong></p> <p>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.</p> <p>Developers who want to run Linux workloads on a Windows host are encouraged to use <a href="https://docs.docker.com/docker-for-windows/wsl/">Docker Desktop with WSL2</a> instead.</p> <h3 id="blkio-weight-options-with-cgroups-v1">BLKIO weight options with cgroups v1</h3> <p><strong>Deprecated in Release: v20.10</strong></p> <p>Specifying blkio weight (<code class="language-plaintext highlighter-rouge">docker run --blkio-weight</code> and <code class="language-plaintext highlighter-rouge">docker run --blkio-weight-device</code>) is now marked as deprecated when using cgroups v1 because the corresponding features were <a href="https://github.com/torvalds/linux/commit/f382fb0bcef4c37dc049e9f6963e3baf204d815c">removed in Linux kernel v5.0 and up</a>. When using cgroups v2, the <code class="language-plaintext highlighter-rouge">--blkio-weight</code> options are implemented using <a href="https://github.com/torvalds/linux/blob/v5.0/Documentation/admin-guide/cgroup-v2.rst#io">`io.weight</a>.</p> <h3 id="kernel-memory-limit">Kernel memory limit</h3> <p><strong>Deprecated in Release: v20.10</strong></p> <p>Specifying kernel memory limit (<code class="language-plaintext highlighter-rouge">docker run --kernel-memory</code>) is now marked as deprecated, as <a href="https://github.com/torvalds/linux/commit/0158115f702b0ba208ab0b5adf44cae99b3ebcc7">Linux kernel deprecated <code class="language-plaintext highlighter-rouge">kmem.limit_in_bytes</code> in v5.4</a>.</p> <h3 id="classic-swarm-and-overlay-networks-using-cluster-store">Classic Swarm and overlay networks using cluster store</h3> <p><strong>Deprecated in Release: v20.10</strong></p> <p>Standalone (“classic”) Swarm has been deprecated, and with that the use of overlay networks using an external key/value store. The corresponding<code class="language-plaintext highlighter-rouge">--cluster-advertise</code>, <code class="language-plaintext highlighter-rouge">--cluster-store</code>, and <code class="language-plaintext highlighter-rouge">--cluster-store-opt</code> daemon options have been marked deprecated, and will be disabled or removed in a future release.</p> <h3 id="support-for-legacy-dockercfg-configuration-files">Support for legacy <code class="language-plaintext highlighter-rouge">~/.dockercfg</code> configuration files</h3> <p><strong>Deprecated in Release: v20.10</strong></p> <p>The docker CLI up until v1.7.0 used the <code class="language-plaintext highlighter-rouge">~/.dockercfg</code> file to store credentials after authenticating to a registry (<code class="language-plaintext highlighter-rouge">docker login</code>). Docker v1.7.0 replaced this file with a new CLI configuration file, located in <code class="language-plaintext highlighter-rouge">~/.docker/config.json</code>. 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.</p> <p>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.</p> <h3 id="configuration-options-for-experimental-cli-features">Configuration options for experimental CLI features</h3> <p>The <code class="language-plaintext highlighter-rouge">DOCKER_CLI_EXPERIMENTAL</code> environment variable and the corresponding <code class="language-plaintext highlighter-rouge">experimental</code> field in the CLI configuration file are deprecated. Experimental features will be enabled by default, and these configuration options will no longer be functional.</p> <h3 id="cli-plugins-support">CLI plugins support</h3> <p><strong>Deprecated in Release: v20.10</strong></p> <p>CLI Plugin API is now marked as deprecated.</p> <h3 id="dockerfile-legacy-env-name-value-syntax">Dockerfile legacy <code class="language-plaintext highlighter-rouge">ENV name value</code> syntax</h3> <p><strong>Deprecated in Release: v20.10</strong></p> <p>The Dockerfile <code class="language-plaintext highlighter-rouge">ENV</code> instruction allows values to be set using either <code class="language-plaintext highlighter-rouge">ENV name=value</code> or <code class="language-plaintext highlighter-rouge">ENV name value</code>. The latter (<code class="language-plaintext highlighter-rouge">ENV name value</code>) form can be ambiguous, for example, the following defines a single env-variable (<code class="language-plaintext highlighter-rouge">ONE</code>) with value <code class="language-plaintext highlighter-rouge">"TWO= THREE=world"</code>, but may have intended to be setting three env-vars:</p> <div class="highlight"><pre class="highlight" data-language="">ENV ONE TWO= THREE=world
+</pre></div> <p>This format also does not allow setting multiple environment-variables in a single <code class="language-plaintext highlighter-rouge">ENV</code> line in the Dockerfile.</p> <p>Use of the <code class="language-plaintext highlighter-rouge">ENV name value</code> syntax is discouraged, and may be removed in a future release. Users are encouraged to update their Dockerfiles to use the <code class="language-plaintext highlighter-rouge">ENV name=value</code> syntax, for example:</p> <div class="highlight"><pre class="highlight" data-language="">ENV ONE="" TWO="" THREE="world"
+</pre></div> <h3 id="docker-build---stream-flag-experimental">
+<code class="language-plaintext highlighter-rouge">docker build --stream</code> flag (experimental)</h3> <p><strong>Deprecated in Release: v20.10</strong> <strong>Removed in Release: v20.10</strong></p> <p>Docker v17.07 introduced an experimental <code class="language-plaintext highlighter-rouge">--stream</code> flag on <code class="language-plaintext highlighter-rouge">docker build</code> which allowed the build-context to be incrementally sent to the daemon, instead of unconditionally sending the whole build-context.</p> <p>This functionality has been reimplemented as part of BuildKit, which uses streaming by default and the <code class="language-plaintext highlighter-rouge">--stream</code> option will be ignored when using the classic builder, printing a deprecation warning instead.</p> <p>Users that want to use this feature are encouraged to enable BuildKit by setting the <code class="language-plaintext highlighter-rouge">DOCKER_BUILDKIT=1</code> environment variable or through the daemon or CLI configuration files.</p> <h3 id="fluentd-async-connect-log-opt">
+<code class="language-plaintext highlighter-rouge">fluentd-async-connect</code> log opt</h3> <p><strong>Deprecated in Release: v20.10</strong></p> <p>The <code class="language-plaintext highlighter-rouge">--log-opt fluentd-async-connect</code> option for the fluentd logging driver is <a href="https://github.com/moby/moby/pull/39086">deprecated in favor of <code class="language-plaintext highlighter-rouge">--log-opt fluentd-async</code></a>. A deprecation message is logged in the daemon logs if the old option is used:</p> <div class="highlight"><pre class="highlight" data-language="">fluent#New: AsyncConnect is now deprecated, please use Async instead
+</pre></div> <p>Users are encouraged to use the <code class="language-plaintext highlighter-rouge">fluentd-async</code> option going forward, as support for the old option will be removed in a future release.</p> <h3 id="pushing-and-pulling-with-image-manifest-v2-schema-1">Pushing and pulling with image manifest v2 schema 1</h3> <p><strong>Deprecated in Release: v19.03</strong></p> <p><strong>Target For Removal In Release: v20.10</strong></p> <p>The image manifest <a href="https://github.com/docker/distribution/blob/fda42e5ef908bdba722d435ff1f330d40dfcd56c/docs/spec/manifest-v2-1/">v2 schema 1</a> format is deprecated in favor of the <a href="https://github.com/docker/distribution/blob/fda42e5ef908bdba722d435ff1f330d40dfcd56c/docs/spec/manifest-v2-2/">v2 schema 2</a> format.</p> <p>If the registry you are using still supports v2 schema 1, urge their administrators to move to v2 schema 2.</p> <h3 id="docker-engine-subcommands">
+<code class="language-plaintext highlighter-rouge">docker engine</code> subcommands</h3> <p><strong>Deprecated in Release: v19.03</strong></p> <p><strong>Removed in Release: v20.10</strong></p> <p>The <code class="language-plaintext highlighter-rouge">docker engine activate</code>, <code class="language-plaintext highlighter-rouge">docker engine check</code>, and <code class="language-plaintext highlighter-rouge">docker engine update</code> provided an alternative installation method to upgrade Docker Community engines to Docker Enterprise, using an image-based distribution of the Docker Engine.</p> <p>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 <code class="language-plaintext highlighter-rouge">docker engine</code> subcommands will be removed, in favor of installation through standard package managers.</p> <h3 id="top-level-docker-deploy-subcommand-experimental">Top-level <code class="language-plaintext highlighter-rouge">docker deploy</code> subcommand (experimental)</h3> <p><strong>Deprecated in Release: v19.03</strong></p> <p><strong>Removed in Release: v20.10</strong></p> <p>The top-level <code class="language-plaintext highlighter-rouge">docker deploy</code> 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 <code class="language-plaintext highlighter-rouge">docker stack deploy</code> subcommand.</p> <h3 id="docker-stack-deploy-using-dab-files-experimental">
+<code class="language-plaintext highlighter-rouge">docker stack deploy</code> using “dab” files (experimental)</h3> <p><strong>Deprecated in Release: v19.03</strong></p> <p><strong>Removed in Release: v20.10</strong></p> <p>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 <code class="language-plaintext highlighter-rouge">docker stack deploy</code> using compose files.</p> <h3 id="aufs-storage-driver">AuFS storage driver</h3> <p><strong>Deprecated in Release: v19.03</strong></p> <p>The <code class="language-plaintext highlighter-rouge">aufs</code> storage driver is deprecated in favor of <code class="language-plaintext highlighter-rouge">overlay2</code>, and will be removed in a future release. Users of the <code class="language-plaintext highlighter-rouge">aufs</code> storage driver are recommended to migrate to a different storage driver, such as <code class="language-plaintext highlighter-rouge">overlay2</code>, which is now the default storage driver.</p> <p>The <code class="language-plaintext highlighter-rouge">aufs</code> storage driver facilitates running Docker on distros that have no support for OverlayFS, such as Ubuntu 14.04 LTS, which originally shipped with a 3.14 kernel.</p> <p>Now that Ubuntu 14.04 is no longer a supported distro for Docker, and <code class="language-plaintext highlighter-rouge">overlay2</code> 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 <code class="language-plaintext highlighter-rouge">aufs</code> storage driver.</p> <h3 id="legacy-overlay-storage-driver">Legacy “overlay” storage driver</h3> <p><strong>Deprecated in Release: v18.09</strong></p> <p>The <code class="language-plaintext highlighter-rouge">overlay</code> storage driver is deprecated in favor of the <code class="language-plaintext highlighter-rouge">overlay2</code> storage driver, which has all the benefits of <code class="language-plaintext highlighter-rouge">overlay</code>, without its limitations (excessive inode consumption). The legacy <code class="language-plaintext highlighter-rouge">overlay</code> storage driver will be removed in a future release. Users of the <code class="language-plaintext highlighter-rouge">overlay</code> storage driver should migrate to the <code class="language-plaintext highlighter-rouge">overlay2</code> storage driver.</p> <p>The legacy <code class="language-plaintext highlighter-rouge">overlay</code> storage driver allowed using overlayFS-backed filesystems on pre 4.x kernels. Now that all supported distributions are able to run <code class="language-plaintext highlighter-rouge">overlay2</code> (as they are either on kernel 4.x, or have support for multiple lowerdirs backported), there is no reason to keep maintaining the <code class="language-plaintext highlighter-rouge">overlay</code> storage driver.</p> <h3 id="device-mapper-storage-driver">Device mapper storage driver</h3> <p><strong>Deprecated in Release: v18.09</strong></p> <p>The <code class="language-plaintext highlighter-rouge">devicemapper</code> storage driver is deprecated in favor of <code class="language-plaintext highlighter-rouge">overlay2</code>, and will be removed in a future release. Users of the <code class="language-plaintext highlighter-rouge">devicemapper</code> storage driver are recommended to migrate to a different storage driver, such as <code class="language-plaintext highlighter-rouge">overlay2</code>, which is now the default storage driver.</p> <p>The <code class="language-plaintext highlighter-rouge">devicemapper</code> storage driver facilitates running Docker on older (3.x) kernels that have no support for other storage drivers (such as overlay2, or AUFS).</p> <p>Now that support for <code class="language-plaintext highlighter-rouge">overlay2</code> 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 <code class="language-plaintext highlighter-rouge">devicemapper</code> storage driver.</p> <h3 id="use-of-reserved-namespaces-in-engine-labels">Use of reserved namespaces in engine labels</h3> <p><strong>Deprecated in Release: v18.06</strong></p> <p><strong>Removed In Release: v20.10</strong></p> <p>The namespaces <code class="language-plaintext highlighter-rouge">com.docker.*</code>, <code class="language-plaintext highlighter-rouge">io.docker.*</code>, and <code class="language-plaintext highlighter-rouge">org.dockerproject.*</code> in engine labels were always documented to be reserved, but there was never any enforcement.</p> <p>Usage of these namespaces will now cause a warning in the engine logs to discourage their use, and will error instead in v20.10 and above.</p> <h3 id="--disable-legacy-registry-override-daemon-option">
+<code class="language-plaintext highlighter-rouge">--disable-legacy-registry</code> override daemon option</h3> <p><strong>Disabled In Release: v17.12</strong></p> <p><strong>Removed In Release: v19.03</strong></p> <p>The <code class="language-plaintext highlighter-rouge">--disable-legacy-registry</code> 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, but hidden. The flag has been removed in Docker 19.03.</p> <h3 id="interacting-with-v1-registries">Interacting with V1 registries</h3> <p><strong>Disabled By Default In Release: v17.06</strong></p> <p><strong>Removed In Release: v17.12</strong></p> <p>Version 1.8.3 added a flag (<code class="language-plaintext highlighter-rouge">--disable-legacy-registry=false</code>) which prevents the docker daemon from <code class="language-plaintext highlighter-rouge">pull</code>, <code class="language-plaintext highlighter-rouge">push</code>, and <code class="language-plaintext highlighter-rouge">login</code> operations against v1 registries. Though enabled by default, this signals the intent to deprecate the v1 protocol.</p> <p>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 <a href="https://docs.docker.com/registry/recipes/mirror/">v2 registry mirror</a>.</p> <p>Starting with Docker 17.12, support for V1 registries has been removed, and the <code class="language-plaintext highlighter-rouge">--disable-legacy-registry</code> flag can no longer be used, and <code class="language-plaintext highlighter-rouge">dockerd</code> will fail to start when set.</p> <h3 id="asynchronous-service-create-and-service-update-as-default">Asynchronous <code class="language-plaintext highlighter-rouge">service create</code> and <code class="language-plaintext highlighter-rouge">service update</code> as default</h3> <p><strong>Deprecated In Release: v17.05</strong></p> <p><strong>Disabled by default in release: <a href="https://github.com/docker/docker-ce/releases/tag/v17.10.0-ce">v17.10</a></strong></p> <p>Docker 17.05 added an optional <code class="language-plaintext highlighter-rouge">--detach=false</code> option to make the <code class="language-plaintext highlighter-rouge">docker service create</code> and <code class="language-plaintext highlighter-rouge">docker service update</code> work synchronously. This option will be enabled by default in Docker 17.10, at which point the <code class="language-plaintext highlighter-rouge">--detach</code> flag can be used to use the previous (asynchronous) behavior.</p> <p>The default for this option will also be changed accordingly for <code class="language-plaintext highlighter-rouge">docker service rollback</code> and <code class="language-plaintext highlighter-rouge">docker service scale</code> in Docker 17.10.</p> <h3 id="-g-and---graph-flags-on-dockerd">
+<code class="language-plaintext highlighter-rouge">-g</code> and <code class="language-plaintext highlighter-rouge">--graph</code> flags on <code class="language-plaintext highlighter-rouge">dockerd</code>
+</h3> <p><strong>Deprecated In Release: v17.05</strong></p> <p>The <code class="language-plaintext highlighter-rouge">-g</code> or <code class="language-plaintext highlighter-rouge">--graph</code> flag for the <code class="language-plaintext highlighter-rouge">dockerd</code> or <code class="language-plaintext highlighter-rouge">docker daemon</code> command was used to indicate the directory in which to store persistent data and resource configuration and has been replaced with the more descriptive <code class="language-plaintext highlighter-rouge">--data-root</code> flag.</p> <p>These flags were added before Docker 1.0, so will not be <em>removed</em>, only <em>hidden</em>, to discourage their use.</p> <h3 id="top-level-network-properties-in-networksettings">Top-level network properties in NetworkSettings</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.13.0">v1.13.0</a></strong></p> <p><strong>Target For Removal In Release: v17.12</strong></p> <p>When inspecting a container, <code class="language-plaintext highlighter-rouge">NetworkSettings</code> contains top-level information about the default (“bridge”) network;</p> <p><code class="language-plaintext highlighter-rouge">EndpointID</code>, <code class="language-plaintext highlighter-rouge">Gateway</code>, <code class="language-plaintext highlighter-rouge">GlobalIPv6Address</code>, <code class="language-plaintext highlighter-rouge">GlobalIPv6PrefixLen</code>, <code class="language-plaintext highlighter-rouge">IPAddress</code>, <code class="language-plaintext highlighter-rouge">IPPrefixLen</code>, <code class="language-plaintext highlighter-rouge">IPv6Gateway</code>, and <code class="language-plaintext highlighter-rouge">MacAddress</code>.</p> <p>These properties are deprecated in favor of per-network properties in <code class="language-plaintext highlighter-rouge">NetworkSettings.Networks</code>. These properties were already “deprecated” in docker 1.9, but kept around for backward compatibility.</p> <p>Refer to <a href="https://github.com/docker/docker/pull/17538">#17538</a> for further information.</p> <h3 id="filter-param-for-imagesjson-endpoint">
+<code class="language-plaintext highlighter-rouge">filter</code> param for <code class="language-plaintext highlighter-rouge">/images/json</code> endpoint</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.13.0">v1.13.0</a></strong></p> <p><strong>Removed In Release: v20.10</strong></p> <p>The <code class="language-plaintext highlighter-rouge">filter</code> param to filter the list of image by reference (name or name:tag) is now implemented as a regular filter, named <code class="language-plaintext highlighter-rouge">reference</code>.</p> <h3 id="repositoryshortid-image-references">
+<code class="language-plaintext highlighter-rouge">repository:shortid</code> image references</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.13.0">v1.13.0</a></strong></p> <p><strong>Removed In Release: v17.12</strong></p> <p>The <code class="language-plaintext highlighter-rouge">repository:shortid</code> syntax for referencing images is very little used, collides with tag references, and can be confused with digest references.</p> <p>Support for the <code class="language-plaintext highlighter-rouge">repository:shortid</code> notation to reference images was removed in Docker 17.12.</p> <h3 id="docker-daemon-subcommand">
+<code class="language-plaintext highlighter-rouge">docker daemon</code> subcommand</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.13.0">v1.13.0</a></strong></p> <p><strong>Removed In Release: v17.12</strong></p> <p>The daemon is moved to a separate binary (<code class="language-plaintext highlighter-rouge">dockerd</code>), and should be used instead.</p> <h3 id="duplicate-keys-with-conflicting-values-in-engine-labels">Duplicate keys with conflicting values in engine labels</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.13.0">v1.13.0</a></strong></p> <p><strong>Removed In Release: v17.12</strong></p> <p>When setting duplicate keys with conflicting values, an error will be produced, and the daemon will fail to start.</p> <h3 id="maintainer-in-dockerfile">
+<code class="language-plaintext highlighter-rouge">MAINTAINER</code> in Dockerfile</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.13.0">v1.13.0</a></strong></p> <p><code class="language-plaintext highlighter-rouge">MAINTAINER</code> was an early very limited form of <code class="language-plaintext highlighter-rouge">LABEL</code> which should be used instead.</p> <h3 id="api-calls-without-a-version">API calls without a version</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.13.0">v1.13.0</a></strong></p> <p><strong>Target For Removal In Release: v17.12</strong></p> <p>API versions should be supplied to all API calls to ensure compatibility with future Engine versions. Instead of just requesting, for example, the URL <code class="language-plaintext highlighter-rouge">/containers/json</code>, you must now request <code class="language-plaintext highlighter-rouge">/v1.25/containers/json</code>.</p> <h3 id="backing-filesystem-without-d_type-support-for-overlayoverlay2">Backing filesystem without <code class="language-plaintext highlighter-rouge">d_type</code> support for overlay/overlay2</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.13.0">v1.13.0</a></strong></p> <p><strong>Removed In Release: v17.12</strong></p> <p>The overlay and overlay2 storage driver does not work as expected if the backing filesystem does not support <code class="language-plaintext highlighter-rouge">d_type</code>. For example, XFS does not support <code class="language-plaintext highlighter-rouge">d_type</code> if it is formatted with the <code class="language-plaintext highlighter-rouge">ftype=0</code> option.</p> <p>Starting with Docker 17.12, new installations will not support running overlay2 on a backing filesystem without <code class="language-plaintext highlighter-rouge">d_type</code> support. For existing installations that upgrade to 17.12, a warning will be printed.</p> <p>Please also refer to <a href="https://github.com/docker/docker/issues/27358">#27358</a> for further information.</p> <h3 id="--automated-and---stars-flags-on-docker-search">
+<code class="language-plaintext highlighter-rouge">--automated</code> and <code class="language-plaintext highlighter-rouge">--stars</code> flags on <code class="language-plaintext highlighter-rouge">docker search</code>
+</h3> <p><strong>Deprecated in Release: <a href="https://github.com/docker/docker/releases/tag/v1.12.0">v1.12.0</a></strong></p> <p><strong>Removed In Release: v20.10</strong></p> <p>The <code class="language-plaintext highlighter-rouge">docker search --automated</code> and <code class="language-plaintext highlighter-rouge">docker search --stars</code> options are deprecated. Use <code class="language-plaintext highlighter-rouge">docker search --filter=is-automated=&lt;true|false&gt;</code> and <code class="language-plaintext highlighter-rouge">docker search --filter=stars=...</code> instead.</p> <h3 id="-h-shorthand-for---help">
+<code class="language-plaintext highlighter-rouge">-h</code> shorthand for <code class="language-plaintext highlighter-rouge">--help</code>
+</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.12.0">v1.12.0</a></strong></p> <p><strong>Target For Removal In Release: v17.09</strong></p> <p>The shorthand (<code class="language-plaintext highlighter-rouge">-h</code>) is less common than <code class="language-plaintext highlighter-rouge">--help</code> on Linux and cannot be used on all subcommands (due to it conflicting with, e.g. <code class="language-plaintext highlighter-rouge">-h</code> / <code class="language-plaintext highlighter-rouge">--hostname</code> on <code class="language-plaintext highlighter-rouge">docker create</code>). For this reason, the <code class="language-plaintext highlighter-rouge">-h</code> shorthand was not printed in the “usage” output of subcommands, nor documented, and is now marked “deprecated”.</p> <h3 id="-e-and---email-flags-on-docker-login">
+<code class="language-plaintext highlighter-rouge">-e</code> and <code class="language-plaintext highlighter-rouge">--email</code> flags on <code class="language-plaintext highlighter-rouge">docker login</code>
+</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.11.0">v1.11.0</a></strong></p> <p><strong>Removed In Release: <a href="https://github.com/docker/docker-ce/releases/tag/v17.06.0-ce">v17.06</a></strong></p> <p>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.</p> <h3 id="separator--of---security-opt-flag-on-docker-run">Separator (<code class="language-plaintext highlighter-rouge">:</code>) of <code class="language-plaintext highlighter-rouge">--security-opt</code> flag on <code class="language-plaintext highlighter-rouge">docker run</code>
+</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.11.0">v1.11.0</a></strong></p> <p><strong>Target For Removal In Release: v17.06</strong></p> <p>The flag <code class="language-plaintext highlighter-rouge">--security-opt</code> doesn’t use the colon separator (<code class="language-plaintext highlighter-rouge">:</code>) anymore to divide keys and values, it uses the equal symbol (<code class="language-plaintext highlighter-rouge">=</code>) for consistency with other similar flags, like <code class="language-plaintext highlighter-rouge">--storage-opt</code>.</p> <h3 id="ambiguous-event-fields-in-api">Ambiguous event fields in API</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.10.0">v1.10.0</a></strong></p> <p>The fields <code class="language-plaintext highlighter-rouge">ID</code>, <code class="language-plaintext highlighter-rouge">Status</code> and <code class="language-plaintext highlighter-rouge">From</code> in the events API have been deprecated in favor of a more rich structure. See the events API documentation for the new format.</p> <h3 id="-f-flag-on-docker-tag">
+<code class="language-plaintext highlighter-rouge">-f</code> flag on <code class="language-plaintext highlighter-rouge">docker tag</code>
+</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.10.0">v1.10.0</a></strong></p> <p><strong>Removed In Release: <a href="https://github.com/docker/docker/releases/tag/v1.12.0">v1.12.0</a></strong></p> <p>To make tagging consistent across the various <code class="language-plaintext highlighter-rouge">docker</code> commands, the <code class="language-plaintext highlighter-rouge">-f</code> flag on the <code class="language-plaintext highlighter-rouge">docker tag</code> command is deprecated. It is not longer necessary to specify <code class="language-plaintext highlighter-rouge">-f</code> to move a tag from one image to another. Nor will <code class="language-plaintext highlighter-rouge">docker</code> generate an error if the <code class="language-plaintext highlighter-rouge">-f</code> flag is missing and the specified tag is already in use.</p> <h3 id="hostconfig-at-api-container-start">HostConfig at API container start</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.10.0">v1.10.0</a></strong></p> <p><strong>Removed In Release: <a href="https://github.com/docker/docker/releases/tag/v1.12.0">v1.12.0</a></strong></p> <p>Passing an <code class="language-plaintext highlighter-rouge">HostConfig</code> to <code class="language-plaintext highlighter-rouge">POST /containers/{name}/start</code> is deprecated in favor of defining it at container creation (<code class="language-plaintext highlighter-rouge">POST /containers/create</code>).</p> <h3 id="--before-and---since-flags-on-docker-ps">
+<code class="language-plaintext highlighter-rouge">--before</code> and <code class="language-plaintext highlighter-rouge">--since</code> flags on <code class="language-plaintext highlighter-rouge">docker ps</code>
+</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.10.0">v1.10.0</a></strong></p> <p><strong>Removed In Release: <a href="https://github.com/docker/docker/releases/tag/v1.12.0">v1.12.0</a></strong></p> <p>The <code class="language-plaintext highlighter-rouge">docker ps --before</code> and <code class="language-plaintext highlighter-rouge">docker ps --since</code> options are deprecated. Use <code class="language-plaintext highlighter-rouge">docker ps --filter=before=...</code> and <code class="language-plaintext highlighter-rouge">docker ps --filter=since=...</code> instead.</p> <h3 id="driver-specific-log-tags">Driver-specific log tags</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.9.0">v1.9.0</a></strong></p> <p><strong>Removed In Release: <a href="https://github.com/docker/docker/releases/tag/v1.12.0">v1.12.0</a></strong></p> <p>Log tags are now generated in a standard way across different logging drivers. Because of which, the driver specific log tag options <code class="language-plaintext highlighter-rouge">syslog-tag</code>, <code class="language-plaintext highlighter-rouge">gelf-tag</code> and <code class="language-plaintext highlighter-rouge">fluentd-tag</code> have been deprecated in favor of the generic <code class="language-plaintext highlighter-rouge">tag</code> option.</p> <div class="highlight"><pre class="highlight" data-language="">
+$ docker --log-driver=syslog --log-opt tag="{{.ImageName}}/{{.Name}}/{{.ID}}"
+
+</pre></div> <h3 id="docker-content-trust-env-passphrase-variables-name-change">Docker Content Trust ENV passphrase variables name change</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.9.0">v1.9.0</a></strong></p> <p><strong>Removed In Release: <a href="https://github.com/docker/docker/releases/tag/v1.12.0">v1.12.0</a></strong></p> <p>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</p> <ul> <li>DOCKER_CONTENT_TRUST_OFFLINE_PASSPHRASE is now named DOCKER_CONTENT_TRUST_ROOT_PASSPHRASE</li> <li>DOCKER_CONTENT_TRUST_TAGGING_PASSPHRASE is now named DOCKER_CONTENT_TRUST_REPOSITORY_PASSPHRASE</li> </ul> <h3 id="containersid-or-namecopy-endpoint">
+<code class="language-plaintext highlighter-rouge">/containers/(id or name)/copy</code> endpoint</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.8.0">v1.8.0</a></strong></p> <p><strong>Removed In Release: <a href="https://github.com/docker/docker/releases/tag/v1.12.0">v1.12.0</a></strong></p> <p>The endpoint <code class="language-plaintext highlighter-rouge">/containers/(id or name)/copy</code> is deprecated in favor of <code class="language-plaintext highlighter-rouge">/containers/(id or name)/archive</code>.</p> <h3 id="lxc-built-in-exec-driver">LXC built-in exec driver</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.8.0">v1.8.0</a></strong></p> <p><strong>Removed In Release: <a href="https://github.com/docker/docker/releases/tag/v1.10.0">v1.10.0</a></strong></p> <p>The built-in LXC execution driver, the lxc-conf flag, and API fields have been removed.</p> <h3 id="old-command-line-options">Old Command Line Options</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.8.0">v1.8.0</a></strong></p> <p><strong>Removed In Release: <a href="https://github.com/docker/docker/releases/tag/v1.10.0">v1.10.0</a></strong></p> <p>The flags <code class="language-plaintext highlighter-rouge">-d</code> and <code class="language-plaintext highlighter-rouge">--daemon</code> are deprecated in favor of the <code class="language-plaintext highlighter-rouge">daemon</code> subcommand:</p> <div class="highlight"><pre class="highlight" data-language="">docker daemon -H ...
+</pre></div> <p>The following single-dash (<code class="language-plaintext highlighter-rouge">-opt</code>) variant of certain command line options are deprecated and replaced with double-dash options (<code class="language-plaintext highlighter-rouge">--opt</code>):</p> <div class="highlight"><pre class="highlight" data-language="">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
+</pre></div> <p>The following double-dash options are deprecated and have no replacement:</p> <div class="highlight"><pre class="highlight" data-language="">docker run --cpuset
+docker run --networking
+docker ps --since-id
+docker ps --before-id
+docker search --trusted
+</pre></div> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.5.0">v1.5.0</a></strong></p> <p><strong>Removed In Release: <a href="https://github.com/docker/docker/releases/tag/v1.12.0">v1.12.0</a></strong></p> <p>The single-dash (<code class="language-plaintext highlighter-rouge">-help</code>) was removed, in favor of the double-dash <code class="language-plaintext highlighter-rouge">--help</code></p> <div class="highlight"><pre class="highlight" data-language="">docker -help
+docker [COMMAND] -help
+</pre></div> <h3 id="--api-enable-cors-flag-on-dockerd">
+<code class="language-plaintext highlighter-rouge">--api-enable-cors</code> flag on dockerd</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v1.6.0">v1.6.0</a></strong></p> <p><strong>Removed In Release: <a href="https://github.com/docker/docker-ce/releases/tag/v17.09.0-ce">v17.09</a></strong></p> <p>The flag <code class="language-plaintext highlighter-rouge">--api-enable-cors</code> is deprecated since v1.6.0. Use the flag <code class="language-plaintext highlighter-rouge">--api-cors-header</code> instead.</p> <h3 id="--run-flag-on-docker-commit">
+<code class="language-plaintext highlighter-rouge">--run</code> flag on docker commit</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v0.10.0">v0.10.0</a></strong></p> <p><strong>Removed In Release: <a href="https://github.com/docker/docker/releases/tag/v1.13.0">v1.13.0</a></strong></p> <p>The flag <code class="language-plaintext highlighter-rouge">--run</code> of the docker commit (and its short version <code class="language-plaintext highlighter-rouge">-run</code>) were deprecated in favor of the <code class="language-plaintext highlighter-rouge">--changes</code> flag that allows to pass <code class="language-plaintext highlighter-rouge">Dockerfile</code> commands.</p> <h3 id="three-arguments-form-in-docker-import">Three arguments form in <code class="language-plaintext highlighter-rouge">docker import</code>
+</h3> <p><strong>Deprecated In Release: <a href="https://github.com/docker/docker/releases/tag/v0.6.7">v0.6.7</a></strong></p> <p><strong>Removed In Release: <a href="https://github.com/docker/docker/releases/tag/v1.12.0">v1.12.0</a></strong></p> <p>The <code class="language-plaintext highlighter-rouge">docker import</code> command format <code class="language-plaintext highlighter-rouge">file|URL|- [REPOSITORY [TAG]]</code> is deprecated since November 2013. It’s no more supported.</p> 
+<p><a href="https://docs.docker.com/search/?q=docker">docker</a>, <a href="https://docs.docker.com/search/?q=documentation">documentation</a>, <a href="https://docs.docker.com/search/?q=about">about</a>, <a href="https://docs.docker.com/search/?q=technology">technology</a>, <a href="https://docs.docker.com/search/?q=deprecate">deprecate</a></p>
+<div class="_attribution">
+  <p class="_attribution-p">
+    &copy; 2019 Docker, Inc.<br>Licensed under the Apache License, Version 2.0.<br>Docker and the Docker logo are trademarks or registered trademarks of Docker, Inc. in the United States and/or other countries.<br>Docker, Inc. and other parties may also have trademark rights in other terms used herein.<br>
+    <a href="https://docs.docker.com/engine/deprecated/" class="_attribution-link">https://docs.docker.com/engine/deprecated/</a>
+  </p>
+</div>