diff --git a/_vendor/github.com/docker/cli/docs/extend/index.md b/_vendor/github.com/docker/cli/docs/extend/index.md index c90a42cb4f..7264d59bae 100644 --- a/_vendor/github.com/docker/cli/docs/extend/index.md +++ b/_vendor/github.com/docker/cli/docs/extend/index.md @@ -117,7 +117,7 @@ enabled, and use it to create a volume. To disable a plugin, use the `docker plugin disable` command. To completely remove it, use the `docker plugin remove` command. For other available commands and options, see the -[command line reference](https://docs.docker.com/engine/reference/commandline/cli/). +[command line reference](https://docs.docker.com/reference/cli/docker/). ## Developing a plugin diff --git a/_vendor/github.com/docker/cli/docs/reference/commandline/cli.md b/_vendor/github.com/docker/cli/docs/reference/commandline/cli.md deleted file mode 100644 index c6bd54337a..0000000000 --- a/_vendor/github.com/docker/cli/docs/reference/commandline/cli.md +++ /dev/null @@ -1,408 +0,0 @@ ---- -title: "Use the Docker command line" -description: "Docker's CLI command description and usage" -keywords: "Docker, Docker documentation, CLI, command line, config.json, CLI configuration file" -aliases: - - /reference/commandline/cli/ - - /engine/reference/commandline/engine/ - - /engine/reference/commandline/engine_activate/ - - /engine/reference/commandline/engine_check/ - - /engine/reference/commandline/engine_update/ ---- - -The base command for the Docker CLI is `docker`. For information about the -available flags and subcommands, refer to the [CLI reference](https://docs.docker.com/reference/cli/docker/) - -Depending on your Docker system configuration, you may be required to preface -each `docker` command with `sudo`. To avoid having to use `sudo` with the -`docker` command, your system administrator can create a Unix group called -`docker` and add users to it. - -For more information about installing Docker or `sudo` configuration, refer to -the [installation](https://docs.docker.com/install/) instructions for your operating system. - -## Environment variables - -The following list of environment variables are supported by the `docker` command -line: - -| Variable | Description | -| :---------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `DOCKER_API_VERSION` | Override the negotiated API version to use for debugging (e.g. `1.19`) | -| `DOCKER_CERT_PATH` | Location of your authentication keys. This variable is used both by the `docker` CLI and the [`dockerd` daemon](https://docs.docker.com/reference/cli/dockerd/) | -| `DOCKER_CONFIG` | The location of your client configuration files. | -| `DOCKER_CONTENT_TRUST_SERVER` | The URL of the Notary server to use. Defaults to the same URL as the registry. | -| `DOCKER_CONTENT_TRUST` | When set Docker uses notary to sign and verify images. Equates to `--disable-content-trust=false` for build, create, pull, push, run. | -| `DOCKER_CONTEXT` | Name of the `docker context` to use (overrides `DOCKER_HOST` env var and default context set with `docker context use`) | -| `DOCKER_DEFAULT_PLATFORM` | Default platform for commands that take the `--platform` flag. | -| `DOCKER_HIDE_LEGACY_COMMANDS` | When set, Docker hides "legacy" top-level commands (such as `docker rm`, and `docker pull`) in `docker help` output, and only `Management commands` per object-type (e.g., `docker container`) are printed. This may become the default in a future release. | -| `DOCKER_HOST` | Daemon socket to connect to. | -| `DOCKER_TLS` | Enable TLS for connections made by the `docker` CLI (equivalent of the `--tls` command-line option). Set to a non-empty value to enable TLS. Note that TLS is enabled automatically if any of the other TLS options are set. | -| `DOCKER_TLS_VERIFY` | When set Docker uses TLS and verifies the remote. This variable is used both by the `docker` CLI and the [`dockerd` daemon](https://docs.docker.com/reference/cli/dockerd/) | -| `BUILDKIT_PROGRESS` | Set type of progress output (`auto`, `plain`, `tty`, `rawjson`) when [building](https://docs.docker.com/reference/cli/docker/image/build/) with [BuildKit backend](https://docs.docker.com/build/buildkit/). Use plain to show container output (default `auto`). | - -Because Docker is developed using Go, you can also use any environment -variables used by the Go runtime. In particular, you may find these useful: - -| Variable | Description | -|:--------------|:-------------------------------------------------------------------------------| -| `HTTP_PROXY` | Proxy URL for HTTP requests unless overridden by NoProxy. | -| `HTTPS_PROXY` | Proxy URL for HTTPS requests unless overridden by NoProxy. | -| `NO_PROXY` | Comma-separated values specifying hosts that should be excluded from proxying. | - -See the [Go specification](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config) -for details on these variables. - -## Configuration files - -By default, the Docker command line stores its configuration files in a -directory called `.docker` within your `$HOME` directory. - -Docker manages most of the files in the configuration directory -and you shouldn't modify them. However, you can modify the -`config.json` file to control certain aspects of how the `docker` -command behaves. - -You can modify the `docker` command behavior using environment -variables or command-line options. You can also use options within -`config.json` to modify some of the same behavior. If an environment variable -and the `--config` flag are set, the flag takes precedent over the environment -variable. Command line options override environment variables and environment -variables override properties you specify in a `config.json` file. - -### Change the `.docker` directory - -To specify a different directory, use the `DOCKER_CONFIG` -environment variable or the `--config` command line option. If both are -specified, then the `--config` option overrides the `DOCKER_CONFIG` environment -variable. The example below overrides the `docker ps` command using a -`config.json` file located in the `~/testconfigs/` directory. - -```console -$ docker --config ~/testconfigs/ ps -``` - -This flag only applies to whatever command is being ran. For persistent -configuration, you can set the `DOCKER_CONFIG` environment variable in your -shell (e.g. `~/.profile` or `~/.bashrc`). The example below sets the new -directory to be `HOME/newdir/.docker`. - -```console -$ echo export DOCKER_CONFIG=$HOME/newdir/.docker > ~/.profile -``` - -## Docker CLI configuration file (`config.json`) properties - - - -Use the Docker CLI configuration to customize settings for the `docker` CLI. The -configuration file uses JSON formatting, and properties: - -By default, configuration file is stored in `~/.docker/config.json`. Refer to the -[change the `.docker` directory](#change-the-docker-directory) section to use a -different location. - -> **Warning** -> -> The configuration file and other files inside the `~/.docker` configuration -> directory may contain sensitive information, such as authentication information -> for proxies or, depending on your credential store, credentials for your image -> registries. Review your configuration file's content before sharing with others, -> and prevent committing the file to version control. - -### Customize the default output format for commands - -These fields lets you customize the default output format for some commands -if no `--format` flag is provided. - -| Property | Description | -| :--------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `configFormat` | Custom default format for `docker config ls` output. See [`docker config ls`](https://docs.docker.com/reference/cli/docker/config/ls/#format) for a list of supported formatting directives. | -| `imagesFormat` | Custom default format for `docker images` / `docker image ls` output. See [`docker images`](https://docs.docker.com/reference/cli/docker/image/ls/#format) for a list of supported formatting directives. | -| `networksFormat` | Custom default format for `docker network ls` output. See [`docker network ls`](https://docs.docker.com/reference/cli/docker/network/ls/#format) for a list of supported formatting directives. | -| `nodesFormat` | Custom default format for `docker node ls` output. See [`docker node ls`](https://docs.docker.com/reference/cli/docker/node/ls/#format) for a list of supported formatting directives. | -| `pluginsFormat` | Custom default format for `docker plugin ls` output. See [`docker plugin ls`](https://docs.docker.com/reference/cli/docker/plugin/ls/#format) for a list of supported formatting directives. | -| `psFormat` | Custom default format for `docker ps` / `docker container ps` output. See [`docker ps`](https://docs.docker.com/reference/cli/docker/container/ls/#format) for a list of supported formatting directives. | -| `secretFormat` | Custom default format for `docker secret ls` output. See [`docker secret ls`](https://docs.docker.com/reference/cli/docker/secret/ls/#format) for a list of supported formatting directives. | -| `serviceInspectFormat` | Custom default format for `docker service inspect` output. See [`docker service inspect`](https://docs.docker.com/reference/cli/docker/service/inspect/#format) for a list of supported formatting directives. | -| `servicesFormat` | Custom default format for `docker service ls` output. See [`docker service ls`](https://docs.docker.com/reference/cli/docker/service/ls/#format) for a list of supported formatting directives. | -| `statsFormat` | Custom default format for `docker stats` output. See [`docker stats`](https://docs.docker.com/reference/cli/docker/container/stats/#format) for a list of supported formatting directives. | -| `tasksFormat` | Custom default format for `docker stack ps` output. See [`docker stack ps`](https://docs.docker.com/reference/cli/docker/stack/ps/#format) for a list of supported formatting directives. | -| `volumesFormat` | Custom default format for `docker volume ls` output. See [`docker volume ls`](https://docs.docker.com/reference/cli/docker/volume/ls/#format) for a list of supported formatting directives. | - -### Custom HTTP headers - -The property `HttpHeaders` specifies a set of headers to include in all messages -sent from the Docker client to the daemon. Docker doesn't try to interpret or -understand these headers; it simply puts them into the messages. Docker does -not allow these headers to change any headers it sets for itself. - -### Credential store options - -The property `credsStore` specifies an external binary to serve as the default -credential store. When this property is set, `docker login` will attempt to -store credentials in the binary specified by `docker-credential-` which -is visible on `$PATH`. If this property isn't set, credentials are stored -in the `auths` property of the CLI configuration file. For more information, -see the [**Credential stores** section in the `docker login` documentation](https://docs.docker.com/reference/cli/docker/login/#credential-stores) - -The property `credHelpers` specifies a set of credential helpers to use -preferentially over `credsStore` or `auths` when storing and retrieving -credentials for specific registries. If this property is set, the binary -`docker-credential-` will be used when storing or retrieving credentials -for a specific registry. For more information, see the -[**Credential helpers** section in the `docker login` documentation](https://docs.docker.com/reference/cli/docker/login/#credential-helpers) - -### Automatic proxy configuration for containers - -The property `proxies` specifies proxy environment variables to be automatically -set on containers, and set as `--build-arg` on containers used during `docker build`. -A `"default"` set of proxies can be configured, and will be used for any Docker -daemon that the client connects to, or a configuration per host (Docker daemon), -for example, `https://docker-daemon1.example.com`. The following properties can -be set for each environment: - -| Property | Description | -|:---------------|:--------------------------------------------------------------------------------------------------------| -| `httpProxy` | Default value of `HTTP_PROXY` and `http_proxy` for containers, and as `--build-arg` on `docker build` | -| `httpsProxy` | Default value of `HTTPS_PROXY` and `https_proxy` for containers, and as `--build-arg` on `docker build` | -| `ftpProxy` | Default value of `FTP_PROXY` and `ftp_proxy` for containers, and as `--build-arg` on `docker build` | -| `noProxy` | Default value of `NO_PROXY` and `no_proxy` for containers, and as `--build-arg` on `docker build` | -| `allProxy` | Default value of `ALL_PROXY` and `all_proxy` for containers, and as `--build-arg` on `docker build` | - -These settings are used to configure proxy settings for containers only, and not -used as proxy settings for the `docker` CLI or the `dockerd` daemon. Refer to the -[environment variables](#environment-variables) and [HTTP/HTTPS proxy](https://docs.docker.com/config/daemon/systemd/#httphttps-proxy) -sections for configuring proxy settings for the cli and daemon. - -> **Warning** -> -> Proxy settings may contain sensitive information (for example, if the proxy -> requires authentication). Environment variables are stored as plain text in -> the container's configuration, and as such can be inspected through the remote -> API or committed to an image when using `docker commit`. -{ .warning } - -### Default key-sequence to detach from containers - -Once attached to a container, users detach from it and leave it running using -the using `CTRL-p CTRL-q` key sequence. This detach key sequence is customizable -using the `detachKeys` property. Specify a `` value for the -property. The format of the `` is a comma-separated list of either -a letter [a-Z], or the `ctrl-` combined with any of the following: - -* `a-z` (a single lowercase alpha character ) -* `@` (at sign) -* `[` (left bracket) -* `\\` (two backward slashes) -* `_` (underscore) -* `^` (caret) - -Your customization applies to all containers started in with your Docker client. -Users can override your custom or the default key sequence on a per-container -basis. To do this, the user specifies the `--detach-keys` flag with the `docker -attach`, `docker exec`, `docker run` or `docker start` command. - -### CLI plugin options - -The property `plugins` contains settings specific to CLI plugins. The -key is the plugin name, while the value is a further map of options, -which are specific to that plugin. - -### Sample configuration file - -Following is a sample `config.json` file to illustrate the format used for -various fields: - -```json -{ - "HttpHeaders": { - "MyHeader": "MyValue" - }, - "psFormat": "table {{.ID}}\\t{{.Image}}\\t{{.Command}}\\t{{.Labels}}", - "imagesFormat": "table {{.ID}}\\t{{.Repository}}\\t{{.Tag}}\\t{{.CreatedAt}}", - "pluginsFormat": "table {{.ID}}\t{{.Name}}\t{{.Enabled}}", - "statsFormat": "table {{.Container}}\t{{.CPUPerc}}\t{{.MemUsage}}", - "servicesFormat": "table {{.ID}}\t{{.Name}}\t{{.Mode}}", - "secretFormat": "table {{.ID}}\t{{.Name}}\t{{.CreatedAt}}\t{{.UpdatedAt}}", - "configFormat": "table {{.ID}}\t{{.Name}}\t{{.CreatedAt}}\t{{.UpdatedAt}}", - "serviceInspectFormat": "pretty", - "nodesFormat": "table {{.ID}}\t{{.Hostname}}\t{{.Availability}}", - "detachKeys": "ctrl-e,e", - "credsStore": "secretservice", - "credHelpers": { - "awesomereg.example.org": "hip-star", - "unicorn.example.com": "vcbait" - }, - "plugins": { - "plugin1": { - "option": "value" - }, - "plugin2": { - "anotheroption": "anothervalue", - "athirdoption": "athirdvalue" - } - }, - "proxies": { - "default": { - "httpProxy": "http://user:pass@example.com:3128", - "httpsProxy": "https://my-proxy.example.com:3129", - "noProxy": "intra.mycorp.example.com", - "ftpProxy": "http://user:pass@example.com:3128", - "allProxy": "socks://example.com:1234" - }, - "https://manager1.mycorp.example.com:2377": { - "httpProxy": "http://user:pass@example.com:3128", - "httpsProxy": "https://my-proxy.example.com:3129" - } - } -} -``` - -### Experimental features - -Experimental features provide early access to future product functionality. -These features are intended for testing and feedback, and they may change -between releases without warning or can be removed from a future release. - -Starting with Docker 20.10, experimental CLI features are enabled by default, -and require no configuration to enable them. - -### Notary - -If using your own notary server and a self-signed certificate or an internal -Certificate Authority, you need to place the certificate at -`tls//ca.crt` in your Docker config directory. - -Alternatively you can trust the certificate globally by adding it to your system's -list of root Certificate Authorities. - -## Examples - -### Specify daemon host (-H, --host) - -You can use the `-H`, `--host` flag to specify a socket to use when you invoke -a `docker` command. You can use the following protocols: - -| Scheme | Description | Example | -|----------------------------------------|---------------------------|----------------------------------| -| `unix://[]` | Unix socket (Linux only) | `unix:///var/run/docker.sock` | -| `tcp://[[:port]]` | TCP connection | `tcp://174.17.0.1:2376` | -| `ssh://[username@][:port]` | SSH connection | `ssh://user@192.168.64.5` | -| `npipe://[]` | Named pipe (Windows only) | `npipe:////./pipe/docker_engine` | - -If you don't specify the `-H` flag, and you're not using a custom -[context](https://docs.docker.com/engine/context/working-with-contexts), -commands use the following default sockets: - -- `unix:///var/run/docker.sock` on macOS and Linux -- `npipe:////./pipe/docker_engine` on Windows - -To achieve a similar effect without having to specify the `-H` flag for every -command, you could also [create a context](https://docs.docker.com/reference/cli/docker/context/create/), -or alternatively, use the -[`DOCKER_HOST` environment variable](#environment-variables). - -For more information about the `-H` flag, see -[Daemon socket option](https://docs.docker.com/reference/cli/dockerd/#daemon-socket-option). - -#### Using TCP sockets - -The following example shows how to invoke `docker ps` over TCP, to a remote -daemon with IP address `174.17.0.1`, listening on port `2376`: - -```console -$ docker -H tcp://174.17.0.1:2376 ps -``` - -> **Note** -> -> By convention, the Docker daemon uses port `2376` for secure TLS connections, -> and port `2375` for insecure, non-TLS connections. - -#### Using SSH sockets - -When you use SSH invoke a command on a remote daemon, the request gets forwarded -to the `/var/run/docker.sock` Unix socket on the SSH host. - -```console -$ docker -H ssh://user@192.168.64.5 ps -``` - -You can optionally specify the location of the socket by appending a path -component to the end of the SSH address. - -```console -$ docker -H ssh://user@192.168.64.5/var/run/docker.sock ps -``` - -### Display help text - -To list the help on any command just execute the command, followed by the -`--help` option. - -```console -$ docker run --help - -Usage: docker run [OPTIONS] IMAGE [COMMAND] [ARG...] - -Create and run a new container from an image - -Options: - --add-host value Add a custom host-to-IP mapping (host:ip) (default []) - -a, --attach value Attach to STDIN, STDOUT or STDERR (default []) -<...> -``` - -### Option types - -Single character command line options can be combined, so rather than -typing `docker run -i -t --name test busybox sh`, -you can write `docker run -it --name test busybox sh`. - -#### Boolean - -Boolean options take the form `-d=false`. The value you see in the help text is -the default value which is set if you do **not** specify that flag. If you -specify a Boolean flag without a value, this will set the flag to `true`, -irrespective of the default value. - -For example, running `docker run -d` will set the value to `true`, so your -container **will** run in "detached" mode, in the background. - -Options which default to `true` (e.g., `docker build --rm=true`) can only be -set to the non-default value by explicitly setting them to `false`: - -```console -$ docker build --rm=false . -``` - -#### Multi - -You can specify options like `-a=[]` multiple times in a single command line, -for example in these commands: - -```console -$ docker run -a stdin -a stdout -i -t ubuntu /bin/bash - -$ docker run -a stdin -a stdout -a stderr ubuntu /bin/ls -``` - -Sometimes, multiple options can call for a more complex value string as for -`-v`: - -```console -$ docker run -v /host:/container example/mysql -``` - -> **Note** -> -> Do not use the `-t` and `-a stderr` options together due to -> limitations in the `pty` implementation. All `stderr` in `pty` mode -> simply goes to `stdout`. - -#### Strings and Integers - -Options like `--name=""` expect a string, and they -can only be specified once. Options like `-c=0` -expect an integer, and they can only be specified once. diff --git a/_vendor/github.com/docker/cli/docs/reference/dockerd.md b/_vendor/github.com/docker/cli/docs/reference/dockerd.md index f8bf348d54..d0be72e45b 100644 --- a/_vendor/github.com/docker/cli/docs/reference/dockerd.md +++ b/_vendor/github.com/docker/cli/docs/reference/dockerd.md @@ -134,15 +134,14 @@ to [the `daemon.json` file](#daemon-configuration-file). The following list of environment variables are supported by the `dockerd` daemon. Some of these environment variables are supported both by the Docker Daemon and the `docker` CLI. Refer to [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) -in the CLI section to learn about environment variables supported by the -`docker` CLI. +to learn about environment variables supported by the `docker` CLI. | Variable | Description | | :------------------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `DOCKER_CERT_PATH` | Location of your authentication keys. This variable is used both by the [`docker` CLI](https://docs.docker.com/engine/reference/commandline/cli/) and the `dockerd` daemon. | +| `DOCKER_CERT_PATH` | Location of your authentication keys. This variable is used both by the [`docker` CLI](https://docs.docker.com/reference/cli/docker/) and the `dockerd` daemon. | | `DOCKER_DRIVER` | The storage driver to use. | | `DOCKER_RAMDISK` | If set this disables `pivot_root`. | -| `DOCKER_TLS_VERIFY` | When set Docker uses TLS and verifies the remote. This variable is used both by the [`docker` CLI](https://docs.docker.com/engine/reference/commandline/cli/) and the `dockerd` daemon. | +| `DOCKER_TLS_VERIFY` | When set Docker uses TLS and verifies the remote. This variable is used both by the [`docker` CLI](https://docs.docker.com/reference/cli/docker/) and the `dockerd` daemon. | | `DOCKER_TMPDIR` | Location for temporary files created by the daemon. | | `HTTP_PROXY` | Proxy URL for HTTP requests unless overridden by NoProxy. See the [Go specification](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config) for details. | | `HTTPS_PROXY` | Proxy URL for HTTPS requests unless overridden by NoProxy. See the [Go specification](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config) for details. | diff --git a/_vendor/modules.txt b/_vendor/modules.txt index d7d90aa9a9..bea08f42fe 100644 --- a/_vendor/modules.txt +++ b/_vendor/modules.txt @@ -1,6 +1,6 @@ # github.com/moby/moby v27.0.3+incompatible # github.com/moby/buildkit v0.15.1 # github.com/docker/buildx v0.16.2 -# github.com/docker/cli v27.0.3+incompatible +# github.com/docker/cli v27.1.1+incompatible # github.com/docker/compose/v2 v2.29.1 # github.com/docker/scout-cli v1.13.0 diff --git a/content/compose/environment-variables/envvars.md b/content/compose/environment-variables/envvars.md index f01ae8b8fe..b2bc90a9a1 100644 --- a/content/compose/environment-variables/envvars.md +++ b/content/compose/environment-variables/envvars.md @@ -6,7 +6,7 @@ aliases: - /compose/reference/envvars/ --- -Compose already comes with pre-defined environment variables. It also inherits common Docker CLI environment variables, such as `DOCKER_HOST` and `DOCKER_CONTEXT`. See [Docker CLI environment variable reference](/engine/reference/commandline/cli/#environment-variables) for details. +Compose already comes with pre-defined environment variables. It also inherits common Docker CLI environment variables, such as `DOCKER_HOST` and `DOCKER_CONTEXT`. See [Docker CLI environment variable reference](/reference/cli/docker/#environment-variables) for details. This page contains information on how you can set or change the following pre-defined environment variables if you need to: @@ -187,7 +187,7 @@ For more information, see [Migrate to Compose V2](../migrate.md). - `COMPOSE_API_VERSION` By default the API version is negotiated with the server. Use `DOCKER_API_VERSION`. - See the [Docker CLI environment variable reference](../../../engine/reference/commandline/cli/#environment-variables) page. + See the [Docker CLI environment variable reference](/reference/cli/docker/#environment-variables) page. - `COMPOSE_HTTP_TIMEOUT` - `COMPOSE_TLS_VERSION` - `COMPOSE_FORCE_WINDOWS_HOST` diff --git a/content/engine/security/trust/deploying_notary.md b/content/engine/security/trust/deploying_notary.md index ec14211ede..29d496723c 100644 --- a/content/engine/security/trust/deploying_notary.md +++ b/content/engine/security/trust/deploying_notary.md @@ -22,7 +22,7 @@ The easiest way to deploy Notary Server is by using Docker Compose. To follow th 3. Make sure that your Docker or Notary client trusts Notary Server's certificate before you try to interact with the Notary server. -See the instructions for [Docker](../../../engine/reference/commandline/cli.md#notary) or +See the instructions for [Docker](/reference/cli/docker/#notary) or for [Notary](https://github.com/docker/notary#using-notary) depending on which one you are using. ## If you want to use Notary in production diff --git a/content/network/proxy.md b/content/network/proxy.md index 6673e4f956..6720e32986 100644 --- a/content/network/proxy.md +++ b/content/network/proxy.md @@ -78,7 +78,7 @@ The following table describes the available configuration parameters. These settings are used to configure proxy environment variables for containers only, and not used as proxy settings for the Docker CLI or the Docker Engine itself. -Refer to the [environment variables](/engine/reference/commandline/cli/#environment-variables) +Refer to the [environment variables](/reference/cli/docker/#environment-variables) and [configure the Docker daemon to use a proxy server](../config/daemon/proxy.md#httphttps-proxy) sections for configuring proxy settings for the CLI and daemon. diff --git a/content/reference/cli/docker/_index.md b/content/reference/cli/docker/_index.md index 1d84371c44..6978a66c95 100644 --- a/content/reference/cli/docker/_index.md +++ b/content/reference/cli/docker/_index.md @@ -14,6 +14,7 @@ aliases: - /engine/reference/commandline/registry_ls/ - /engine/reference/commandline/registry_rmi/ - /engine/reference/commandline/docker/ +- /engine/reference/commandline/cli/ layout: cli --- diff --git a/data/engine-cli/docker.yaml b/data/engine-cli/docker.yaml index b108b21b3c..e748afd6d9 100644 --- a/data/engine-cli/docker.yaml +++ b/data/engine-cli/docker.yaml @@ -1,6 +1,345 @@ command: docker short: The base command for the Docker CLI. -long: The base command for the Docker CLI. +long: |- + Depending on your Docker system configuration, you may be required to preface + each `docker` command with `sudo`. To avoid having to use `sudo` with the + `docker` command, your system administrator can create a Unix group called + `docker` and add users to it. + + For more information about installing Docker or `sudo` configuration, refer to + the [installation](/install/) instructions for your operating system. + + ### Display help text + + To list the help on any command just execute the command, followed by the + `--help` option. + + ```console + $ docker run --help + + Usage: docker run [OPTIONS] IMAGE [COMMAND] [ARG...] + + Create and run a new container from an image + + Options: + --add-host value Add a custom host-to-IP mapping (host:ip) (default []) + -a, --attach value Attach to STDIN, STDOUT or STDERR (default []) + <...> + ``` + + ### Environment variables + + The following list of environment variables are supported by the `docker` command + line: + + | Variable | Description | + | :---------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + | `DOCKER_API_VERSION` | Override the negotiated API version to use for debugging (e.g. `1.19`) | + | `DOCKER_CERT_PATH` | Location of your authentication keys. This variable is used both by the `docker` CLI and the [`dockerd` daemon](/reference/cli/dockerd/) | + | `DOCKER_CONFIG` | The location of your client configuration files. | + | `DOCKER_CONTENT_TRUST_SERVER` | The URL of the Notary server to use. Defaults to the same URL as the registry. | + | `DOCKER_CONTENT_TRUST` | When set Docker uses notary to sign and verify images. Equates to `--disable-content-trust=false` for build, create, pull, push, run. | + | `DOCKER_CONTEXT` | Name of the `docker context` to use (overrides `DOCKER_HOST` env var and default context set with `docker context use`) | + | `DOCKER_CUSTOM_HEADERS` | (Experimental) Configure [custom HTTP headers](#custom-http-headers) to be sent by the client. Headers must be provided as a comma-separated list of `name=value` pairs. This is the equivalent to the `HttpHeaders` field in the configuration file. | + | `DOCKER_DEFAULT_PLATFORM` | Default platform for commands that take the `--platform` flag. | + | `DOCKER_HIDE_LEGACY_COMMANDS` | When set, Docker hides "legacy" top-level commands (such as `docker rm`, and `docker pull`) in `docker help` output, and only `Management commands` per object-type (e.g., `docker container`) are printed. This may become the default in a future release. | + | `DOCKER_HOST` | Daemon socket to connect to. | + | `DOCKER_TLS` | Enable TLS for connections made by the `docker` CLI (equivalent of the `--tls` command-line option). Set to a non-empty value to enable TLS. Note that TLS is enabled automatically if any of the other TLS options are set. | + | `DOCKER_TLS_VERIFY` | When set Docker uses TLS and verifies the remote. This variable is used both by the `docker` CLI and the [`dockerd` daemon](/reference/cli/dockerd/) | + | `BUILDKIT_PROGRESS` | Set type of progress output (`auto`, `plain`, `tty`, `rawjson`) when [building](/reference/cli/docker/image/build/) with [BuildKit backend](/build/buildkit/). Use plain to show container output (default `auto`). | + + Because Docker is developed using Go, you can also use any environment + variables used by the Go runtime. In particular, you may find these useful: + + | Variable | Description | + |:--------------|:-------------------------------------------------------------------------------| + | `HTTP_PROXY` | Proxy URL for HTTP requests unless overridden by NoProxy. | + | `HTTPS_PROXY` | Proxy URL for HTTPS requests unless overridden by NoProxy. | + | `NO_PROXY` | Comma-separated values specifying hosts that should be excluded from proxying. | + + See the [Go specification](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config) + for details on these variables. + + ### Option types + + Single character command line options can be combined, so rather than + typing `docker run -i -t --name test busybox sh`, + you can write `docker run -it --name test busybox sh`. + + #### Boolean + + Boolean options take the form `-d=false`. The value you see in the help text is + the default value which is set if you do **not** specify that flag. If you + specify a Boolean flag without a value, this will set the flag to `true`, + irrespective of the default value. + + For example, running `docker run -d` will set the value to `true`, so your + container **will** run in "detached" mode, in the background. + + Options which default to `true` (e.g., `docker build --rm=true`) can only be + set to the non-default value by explicitly setting them to `false`: + + ```console + $ docker build --rm=false . + ``` + + #### Multi + + You can specify options like `-a=[]` multiple times in a single command line, + for example in these commands: + + ```console + $ docker run -a stdin -a stdout -i -t ubuntu /bin/bash + + $ docker run -a stdin -a stdout -a stderr ubuntu /bin/ls + ``` + + Sometimes, multiple options can call for a more complex value string as for + `-v`: + + ```console + $ docker run -v /host:/container example/mysql + ``` + + > **Note** + > + > Do not use the `-t` and `-a stderr` options together due to + > limitations in the `pty` implementation. All `stderr` in `pty` mode + > simply goes to `stdout`. + + #### Strings and Integers + + Options like `--name=""` expect a string, and they + can only be specified once. Options like `-c=0` + expect an integer, and they can only be specified once. + + ### Configuration files + + By default, the Docker command line stores its configuration files in a + directory called `.docker` within your `$HOME` directory. + + Docker manages most of the files in the configuration directory + and you shouldn't modify them. However, you can modify the + `config.json` file to control certain aspects of how the `docker` + command behaves. + + You can modify the `docker` command behavior using environment + variables or command-line options. You can also use options within + `config.json` to modify some of the same behavior. If an environment variable + and the `--config` flag are set, the flag takes precedent over the environment + variable. Command line options override environment variables and environment + variables override properties you specify in a `config.json` file. + + #### Change the `.docker` directory + + To specify a different directory, use the `DOCKER_CONFIG` + environment variable or the `--config` command line option. If both are + specified, then the `--config` option overrides the `DOCKER_CONFIG` environment + variable. The example below overrides the `docker ps` command using a + `config.json` file located in the `~/testconfigs/` directory. + + ```console + $ docker --config ~/testconfigs/ ps + ``` + + This flag only applies to whatever command is being ran. For persistent + configuration, you can set the `DOCKER_CONFIG` environment variable in your + shell (e.g. `~/.profile` or `~/.bashrc`). The example below sets the new + directory to be `HOME/newdir/.docker`. + + ```console + $ echo export DOCKER_CONFIG=$HOME/newdir/.docker > ~/.profile + ``` + + ### Docker CLI configuration file (`config.json`) properties + + + + Use the Docker CLI configuration to customize settings for the `docker` CLI. The + configuration file uses JSON formatting, and properties: + + By default, configuration file is stored in `~/.docker/config.json`. Refer to the + [change the `.docker` directory](#change-the-docker-directory) section to use a + different location. + + > **Warning** + > + > The configuration file and other files inside the `~/.docker` configuration + > directory may contain sensitive information, such as authentication information + > for proxies or, depending on your credential store, credentials for your image + > registries. Review your configuration file's content before sharing with others, + > and prevent committing the file to version control. + + #### Customize the default output format for commands + + These fields lets you customize the default output format for some commands + if no `--format` flag is provided. + + | Property | Description | + | :--------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | `configFormat` | Custom default format for `docker config ls` output. See [`docker config ls`](/reference/cli/docker/config/ls/#format) for a list of supported formatting directives. | + | `imagesFormat` | Custom default format for `docker images` / `docker image ls` output. See [`docker images`](/reference/cli/docker/image/ls/#format) for a list of supported formatting directives. | + | `networksFormat` | Custom default format for `docker network ls` output. See [`docker network ls`](/reference/cli/docker/network/ls/#format) for a list of supported formatting directives. | + | `nodesFormat` | Custom default format for `docker node ls` output. See [`docker node ls`](/reference/cli/docker/node/ls/#format) for a list of supported formatting directives. | + | `pluginsFormat` | Custom default format for `docker plugin ls` output. See [`docker plugin ls`](/reference/cli/docker/plugin/ls/#format) for a list of supported formatting directives. | + | `psFormat` | Custom default format for `docker ps` / `docker container ps` output. See [`docker ps`](/reference/cli/docker/container/ls/#format) for a list of supported formatting directives. | + | `secretFormat` | Custom default format for `docker secret ls` output. See [`docker secret ls`](/reference/cli/docker/secret/ls/#format) for a list of supported formatting directives. | + | `serviceInspectFormat` | Custom default format for `docker service inspect` output. See [`docker service inspect`](/reference/cli/docker/service/inspect/#format) for a list of supported formatting directives. | + | `servicesFormat` | Custom default format for `docker service ls` output. See [`docker service ls`](/reference/cli/docker/service/ls/#format) for a list of supported formatting directives. | + | `statsFormat` | Custom default format for `docker stats` output. See [`docker stats`](/reference/cli/docker/container/stats/#format) for a list of supported formatting directives. | + | `tasksFormat` | Custom default format for `docker stack ps` output. See [`docker stack ps`](/reference/cli/docker/stack/ps/#format) for a list of supported formatting directives. | + | `volumesFormat` | Custom default format for `docker volume ls` output. See [`docker volume ls`](/reference/cli/docker/volume/ls/#format) for a list of supported formatting directives. | + + #### Custom HTTP headers + + The property `HttpHeaders` specifies a set of headers to include in all messages + sent from the Docker client to the daemon. Docker doesn't try to interpret or + understand these headers; it simply puts them into the messages. Docker does + not allow these headers to change any headers it sets for itself. + + Alternatively, use the `DOCKER_CUSTOM_HEADERS` [environment variable](#environment-variables), + which is available in v27.1 and higher. This environment-variable is experimental, + and its exact behavior may change. + + #### Credential store options + + The property `credsStore` specifies an external binary to serve as the default + credential store. When this property is set, `docker login` will attempt to + store credentials in the binary specified by `docker-credential-` which + is visible on `$PATH`. If this property isn't set, credentials are stored + in the `auths` property of the CLI configuration file. For more information, + see the [**Credential stores** section in the `docker login` documentation](/reference/cli/docker/login/#credential-stores) + + The property `credHelpers` specifies a set of credential helpers to use + preferentially over `credsStore` or `auths` when storing and retrieving + credentials for specific registries. If this property is set, the binary + `docker-credential-` will be used when storing or retrieving credentials + for a specific registry. For more information, see the + [**Credential helpers** section in the `docker login` documentation](/reference/cli/docker/login/#credential-helpers) + + #### Automatic proxy configuration for containers + + The property `proxies` specifies proxy environment variables to be automatically + set on containers, and set as `--build-arg` on containers used during `docker build`. + A `"default"` set of proxies can be configured, and will be used for any Docker + daemon that the client connects to, or a configuration per host (Docker daemon), + for example, `https://docker-daemon1.example.com`. The following properties can + be set for each environment: + + | Property | Description | + |:---------------|:--------------------------------------------------------------------------------------------------------| + | `httpProxy` | Default value of `HTTP_PROXY` and `http_proxy` for containers, and as `--build-arg` on `docker build` | + | `httpsProxy` | Default value of `HTTPS_PROXY` and `https_proxy` for containers, and as `--build-arg` on `docker build` | + | `ftpProxy` | Default value of `FTP_PROXY` and `ftp_proxy` for containers, and as `--build-arg` on `docker build` | + | `noProxy` | Default value of `NO_PROXY` and `no_proxy` for containers, and as `--build-arg` on `docker build` | + | `allProxy` | Default value of `ALL_PROXY` and `all_proxy` for containers, and as `--build-arg` on `docker build` | + + These settings are used to configure proxy settings for containers only, and not + used as proxy settings for the `docker` CLI or the `dockerd` daemon. Refer to the + [environment variables](#environment-variables) and [HTTP/HTTPS proxy](/config/daemon/proxy.md#httphttps-proxy) + sections for configuring proxy settings for the cli and daemon. + + > **Warning** + > + > Proxy settings may contain sensitive information (for example, if the proxy + > requires authentication). Environment variables are stored as plain text in + > the container's configuration, and as such can be inspected through the remote + > API or committed to an image when using `docker commit`. + { .warning } + + #### Default key-sequence to detach from containers + + Once attached to a container, users detach from it and leave it running using + the using `CTRL-p CTRL-q` key sequence. This detach key sequence is customizable + using the `detachKeys` property. Specify a `` value for the + property. The format of the `` is a comma-separated list of either + a letter [a-Z], or the `ctrl-` combined with any of the following: + + * `a-z` (a single lowercase alpha character ) + * `@` (at sign) + * `[` (left bracket) + * `\\` (two backward slashes) + * `_` (underscore) + * `^` (caret) + + Your customization applies to all containers started in with your Docker client. + Users can override your custom or the default key sequence on a per-container + basis. To do this, the user specifies the `--detach-keys` flag with the `docker + attach`, `docker exec`, `docker run` or `docker start` command. + + #### CLI plugin options + + The property `plugins` contains settings specific to CLI plugins. The + key is the plugin name, while the value is a further map of options, + which are specific to that plugin. + + #### Sample configuration file + + Following is a sample `config.json` file to illustrate the format used for + various fields: + + ```json + { + "HttpHeaders": { + "MyHeader": "MyValue" + }, + "psFormat": "table {{.ID}}\\t{{.Image}}\\t{{.Command}}\\t{{.Labels}}", + "imagesFormat": "table {{.ID}}\\t{{.Repository}}\\t{{.Tag}}\\t{{.CreatedAt}}", + "pluginsFormat": "table {{.ID}}\t{{.Name}}\t{{.Enabled}}", + "statsFormat": "table {{.Container}}\t{{.CPUPerc}}\t{{.MemUsage}}", + "servicesFormat": "table {{.ID}}\t{{.Name}}\t{{.Mode}}", + "secretFormat": "table {{.ID}}\t{{.Name}}\t{{.CreatedAt}}\t{{.UpdatedAt}}", + "configFormat": "table {{.ID}}\t{{.Name}}\t{{.CreatedAt}}\t{{.UpdatedAt}}", + "serviceInspectFormat": "pretty", + "nodesFormat": "table {{.ID}}\t{{.Hostname}}\t{{.Availability}}", + "detachKeys": "ctrl-e,e", + "credsStore": "secretservice", + "credHelpers": { + "awesomereg.example.org": "hip-star", + "unicorn.example.com": "vcbait" + }, + "plugins": { + "plugin1": { + "option": "value" + }, + "plugin2": { + "anotheroption": "anothervalue", + "athirdoption": "athirdvalue" + } + }, + "proxies": { + "default": { + "httpProxy": "http://user:pass@example.com:3128", + "httpsProxy": "https://my-proxy.example.com:3129", + "noProxy": "intra.mycorp.example.com", + "ftpProxy": "http://user:pass@example.com:3128", + "allProxy": "socks://example.com:1234" + }, + "https://manager1.mycorp.example.com:2377": { + "httpProxy": "http://user:pass@example.com:3128", + "httpsProxy": "https://my-proxy.example.com:3129" + } + } + } + ``` + + #### Experimental features + + Experimental features provide early access to future product functionality. + These features are intended for testing and feedback, and they may change + between releases without warning or can be removed from a future release. + + Starting with Docker 20.10, experimental CLI features are enabled by default, + and require no configuration to enable them. + + #### Notary + + If using your own notary server and a self-signed certificate or an internal + Certificate Authority, you need to place the certificate at + `tls//ca.crt` in your Docker config directory. + + Alternatively you can trust the certificate globally by adding it to your system's + list of root Certificate Authorities. cname: - docker attach - docker build @@ -164,6 +503,7 @@ options: shorthand: H value_type: list description: Daemon socket to connect to + details_url: '#host' deprecated: false hidden: false experimental: false @@ -231,6 +571,63 @@ options: experimentalcli: false kubernetes: false swarm: false +examples: |- + ### Specify daemon host (-H, --host) {#host} + + You can use the `-H`, `--host` flag to specify a socket to use when you invoke + a `docker` command. You can use the following protocols: + + | Scheme | Description | Example | + |----------------------------------------|---------------------------|----------------------------------| + | `unix://[]` | Unix socket (Linux only) | `unix:///var/run/docker.sock` | + | `tcp://[[:port]]` | TCP connection | `tcp://174.17.0.1:2376` | + | `ssh://[username@][:port]` | SSH connection | `ssh://user@192.168.64.5` | + | `npipe://[]` | Named pipe (Windows only) | `npipe:////./pipe/docker_engine` | + + If you don't specify the `-H` flag, and you're not using a custom + [context](/engine/context/working-with-contexts), + commands use the following default sockets: + + - `unix:///var/run/docker.sock` on macOS and Linux + - `npipe:////./pipe/docker_engine` on Windows + + To achieve a similar effect without having to specify the `-H` flag for every + command, you could also [create a context](/reference/cli/docker/context/create/), + or alternatively, use the + [`DOCKER_HOST` environment variable](#environment-variables). + + For more information about the `-H` flag, see + [Daemon socket option](/reference/cli/dockerd/#daemon-socket-option). + + #### Using TCP sockets + + The following example shows how to invoke `docker ps` over TCP, to a remote + daemon with IP address `174.17.0.1`, listening on port `2376`: + + ```console + $ docker -H tcp://174.17.0.1:2376 ps + ``` + + > **Note** + > + > By convention, the Docker daemon uses port `2376` for secure TLS connections, + > and port `2375` for insecure, non-TLS connections. + + #### Using SSH sockets + + When you use SSH invoke a command on a remote daemon, the request gets forwarded + to the `/var/run/docker.sock` Unix socket on the SSH host. + + ```console + $ docker -H ssh://user@192.168.64.5 ps + ``` + + You can optionally specify the location of the socket by appending a path + component to the end of the SSH address. + + ```console + $ docker -H ssh://user@192.168.64.5/var/run/docker.sock ps + ``` deprecated: false hidden: false experimental: false diff --git a/data/engine-cli/docker_container_attach.yaml b/data/engine-cli/docker_container_attach.yaml index 1b3d1ad29e..28fa871505 100644 --- a/data/engine-cli/docker_container_attach.yaml +++ b/data/engine-cli/docker_container_attach.yaml @@ -190,7 +190,7 @@ examples: |- These `a`, `ctrl-a`, `X`, or `ctrl-\\` values are all examples of valid key sequences. To configure a different configuration default key sequence for all - containers, see [**Configuration file** section](/engine/reference/commandline/cli/#configuration-files). + containers, see [**Configuration file** section](/reference/cli/docker/#configuration-files). deprecated: false hidden: false experimental: false diff --git a/data/engine-cli/docker_container_run.yaml b/data/engine-cli/docker_container_run.yaml index e12ddb4aac..13e2400063 100644 --- a/data/engine-cli/docker_container_run.yaml +++ b/data/engine-cli/docker_container_run.yaml @@ -1838,7 +1838,7 @@ examples: |- These `a`, `ctrl-a`, `X`, or `ctrl-\\` values are all examples of valid key sequences. To configure a different configuration default key sequence for all - containers, see [**Configuration file** section](/engine/reference/commandline/cli/#configuration-files). + containers, see [**Configuration file** section](/reference/cli/docker/#configuration-files). ### Add host device to container (--device) {#device} diff --git a/data/engine-cli/docker_image_push.yaml b/data/engine-cli/docker_image_push.yaml index 2d4fae01c5..89777eeded 100644 --- a/data/engine-cli/docker_image_push.yaml +++ b/data/engine-cli/docker_image_push.yaml @@ -53,6 +53,7 @@ options: value_type: string description: |- Push a platform-specific manifest as a single-platform image to the registry. + Image index won't be pushed, meaning that other manifests, including attestations won't be preserved. 'os[/arch[/variant]]': Explicit platform (eg. linux/amd64) deprecated: false hidden: false diff --git a/data/engine-cli/docker_push.yaml b/data/engine-cli/docker_push.yaml index 912911f6b5..dcd3095f86 100644 --- a/data/engine-cli/docker_push.yaml +++ b/data/engine-cli/docker_push.yaml @@ -31,6 +31,7 @@ options: value_type: string description: |- Push a platform-specific manifest as a single-platform image to the registry. + Image index won't be pushed, meaning that other manifests, including attestations won't be preserved. 'os[/arch[/variant]]': Explicit platform (eg. linux/amd64) deprecated: false hidden: false diff --git a/data/engine-cli/docker_service_create.yaml b/data/engine-cli/docker_service_create.yaml index 2c2b7d337e..55e91fec7d 100644 --- a/data/engine-cli/docker_service_create.yaml +++ b/data/engine-cli/docker_service_create.yaml @@ -412,6 +412,17 @@ options: experimentalcli: false kubernetes: false swarm: false + - option: oom-score-adj + value_type: int64 + default_value: "0" + description: Tune host's OOM preferences (-1000 to 1000) + deprecated: false + hidden: false + min_api_version: "1.46" + experimental: false + experimentalcli: false + kubernetes: false + swarm: false - option: placement-pref value_type: pref description: Add a placement preference diff --git a/data/engine-cli/docker_service_update.yaml b/data/engine-cli/docker_service_update.yaml index ea37a21a34..6f606db6ed 100644 --- a/data/engine-cli/docker_service_update.yaml +++ b/data/engine-cli/docker_service_update.yaml @@ -538,6 +538,17 @@ options: experimentalcli: false kubernetes: false swarm: false + - option: oom-score-adj + value_type: int64 + default_value: "0" + description: Tune host's OOM preferences (-1000 to 1000) + deprecated: false + hidden: false + min_api_version: "1.46" + experimental: false + experimentalcli: false + kubernetes: false + swarm: false - option: placement-pref-add value_type: pref description: Add a placement preference diff --git a/data/toc.yaml b/data/toc.yaml index 26aa8bc2fa..ada0ccdb6d 100644 --- a/data/toc.yaml +++ b/data/toc.yaml @@ -1654,8 +1654,6 @@ Manuals: title: Start containers automatically - sectiontitle: CLI section: - - path: /engine/reference/commandline/cli/ - title: Use the Docker CLI - path: /config/completion/ title: Completion - path: /config/filter/ diff --git a/go.mod b/go.mod index d3a0a54da1..c4098cbc14 100644 --- a/go.mod +++ b/go.mod @@ -6,7 +6,7 @@ toolchain go1.22.5 require ( github.com/docker/buildx v0.16.2 // indirect - github.com/docker/cli v27.0.3+incompatible // indirect + github.com/docker/cli v27.1.1+incompatible // indirect github.com/docker/compose/v2 v2.29.1 // indirect github.com/docker/scout-cli v1.13.0 // indirect github.com/moby/buildkit v0.15.1 // indirect @@ -15,7 +15,7 @@ require ( replace ( github.com/docker/buildx => github.com/docker/buildx v0.16.2 - github.com/docker/cli => github.com/docker/cli v27.0.3+incompatible + github.com/docker/cli => github.com/docker/cli v27.1.1+incompatible github.com/docker/compose/v2 => github.com/docker/compose/v2 v2.29.0 github.com/docker/scout-cli => github.com/docker/scout-cli v1.13.0 github.com/moby/buildkit => github.com/moby/buildkit v0.15.1 diff --git a/go.sum b/go.sum index dafe4219ac..2995573d4d 100644 --- a/go.sum +++ b/go.sum @@ -114,6 +114,8 @@ github.com/docker/cli v27.0.1+incompatible h1:d/OrlblkOTkhJ1IaAGD1bLgUBtFQC/oP0V github.com/docker/cli v27.0.1+incompatible/go.mod h1:JLrzqnKDaYBop7H2jaqPtU4hHvMKP+vjCwu2uszcLI8= github.com/docker/cli v27.0.3+incompatible h1:usGs0/BoBW8MWxGeEtqPMkzOY56jZ6kYlSN5BLDioCQ= github.com/docker/cli v27.0.3+incompatible/go.mod h1:JLrzqnKDaYBop7H2jaqPtU4hHvMKP+vjCwu2uszcLI8= +github.com/docker/cli v27.1.1+incompatible h1:goaZxOqs4QKxznZjjBWKONQci/MywhtRv2oNn0GkeZE= +github.com/docker/cli v27.1.1+incompatible/go.mod h1:JLrzqnKDaYBop7H2jaqPtU4hHvMKP+vjCwu2uszcLI8= github.com/docker/compose-cli v1.0.35 h1:uZyEHLalfqBS2PiTpA1LAULyJmuQ+YtZg7nG4Xl3/Cc= github.com/docker/compose-cli v1.0.35/go.mod h1:mSXI4hFLpRU3EtI8NTo32bNwI0UXSr8jnq+/rYjGAUU= github.com/docker/compose/v2 v2.22.0 h1:3rRz4L7tPU75wRsV8JZh2/aTgerQvPa1cpzZN+tHqUY= diff --git a/hugo.yaml b/hugo.yaml index 98e65cdbc9..847527041e 100644 --- a/hugo.yaml +++ b/hugo.yaml @@ -283,8 +283,6 @@ module: target: content/engine/deprecated.md - source: docs/reference/run.md target: content/engine/reference/run.md - - source: docs/reference/commandline/cli.md - target: content/engine/reference/commandline/cli.md - source: docs/reference/dockerd.md target: content/reference/cli/dockerd.md