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

Merge pull request #20573 from dvdksn/manuals-engine-refactor 

refactor: Docker Engine manuals section
This commit is contained in:
David Karlsson 2024-08-12 09:51:32 +02:00 committed by GitHub
parent d38ed68e04 52a1e5ff62
commit d20f452358
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
176 changed files with 947 additions and 878 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_vendor/github.com/docker/cli/docs/extend/index.md generated
View File

@ -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

408
_vendor/github.com/docker/cli/docs/reference/commandline/cli.md generated
View File

@ -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
<a name="configjson-properties"><!-- included for deep-links to old section --></a>
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-<value>` 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-<value>` 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 `<sequence>` value for the
property. The format of the `<sequence>` 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/<registry_url>/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
### <a name="host"></a> 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://[<path>]` | Unix socket (Linux only) | `unix:///var/run/docker.sock` |
| `tcp://[<IP or host>[:port]]` | TCP connection | `tcp://174.17.0.1:2376` |
| `ssh://[username@]<IP or host>[:port]` | SSH connection | `ssh://user@192.168.64.5` |
| `npipe://[<name>]` | 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.

29
_vendor/github.com/docker/cli/docs/reference/dockerd.md generated
View File

@ -133,16 +133,15 @@ 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.
the `docker` CLI. Refer to [Environment variables](https://docs.docker.com/reference/cli/docker/#environment-variables)
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. |
@ -170,7 +169,7 @@ in three ways:
options. (Docker Engine version 23.0 or later).
The command-line and configuration file options take precedence over environment
variables. Refer to [control and configure Docker with systemd](https://docs.docker.com/config/daemon/systemd/#httphttps-proxy)
variables. Refer to [control and configure Docker with systemd](https://docs.docker.com/engine/daemon/proxy/)
to set these environment variables on a host using `systemd`.
### Daemon socket option
@ -333,7 +332,7 @@ drivers: `overlay2`, `fuse-overlayfs`, `btrfs`, and `zfs`.
and is selected by default. Unless users have a strong reason to prefer another storage driver,
`overlay2` should be used.
You can find out more about storage drivers and how to select one in [Select a storage driver](https://docs.docker.com/storage/storagedriver/select-storage-driver/).
You can find out more about storage drivers and how to select one in [Select a storage driver](https://docs.docker.com/engine/storage/drivers/select-storage-driver/).
On Windows, the Docker daemon only supports the `windowsfilter` storage driver.
@ -425,7 +424,7 @@ installed outside of `PATH`, must be registered with the daemon, either via the
configuration file or using the `--add-runtime` command line flag.
For examples on how to use other container runtimes, see
[Alternative container runtimes](https://docs.docker.com/engine/alternative-runtimes/)
[Alternative container runtimes](https://docs.docker.com/engine/daemon/alternative-runtimes/)
##### Configure runtimes using `daemon.json`
@ -610,7 +609,7 @@ $ sudo dockerd --add-runtime <runtime>=<path>
Defining runtime arguments via the command line is not supported.
For an example configuration for a runc drop-in replacment, see
[Alternative container runtimes > youki](https://docs.docker.com/engine/alternative-runtimes/#youki)
[Alternative container runtimes > youki](https://docs.docker.com/engine/daemon/alternative-runtimes/#youki)
##### Configure the default container runtime
@ -784,7 +783,7 @@ Docker host's configuration:
This only adds the proxy and authentication to the Docker daemon's requests.
To use the proxy when building images and running containers, see
[Configure Docker to use a proxy server](https://docs.docker.com/network/proxy/)
[Configure Docker to use a proxy server](https://docs.docker.com/engine/cli/proxy/)
### Default `ulimit` settings
@ -953,7 +952,7 @@ to avoid collisions with other Prometheus exporters and services.
If you are running a Prometheus server you can add this address to your scrape configs
to have Prometheus collect metrics on Docker. For more information, see
[Collect Docker metrics with Prometheus](https://docs.docker.com/config/daemon/prometheus/).
[Collect Docker metrics with Prometheus](https://docs.docker.com/engine/daemon/prometheus/).
#### Node generic resources
@ -1152,7 +1151,7 @@ The following is a full example of the allowed configuration options on Linux:
> daemon startup as a flag.
> On systems that use systemd to start the Docker daemon, `-H` is already set, so
> you can't use the `hosts` key in `daemon.json` to add listening addresses.
> See [custom Docker daemon options](https://docs.docker.com/config/daemon/systemd/#custom-docker-daemon-options)
> See [custom Docker daemon options](https://docs.docker.com/engine/daemon/proxy/#systemd-unit-file)
> for an example on how to configure the daemon using systemd drop-in files.
##### On Windows
@ -1235,7 +1234,7 @@ The list of feature options include:
- `containerd-snapshotter`: when set to `true`, the daemon uses containerd
snapshotters instead of the classic storage drivers for storing image and
container data. For more information, see
[containerd storage](https://docs.docker.com/storage/containerd/).
[containerd storage](https://docs.docker.com/engine/storage/containerd/).
- `windows-dns-proxy`: when set to `true`, the daemon's internal DNS resolver
will forward requests to external servers. Without this, most applications
running in the container will still be able to use secondary DNS servers
@ -1261,7 +1260,7 @@ The list of currently supported options that can be reconfigured is this:
| ---------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| `debug` | Toggles debug mode of the daemon. |
| `labels` | Replaces the daemon labels with a new set of labels. |
| `live-restore` | Toggles [live restore](https://docs.docker.com/config/containers/live-restore/). |
| `live-restore` | Toggles [live restore](https://docs.docker.com/engine/containers/live-restore/). |
| `max-concurrent-downloads` | Configures the max concurrent downloads for each pull. |
| `max-concurrent-uploads` | Configures the max concurrent uploads for each push. |
| `max-download-attempts` | Configures the max download attempts for each pull. |
@ -1363,7 +1362,7 @@ using the `daemon.json` file.
```
This example uses the `bridge` network driver. Refer to the
[bridge network driver page](https://docs.docker.com/network/drivers/bridge/#options)
[bridge network driver page](https://docs.docker.com/engine/network/drivers/bridge/#options)
for an overview of available driver options.
After changing the configuration and restarting the daemon, new networks that

2
_vendor/modules.txt
View File

@ -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

2
content/build/builders/_index.md
View File

@ -18,7 +18,7 @@ for your builds. This builder uses the BuildKit library bundled with the
daemon. This builder requires no configuration.
The default builder is directly bound to the Docker daemon and its
[context](../../engine/context/working-with-contexts.md). If you change the
[context](/engine/manage-resources/contexts.md). If you change the
Docker context, your `default` builder refers to the new Docker context.
## Build drivers

2
content/build/building/annotations.md
View File

@ -211,5 +211,5 @@ Reference information:
[config]: https://github.com/opencontainers/image-spec/blob/main/config.md
[descriptors]: https://github.com/opencontainers/image-spec/blob/main/descriptor.md
[indexes]: https://github.com/opencontainers/image-spec/blob/main/image-index.md
[labels]: ../../config/labels-custom-metadata.md
[labels]: /engine/manage-resources/labels.md
[manifests]: https://github.com/opencontainers/image-spec/blob/main/manifest.md

8
content/build/building/best-practices.md
View File

@ -145,14 +145,14 @@ database, and an in-memory cache in a decoupled manner.
Limiting each container to one process is a good rule of thumb, but it's not a
hard and fast rule. For example, not only can containers be
[spawned with an init process](../../engine/reference/run.md#specify-an-init-process),
[spawned with an init process](/engine/containers/run.md#specify-an-init-process),
some programs might spawn additional processes of their own accord. For
instance, [Celery](https://docs.celeryproject.org/) can spawn multiple worker
processes, and [Apache](https://httpd.apache.org/) can create one process per
request.
Use your best judgment to keep containers as clean and modular as possible. If
containers depend on each other, you can use [Docker container networks](../../network/index.md)
containers depend on each other, you can use [Docker container networks](/engine/network/_index.md)
to ensure that these containers can communicate.
## Sort multi-line arguments
@ -308,10 +308,10 @@ LABEL vendor=ACME\ Incorporated \
com.example.release-date="2015-02-12"
```
See [Understanding object labels](../../config/labels-custom-metadata.md)
See [Understanding object labels](/engine/manage-resources/labels.md)
for guidelines about acceptable label keys and values. For information about
querying labels, refer to the items related to filtering in
[Managing labels on objects](../../config/labels-custom-metadata.md#manage-labels-on-objects).
[Managing labels on objects](/engine/manage-resources/labels.md#manage-labels-on-objects).
See also [LABEL](../../reference/dockerfile.md#label) in the Dockerfile reference.
### RUN

4
content/build/drivers/docker-container.md
View File

@ -46,11 +46,11 @@ pass to `--driver-opt`:
| `default-load` | Boolean | `false` | Automatically load images to the Docker Engine image store. |
| `network` | String | | Sets the network mode for the container. |
| `cgroup-parent` | String | `/docker/buildx` | Sets the cgroup parent of the container if Docker is using the "cgroupfs" driver. |
| `restart-policy` | String | `unless-stopped` | Sets the container's [restart policy](../../config/containers/start-containers-automatically.md#use-a-restart-policy). |
| `restart-policy` | String | `unless-stopped` | Sets the container's [restart policy](/engine/containers/start-containers-automatically.md#use-a-restart-policy). |
| `env.<key>` | String | | Sets the environment variable `key` to the specified `value` in the container. |
Before you configure the resource limits for the container,
read about [configuring runtime resource constraints for containers](../../config/containers/resource_constraints/).
read about [configuring runtime resource constraints for containers](/engine/containers/resource_constraints/).
## Usage

2
content/build/guide/mounts.md
View File

@ -215,7 +215,7 @@ mounts.
Related information:
- [Dockerfile reference](../../reference/dockerfile.md#run---mount)
- [Bind mounts](../../storage/bind-mounts.md)
- [Bind mounts](/engine/storage/bind-mounts.md)
## Next steps

2
content/build/guide/multi-platform.md
View File

@ -241,7 +241,7 @@ Related information:
- [Multi-platfom images](../building/multi-platform.md)
- [containerd image store (Docker Desktop)](../../desktop/containerd.md)
- [containerd image store (Docker Engine)](../../storage/containerd.md)
- [containerd image store (Docker Engine)](/engine/storage/containerd.md)
You may also want to consider checking out
[xx - Dockerfile cross-compilation helpers](https://github.com/tonistiigi/xx).

4
content/compose/compose-file/05-services.md
View File

@ -1217,7 +1217,7 @@ There is a performance penalty for applications that swap memory to disk often.
- `none`: Turns off all container networking.
- `host`: Gives the container raw access to the host's network interface.
- `service:{name}`: Gives the containers access to the specified service only. For more information, see [Container networks](../../network/_index.md#container-networks).
- `service:{name}`: Gives the containers access to the specified service only. For more information, see [Container networks](/engine/network/_index.md#container-networks).
```yml
network_mode: "host"
@ -1574,7 +1574,7 @@ web:
runtime: runc
```
The default is `runc`. To use a different runtime, see [Alternative runtimes](../../engine/alternative-runtimes.md).
The default is `runc`. To use a different runtime, see [Alternative runtimes](/engine/daemon/alternative-runtimes.md).
### scale

4
content/compose/compose-file/06-networks.md
View File

@ -73,7 +73,7 @@ networks:
driver: bridge
```
For more information on drivers and available options, see [Network drivers](../../network/drivers/_index.md).
For more information on drivers and available options, see [Network drivers](/engine/network/drivers/_index.md).
### driver_opts
@ -103,7 +103,7 @@ networks:
### enable_ipv6
`enable_ipv6` enables IPv6 networking. For an example, see step four of [Create an IPv6 network](../../config/daemon/ipv6.md).
`enable_ipv6` enables IPv6 networking. For an example, see step four of [Create an IPv6 network](/engine/daemon/ipv6.md).
### external

4
content/compose/environment-variables/envvars.md
View File

@ -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`

2
content/compose/gettingstarted.md
View File

@ -240,7 +240,7 @@ services:
Whenever a file is changed, Compose syncs the file to the corresponding location under `/code` inside the container. Once copied, the bundler updates the running application without a restart.
For more information on how Compose Watch works, see [Use Compose Watch](file-watch.md). Alternatively, see [Manage data in containers](../storage/volumes.md) for other options.
For more information on how Compose Watch works, see [Use Compose Watch](file-watch.md). Alternatively, see [Manage data in containers](/engine/storage/volumes.md) for other options.
> **Note**
>

2
content/compose/gpu-support.md
View File

@ -4,7 +4,7 @@ keywords: documentation, docs, docker, compose, GPU access, NVIDIA, samples
title: Turn on GPU access with Docker Compose
---
Compose services can define GPU device reservations if the Docker host contains such devices and the Docker Daemon is set accordingly. For this, make sure you install the [prerequisites](../config/containers/resource_constraints.md#gpu) if you haven't already done so.
Compose services can define GPU device reservations if the Docker host contains such devices and the Docker Daemon is set accordingly. For this, make sure you install the [prerequisites](/engine/containers/resource_constraints.md#gpu) if you haven't already done so.
The examples in the following sections focus specifically on providing service containers access to GPU devices with Docker Compose.
You can use either `docker-compose` or `docker compose` commands. For more information, see [Migrate to Compose V2](migrate.md).

8
content/compose/networking.md
View File

@ -7,7 +7,7 @@ title: Networking in Compose
{{< include "compose-eol.md" >}}
By default Compose sets up a single
[network](../reference/cli/docker/network/create.md) for your app. Each
[network](/reference/cli/docker/network/create.md) for your app. Each
container for a service joins the default network and is both reachable by
other containers on that network, and discoverable by the service's name.
@ -85,13 +85,13 @@ See the [links reference](compose-file/05-services.md#links) for more informatio
## Multi-host networking
When deploying a Compose application on a Docker Engine with [Swarm mode enabled](../engine/swarm/index.md),
When deploying a Compose application on a Docker Engine with [Swarm mode enabled](../engine/swarm/_index.md),
you can make use of the built-in `overlay` driver to enable multi-host communication.
Overlay networks are always created as `attachable`. You can optionally set the [`attachable`](compose-file/06-networks.md#attachable) property to `false`.
Consult the [Swarm mode section](../engine/swarm/index.md), to see how to set up
a Swarm cluster, and the [Getting started with multi-host networking](../network/network-tutorial-overlay.md)
Consult the [Swarm mode section](../engine/swarm/_index.md), to see how to set up
a Swarm cluster, and the [Getting started with multi-host networking](/engine/network/tutorials/overlay.md)
to learn about multi-host overlay networks.
## Specify custom networks

2
content/compose/release-notes.md
View File

@ -2303,7 +2303,7 @@ naming scheme accordingly before upgrading.
- Added support for `extra_hosts` in build configuration
- Added support for the [long syntax](compose-file/legacy-versions.md) for volume entries, as previously introduced in the 3.2 format.
Using this syntax will create [mounts](../storage/bind-mounts.md) instead of volumes.
Using this syntax will create [mounts](/engine/storage/bind-mounts.md) instead of volumes.
#### Compose file version 2.1 and up

4
content/desktop/backup-and-restore.md
View File

@ -24,7 +24,7 @@ computer, for example.
Also note that filesystem changes in volume that are attached to the
container are not included in the image, and must be backed up separately.
If you used a [named volume](../storage/index.md#more-details-about-mount-types) to store container data, such as databases, refer to the [back up, restore, or migrate data volumes](../storage/volumes.md#back-up-restore-or-migrate-data-volumes) page in the storage section.
If you used a [named volume](/engine/storage/index.md#more-details-about-mount-types) to store container data, such as databases, refer to the [back up, restore, or migrate data volumes](/engine/storage/volumes.md#back-up-restore-or-migrate-data-volumes) page in the storage section.
2. Use [`docker push`](../reference/cli/docker/image/push.md) to push any
images you have built locally and want to keep to the [Docker Hub registry](../docker-hub/index.md).
@ -49,4 +49,4 @@ and [install a different version](release-notes.md) or reset Docker Desktop to f
2. Re-create your containers if needed, using [`docker run`](../reference/cli/docker/container/run.md),
or [Docker Compose](../compose/index.md).
Refer to the [backup, restore, or migrate data volumes](../storage/volumes.md#back-up-restore-or-migrate-data-volumes) page in the storage section to restore volume data.
Refer to the [backup, restore, or migrate data volumes](/engine/storage/volumes.md#back-up-restore-or-migrate-data-volumes) page in the storage section to restore volume data.

6
content/desktop/install/linux-install.md
View File

@ -74,7 +74,7 @@ $ sudo systemctl disable docker docker.socket containerd
The Docker CLI can be used to interact with multiple Docker Engines. For example,
you can use the same Docker CLI to control a local Docker Engine and to control
a remote Docker Engine instance running in the cloud. [Docker Contexts](../../engine/context/working-with-contexts.md)
a remote Docker Engine instance running in the cloud. [Docker Contexts](/engine/manage-resources/contexts.md)
allow you to switch between Docker Engines instances.
When installing Docker Desktop, a dedicated "desktop-linux" context is created to
@ -112,7 +112,7 @@ desktop-linux
Current context is now "desktop-linux"
```
Refer to the [Docker Context documentation](../../engine/context/working-with-contexts.md) for more details.
Refer to the [Docker Context documentation](/engine/manage-resources/contexts.md) for more details.
{{< /accordion >}}
@ -241,7 +241,7 @@ Sign out and sign back in so that your group membership is re-evaluated.
- Explore [Docker's core subscriptions](https://www.docker.com/pricing/) to see what Docker can offer you.
- [Get started with Docker](../../guides/getting-started/_index.md).
- [Explore Docker Desktop](../use-desktop/index.md) and all its features.
- [Explore Docker Desktop](../use-desktop/_index.md) and all its features.
- [Troubleshooting](../troubleshoot/overview.md) describes common problems, workarounds, how to run and submit diagnostics, and submit issues.
- [FAQs](../faqs/general.md) provide answers to frequently asked questions.
- [Release notes](../release-notes.md) lists component updates, new features, and improvements associated with Docker Desktop releases.

2
content/desktop/networking.md
View File

@ -181,7 +181,7 @@ container to random ports on the host.
$ docker run -d -P --name webserver nginx
```
Alternatively, you can also use [host networking](../network/drivers/host.md#docker-desktop)
Alternatively, you can also use [host networking](/engine/network/drivers/host.md#docker-desktop)
to give the container direct access to the network stack of the host.
See the [run command](../reference/cli/docker/container/run.md) for more details on

2
content/desktop/previous-versions/archive-mac.md
View File

@ -36,7 +36,7 @@ This page contains release notes for older versions of Docker Desktop for Mac.
- Re-enable raw as the default disk format for users running macOS 10.13.4 and higher. Note this change only takes effect after a "reset to factory defaults" or "remove all data" (from the Whale menu -> Preferences -> Reset). Related to [docker/for-mac#2625](https://github.com/docker/for-mac/issues/2625)
* Bug fixes and minor changes
- AUFS storage driver is deprecated in Docker Desktop and AUFS support will be removed in the next major release. You can continue with AUFS in Docker Desktop 18.06.x, but you will need to reset disk image (in Preferences > Reset menu) before updating to the next major update. You can check documentation to [save images](/reference/cli/docker/image/save/#examples) and [back up volumes](../../storage/volumes.md#back-up-restore-or-migrate-data-volumes)
- AUFS storage driver is deprecated in Docker Desktop and AUFS support will be removed in the next major release. You can continue with AUFS in Docker Desktop 18.06.x, but you will need to reset disk image (in Preferences > Reset menu) before updating to the next major update. You can check documentation to [save images](/reference/cli/docker/image/save/#examples) and [back up volumes](/engine/storage/volumes.md#back-up-restore-or-migrate-data-volumes)
- OS X El Captain 10.11 is deprecated in Docker Desktop. You will not be able to install updates after Docker Desktop 18.06.x. We recommend upgrading to the latest version of macOS.
- Fix bug which would cause VM logs to be written to RAM rather than disk in some cases, and the VM to hang. See [docker/for-mac#2984](https://github.com/docker/for-mac/issues/2984)
- Fix network connection leak triggered by haproxy TCP health-checks [docker/for-mac#1132](https://github.com/docker/for-mac/issues/1132)

2
content/desktop/previous-versions/archive-windows.md
View File

@ -50,7 +50,7 @@ This page contains release notes for older versions of Docker Desktop for Window
- Kubernetes Support. You can now run a single-node Kubernetes cluster from the "Kubernetes" Pane in Docker for Windows settings and use kubectl commands as well as Docker commands. See [the Kubernetes section](../kubernetes.md)
* Bug fixes and minor changes
- AUFS storage driver is deprecated in Docker Desktop and AUFS support will be removed in the next major release. You can continue with AUFS in Docker Desktop 18.06.x, but you will need to reset the disk image (in Settings > Reset menu) before updating to the next major update. You can check documentation to [save images](/reference/cli/docker/image/save/#examples) and [backup volumes](../../storage/volumes.md#back-up-restore-or-migrate-data-volumes)
- AUFS storage driver is deprecated in Docker Desktop and AUFS support will be removed in the next major release. You can continue with AUFS in Docker Desktop 18.06.x, but you will need to reset the disk image (in Settings > Reset menu) before updating to the next major update. You can check documentation to [save images](/reference/cli/docker/image/save/#examples) and [backup volumes](/engine/storage/volumes.md#back-up-restore-or-migrate-data-volumes)
- Fix bug which would in some cases cause virtual machine logs to be written to RAM rather than disk, and the virtual machine to hang.
- Fix security issue with named pipe connection to docker service.
- Fix VPNKit memory leak. Fixes [docker/for-win#2087](https://github.com/docker/for-win/issues/2087), [moby/vpnkit#371](https://github.com/moby/vpnkit/issues/371)

2
content/desktop/previous-versions/edge-releases-mac.md
View File

@ -733,7 +733,7 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus
- Add an experimental SOCKS server to allow access to container networks, see [docker/for-mac#2670](https://github.com/docker/for-mac/issues/2670#issuecomment-372365274). Also see [docker/for-mac#2721](https://github.com/docker/for-mac/issues/2721)
* Bug fixes and minor changes
- AUFS storage driver is deprecated in Docker Desktop and AUFS support will be removed in the next major release. You can continue with AUFS in Docker Desktop 18.06.x, but you will need to reset disk image (in Preferences > Reset menu) before updating to the next major update. You can check documentation to [save images](/reference/cli/docker/image/save/#examples) and [back up volumes](../../storage/volumes.md#back-up-restore-or-migrate-data-volumes)
- AUFS storage driver is deprecated in Docker Desktop and AUFS support will be removed in the next major release. You can continue with AUFS in Docker Desktop 18.06.x, but you will need to reset disk image (in Preferences > Reset menu) before updating to the next major update. You can check documentation to [save images](/reference/cli/docker/image/save/#examples) and [back up volumes](/engine/storage/volumes.md#back-up-restore-or-migrate-data-volumes)
- Fix startup issue with AUFS [docker/for-mac#2804](https://github.com/docker/for-mac/issues/2804)
- Fix status bug which could prevent the Kubernetes cluster from starting. Fixes [docker/for-mac#2990](https://github.com/docker/for-mac/issues/2990)
- Fix bug which would cause virtual machine logs to be written to RAM rather than disk in some cases, and the virtual machine to hang. See [docker/for-mac#2984](https://github.com/docker/for-mac/issues/2984)

2
content/desktop/previous-versions/edge-releases-windows.md
View File

@ -954,7 +954,7 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus
- New Kubernetes menu item allowing to switch Kubernetes context & connect to clusters other than the local one.
* Bug fixes and minor changes
- AUFS storage driver is deprecated in Docker Desktop and AUFS support will be removed in the next major release. You can continue with AUFS in Docker Desktop 18.06.x, but you will need to reset disk image (in Settings > Reset menu) before updating to the next major update. You can check documentation to [save images](/reference/cli/docker/image/save/#examples) and [back up volumes](../../storage/volumes.md#back-up-restore-or-migrate-data-volumes)
- AUFS storage driver is deprecated in Docker Desktop and AUFS support will be removed in the next major release. You can continue with AUFS in Docker Desktop 18.06.x, but you will need to reset disk image (in Settings > Reset menu) before updating to the next major update. You can check documentation to [save images](/reference/cli/docker/image/save/#examples) and [back up volumes](/engine/storage/volumes.md#back-up-restore-or-migrate-data-volumes)
- Fix startup issue with AUFS
- Fix status bug which could prevent the kubernetes cluster from starting.
- Fix bug which would cause VM logs to be written to RAM rather than disk in some cases, and the VM to hang.

2
content/desktop/release-notes.md
View File

@ -372,7 +372,7 @@ This can be resolved by adding the user to the **docker-users** group. Before st
- New [interactive Compose CLI (experimental)](../compose/environment-variables/envvars.md#compose_menu).
- Beta release of:
- Air-Gapped Containers with [Settings Management](hardened-desktop/air-gapped-containers/_index.md).
- [Host networking](../network/drivers/host.md#docker-desktop) in Docker Desktop.
- [Host networking](/engine/network/drivers/host.md#docker-desktop) in Docker Desktop.
- [Docker Debug](use-desktop/container.md#integrated-terminal) for running containers.
- [Volumes Backup & Share extension](use-desktop/volumes.md) functionality available in the **Volumes** tab.

8
content/desktop/settings/linux.md
View File

@ -137,8 +137,8 @@ File share settings are:
> * Shared folders are designed to allow application code to be edited
> on the host while being executed in containers. For non-code items
> such as cache directories or databases, the performance will be much
> better if they are stored in the Linux VM, using a [data volume](../../storage/volumes.md)
> (named volume) or [data container](../../storage/volumes.md).
> better if they are stored in the Linux VM, using a [data volume](/engine/storage/volumes.md)
> (named volume) or [data container](/engine/storage/volumes.md).
{ .tip }
### Proxies
@ -204,8 +204,8 @@ edit the file using your favorite text editor.
>
> Only the **Docker Desktop** daemon uses the configuration file under `$HOME/.docker`.
> If you manually install Docker Engine alongside Docker Desktop, the manually
> installed instance uses a `daemon.json` configuration file in a different location.
> Refer to [Configure the daemon](../../config/daemon/index.md) for more information
> installed instance uses a `daemon.json` configuration file in a different location.
> Refer to [Configure the daemon](/engine/daemon/_index.md) for more information
> about how to configure the Docker daemon on a manually installed Docker Engine.
To see the full list of possible configuration options, see the

4
content/desktop/settings/mac.md
View File

@ -169,8 +169,8 @@ File share settings are:
> * Shared folders are designed to allow application code to be edited
> on the host while being executed in containers. For non-code items
> such as cache directories or databases, the performance will be much
> better if they are stored in the Linux VM, using a [data volume](../../storage/volumes.md)
> (named volume) or [data container](../../storage/volumes.md).
> better if they are stored in the Linux VM, using a [data volume](/engine/storage/volumes.md)
> (named volume) or [data container](/engine/storage/volumes.md).
> * If you share the whole of your home directory into a container, MacOS may
> prompt you to give Docker access to personal areas of your home directory such as
> your Reminders or Downloads.

4
content/desktop/settings/windows.md
View File

@ -163,8 +163,8 @@ File share settings are:
> * Shared folders are designed to allow application code to be edited
> on the host while being executed in containers. For non-code items
> such as cache directories or databases, the performance will be much
> better if they are stored in the Linux VM, using a [data volume](../../storage/volumes.md)
> (named volume) or [data container](../../storage/volumes.md).
> better if they are stored in the Linux VM, using a [data volume](/engine/storage/volumes.md)
> (named volume) or [data container](/engine/storage/volumes.md).
> * Docker Desktop sets permissions to read/write/execute for users, groups and
> others [0777 or a+rwx](https://chmodcommand.com/chmod-0777/).
> This is not configurable. See [Permissions errors on data directories for shared volumes](../troubleshoot/topics.md).

2
content/desktop/synchronized-file-sharing.md
View File

@ -24,7 +24,7 @@ Synchronized file shares is ideal for developers who:
A Synchronized file share behaves just like a virtual file share, but takes advantage of a high-performance, low-latency code synchronization engine to create a synchronized cache of the host files on an ext4 filesystem within the Docker Desktop VM. If you make filesystem changes on the host or in the VM’s containers, it propagates via bidirectional synchronization.
After creating a file share instance, any container using a bind mount that points to a location on the host filesystem matching the specified synchronized file share location, or a subdirectory within it, utilizes the Synchronized File Shares feature. Bind mounts that don't satisfy this condition are passed to the normal virtual filesystem [bind-mounting mechanism](../storage/bind-mounts.md), for example VirtioFS or gRPC-FUSE.
After creating a file share instance, any container using a bind mount that points to a location on the host filesystem matching the specified synchronized file share location, or a subdirectory within it, utilizes the Synchronized File Shares feature. Bind mounts that don't satisfy this condition are passed to the normal virtual filesystem [bind-mounting mechanism](/engine/storage/bind-mounts.md), for example VirtioFS or gRPC-FUSE.
> **Note**
>

2
content/desktop/troubleshoot/overview.md
View File

@ -306,7 +306,7 @@ Desktop at `$HOME/.docker/desktop/log/`.
## View the Docker daemon logs
Refer to the [Read the daemon logs](../../config/daemon/logs.md) section
Refer to the [Read the daemon logs](/engine/daemon/logs.md) section
to learn how to view the Docker Daemon logs.
## Further resources

8
content/desktop/use-desktop/volumes.md
View File

@ -5,7 +5,7 @@ title: Explore Volumes
---
The **Volumes** view in Docker Dashboard lets you create, delete, and perform
other actions on your [volumes](../../storage/volumes.md). You can also see
other actions on your [volumes](/engine/storage/volumes.md). You can also see
which volumes are being used as well as inspect the files and folders in your
volumes.
@ -34,7 +34,7 @@ doing the following:
## Create a volume
You use the following steps to create an empty volume. Alternatively, if you
[start a container with a volume](../../storage/volumes.md#start-a-container-with-a-volume)
[start a container with a volume](/engine/storage/volumes.md#start-a-container-with-a-volume)
that doesn't yet exist, Docker creates the volume for you.
To create a volume:
@ -43,7 +43,7 @@ To create a volume:
2. In the **New Volume** modal, specify a volume name, and then select
**Create**.
To use the volume with a container, see [Use volumes](../../storage/volumes.md#start-a-container-with-a-volume).
To use the volume with a container, see [Use volumes](/engine/storage/volumes.md#start-a-container-with-a-volume).
## Inspect a volume
@ -246,4 +246,4 @@ To import a volume:
## Additional resources
- [Persisting container data](../../guides/docker-concepts/running-containers/persisting-container-data.md)
- [Use volumes](../../storage/volumes.md)
- [Use volumes](/engine/storage/volumes.md)

2
content/config/completion.md → content/engine/cli/completion.md
View File

@ -2,6 +2,8 @@
title: CLI completion
description: Set up your shell to get autocomplete for Docker commands and flags
keywords: cli, shell, fish, bash, zsh, completion, options
aliases:
- /config/completion/
---
You can generate a shell completion script for the Docker CLI using the `docker

40
content/config/filter.md → content/engine/cli/filter.md
View File

@ -4,6 +4,8 @@ description: |
Use the filtering function in the CLI to selectively include resources
that match the pattern you define.
keywords: cli, filter, commands, output, include, exclude
aliases:
- /config/filter/
---
You can use the `--filter` flag to scope your commands. When filtering, the
@ -70,7 +72,7 @@ busybox glibc 7338d0c72c65 2 hours ago 6.09MB
### Multiple negated filters
Some commands support negated filters on [labels](./labels-custom-metadata.md).
Some commands support negated filters on [labels](/engine/manage-resources/labels.md).
Negated filters only consider results that don't match the specified patterns.
The following command prunes all containers that aren't labeled `foo`.
@ -92,21 +94,21 @@ $ docker container prune --filter "label!=foo" --filter "label!=bar"
For more information about filtering commands, refer to the CLI reference
description for commands that support the `--filter` flag:
- [`docker config ls`](../reference/cli/docker/config/ls.md)
- [`docker container prune`](../reference/cli/docker/container/prune.md)
- [`docker image prune`](../reference/cli/docker/image/prune.md)
- [`docker image ls`](../reference/cli/docker/image/ls.md)
- [`docker network ls`](../reference/cli/docker/network/ls.md)
- [`docker network prune`](../reference/cli/docker/network/prune.md)
- [`docker node ls`](../reference/cli/docker/node/ls.md)
- [`docker node ps`](../reference/cli/docker/node/ps.md)
- [`docker plugin ls`](../reference/cli/docker/plugin/ls.md)
- [`docker container ls`](../reference/cli/docker/container/ls.md)
- [`docker search`](../reference/cli/docker/search.md)
- [`docker secret ls`](../reference/cli/docker/secret/ls.md)
- [`docker service ls`](../reference/cli/docker/service/ls.md)
- [`docker service ps`](../reference/cli/docker/service/ps.md)
- [`docker stack ps`](../reference/cli/docker/stack/ps.md)
- [`docker system prune`](../reference/cli/docker/system/prune.md)
- [`docker volume ls`](../reference/cli/docker/volume/ls.md)
- [`docker volume prune`](../reference/cli/docker/volume/prune.md)
- [`docker config ls`](/reference/cli/docker/config/ls.md)
- [`docker container prune`](/reference/cli/docker/container/prune.md)
- [`docker image prune`](/reference/cli/docker/image/prune.md)
- [`docker image ls`](/reference/cli/docker/image/ls.md)
- [`docker network ls`](/reference/cli/docker/network/ls.md)
- [`docker network prune`](/reference/cli/docker/network/prune.md)
- [`docker node ls`](/reference/cli/docker/node/ls.md)
- [`docker node ps`](/reference/cli/docker/node/ps.md)
- [`docker plugin ls`](/reference/cli/docker/plugin/ls.md)
- [`docker container ls`](/reference/cli/docker/container/ls.md)
- [`docker search`](/reference/cli/docker/search.md)
- [`docker secret ls`](/reference/cli/docker/secret/ls.md)
- [`docker service ls`](/reference/cli/docker/service/ls.md)
- [`docker service ps`](/reference/cli/docker/service/ps.md)
- [`docker stack ps`](/reference/cli/docker/stack/ps.md)
- [`docker system prune`](/reference/cli/docker/system/prune.md)
- [`docker volume ls`](/reference/cli/docker/volume/ls.md)
- [`docker volume prune`](/reference/cli/docker/volume/prune.md)

1
content/config/formatting.md → content/engine/cli/formatting.md
View File

@ -4,6 +4,7 @@ keywords: format, formatting, output, templates, log
title: Format command and log output
aliases:
- /engine/admin/formatting/
- /config/formatting/
---
Docker supports [Go templates](https://golang.org/pkg/text/template/) which you

2
content/config/otel.md → content/engine/cli/otel.md
View File

@ -2,6 +2,8 @@
title: OpenTelemetry for the Docker CLI
description: Learn about how to capture OpenTelemetry metrics for the Docker command line
keywords: otel, opentelemetry, telemetry, traces, tracing, metrics, logs
aliases:
- /config/otel/
---
{{< introduced engine 26.1.0 >}}

20
content/network/proxy.md → content/engine/cli/proxy.md
View File

@ -1,7 +1,9 @@
---
title: Configure Docker to use a proxy server
description: How to configure the Docker client to use a proxy server
title: Use a proxy server with the Docker CLI
description: How to configure the Docker client CLI to use a proxy server
keywords: network, networking, proxy, client
aliases:
- /network/proxy/
---
This page describes how to configure the Docker CLI to use proxies via
@ -9,12 +11,12 @@ environment variables in containers.
This page doesn't describe how to configure proxies for the Docker daemon.
For instructions on configuring Docker Desktop to use HTTP/HTTPS proxies, see
[proxies on Mac](../desktop/settings/mac.md#proxies),
[proxies on Windows](../desktop/settings/windows.md#proxies), and
[proxies on Linux](../desktop/settings/linux.md#proxies).
[proxies on Mac](/desktop/settings/mac.md#proxies),
[proxies on Windows](/desktop/settings/windows.md#proxies), and
[proxies on Linux](/desktop/settings/linux.md#proxies).
If you're running Docker Engine without Docker Desktop, refer to
[Configure the Docker daemon to use a proxy](../config/daemon/proxy.md)
[Configure the Docker daemon to use a proxy](/engine/daemon/proxy.md)
to learn how to configure a proxy server for the Docker daemon (`dockerd`) itself.
If your container needs to use an HTTP, HTTPS, or FTP proxy server, you can
@ -78,8 +80,8 @@ 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)
and [configure the Docker daemon to use a proxy server](../config/daemon/proxy.md#httphttps-proxy)
Refer to the [environment variables](/reference/cli/docker/#environment-variables)
and [configure the Docker daemon to use a proxy server](/engine/daemon/proxy.md)
sections for configuring proxy settings for the CLI and daemon.
### Run containers with a proxy configuration
@ -174,7 +176,7 @@ $ docker run --env HTTP_PROXY="http://proxy.example.com:3128" redis
For a list of all the proxy-related build arguments that you can use with the
`docker build` command, see
[Predefined ARGs](../reference/dockerfile.md#predefined-args).
[Predefined ARGs](/reference/dockerfile.md#predefined-args).
These proxy values are only available in the build container.
They're not included in the build output.

1
content/config/containers/live-restore.md → content/engine/containers/live-restore.md
View File

@ -4,6 +4,7 @@ keywords: docker, upgrade, daemon, dockerd, live-restore, daemonless container
title: Live restore
aliases:
- /engine/admin/live-restore/
- /config/containers/live-restore/
---
By default, when the Docker daemon terminates, it shuts down running containers.

1
content/config/containers/multi-service_container.md → content/engine/containers/multi-service_container.md
View File

@ -7,6 +7,7 @@ aliases:
- /engine/admin/multi-service_container/
- /engine/admin/using_supervisord/
- /engine/articles/using_supervisord/
- /config/containers/multi-service_container/
---
A container's main running process is the `ENTRYPOINT` and/or `CMD` at the

1
content/config/containers/resource_constraints.md → content/engine/containers/resource_constraints.md
View File

@ -4,6 +4,7 @@ description: Specify the runtime options for a container
keywords: docker, daemon, configuration, runtime
aliases:
- /engine/admin/resource_constraints/
- /config/containers/resource_constraints/
---
By default, a container has no resource constraints and can use as much of a

1
content/config/containers/runmetrics.md → content/engine/containers/runmetrics.md
View File

@ -7,6 +7,7 @@ aliases:
- /engine/articles/run_metrics/
- /engine/articles/runmetrics/
- /engine/admin/runmetrics/
- /config/containers/runmetrics/
---
## Docker stats

5
content/config/containers/start-containers-automatically.md → content/engine/containers/start-containers-automatically.md
View File

@ -6,9 +6,10 @@ aliases:
- /engine/articles/host_integration/
- /engine/admin/host_integration/
- /engine/admin/start-containers-automatically/
- /config/containers/start-containers-automatically/
---
Docker provides [restart policies](../../engine/reference/run.md#restart-policies---restart)
Docker provides [restart policies](/engine/containers/run.md#restart-policies---restart)
to control whether your containers start automatically when they exit, or when
Docker restarts. Restart policies start linked containers in the correct order.
Docker recommends that you use restart policies, and avoid using process
@ -66,7 +67,7 @@ Keep the following in mind when using restart policies:
- Restart policies only apply to containers. To configure restart policies for
Swarm services, see
[flags related to service restart](../../reference/cli/docker/service/create.md).
[flags related to service restart](/reference/cli/docker/service/create.md).
### Restarting foreground containers

13
content/config/daemon/_index.md → content/engine/daemon/_index.md
View File

@ -23,6 +23,7 @@ aliases:
- /engine/articles/dsc/
- /engine/articles/puppet/
- /engine/userguide/
- /config/daemon/
---
This page shows you how to customize the Docker daemon, `dockerd`.
@ -67,7 +68,7 @@ You can also explicitly specify the location of the configuration file on
startup, using the `dockerd --config-file` flag.
Learn about the available configuration options in the
[dockerd reference docs](../../reference/cli/dockerd.md#daemon-configuration-file)
[dockerd reference docs](/reference/cli/dockerd.md#daemon-configuration-file)
### Configuration using flags
@ -86,7 +87,7 @@ $ dockerd --debug \
```
Learn about the available configuration options in the
[dockerd reference docs](../../reference/cli/dockerd.md), or by
[dockerd reference docs](/reference/cli/dockerd.md), or by
running:
```console
@ -123,8 +124,8 @@ to troubleshoot.
Many specific configuration options are discussed throughout the Docker
documentation. Some places to go next include:
- [Automatically start containers](../containers/start-containers-automatically.md)
- [Limit a container's resources](../containers/resource_constraints.md)
- [Configure storage drivers](../../storage/storagedriver/select-storage-driver.md)
- [Container security](../../engine/security/_index.md)
- [Automatically start containers](/engine/containers/start-containers-automatically.md)
- [Limit a container's resources](/engine/containers/resource_constraints.md)
- [Configure storage drivers](/engine/storage/drivers/select-storage-driver.md)
- [Container security](/engine/security/_index.md)
- [Configure the Docker daemon to use a proxy](./proxy.md)

19
content/engine/alternative-runtimes.md → content/engine/daemon/alternative-runtimes.md
View File

@ -1,13 +1,12 @@
---
title: Alternative container runtimes
description: 'Docker Engine uses runc as the default container runtime, but you
description: |
Docker Engine uses runc as the default container runtime, but you
can specify alternative runtimes using the CLI or by configuring
the daemon
'
keywords: engine, runtime, containerd, runtime v2, shim
aliases:
- /engine/alternative-runtimes/
---
Docker Engine uses containerd for managing the container lifecycle,
@ -107,7 +106,7 @@ use the `runtimes` option in the daemon configuration file.
```
For more information about the configuration options for containerd shims, see
[Configure containerd shims](./../reference/cli/dockerd.md#configure-containerd-shims).
[Configure containerd shims](/reference/cli/dockerd.md#configure-containerd-shims).
## Examples
@ -127,7 +126,7 @@ youki functions as a drop-in replacement for runc, meaning it relies on the
runc shim to invoke the runtime binary. When you register runtimes acting as
runc replacements, you configure the path to the runtime executable, and
optionally a set of runtime arguments. For more information, see
[Configure runc drop-in replacements](./../reference/cli/dockerd.md#configure-runc-drop-in-replacements).
[Configure runc drop-in replacements](/reference/cli/dockerd.md#configure-runc-drop-in-replacements).
To add youki as a container runtime:
@ -176,7 +175,7 @@ plus the added sandboxing provided by the Wasm runtime environment.
To add Wasmtime as a container runtime, follow these steps:
1. Turn on the [containerd image store](../storage/containerd.md)
1. Turn on the [containerd image store](/engine/storage/containerd.md)
feature in the daemon configuration file.
> **Note**
@ -233,6 +232,6 @@ $ docker run --rm \
## Related information
- To learn more about the configuration options for container runtimes,
see [Configure container runtimes](./../reference/cli/dockerd.md#configure-container-runtimes).
see [Configure container runtimes](/reference/cli/dockerd.md#configure-container-runtimes).
- You can configure which runtime that the daemon should use as its default.
Refer to [Configure the default container runtime](./../reference/cli/dockerd.md#configure-the-default-container-runtime).
Refer to [Configure the default container runtime](/reference/cli/dockerd.md#configure-the-default-container-runtime).

0
content/config/daemon/images/prometheus-graph_idle.webp → content/engine/daemon/images/prometheus-graph_idle.webp
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 73 KiB

After

Width:  |  Height:  |  Size: 73 KiB

0
content/config/daemon/images/prometheus-graph_load.webp → content/engine/daemon/images/prometheus-graph_load.webp
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 74 KiB

After

Width:  |  Height:  |  Size: 74 KiB

0
content/config/daemon/images/prometheus-targets.webp → content/engine/daemon/images/prometheus-targets.webp
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 65 KiB

After

Width:  |  Height:  |  Size: 65 KiB

3
content/config/daemon/ipv6.md → content/engine/daemon/ipv6.md
View File

@ -4,6 +4,7 @@ description: How to enable IPv6 support in the Docker daemon
keywords: daemon, network, networking, ipv6
aliases:
- /engine/userguide/networking/default_network/ipv6/
- /config/daemon/ipv6/
---
IPv6 is only supported on Docker daemons running on Linux hosts.
@ -191,4 +192,4 @@ Engine.
## Next steps
- [Networking overview](../../network/index.md)
- [Networking overview](/engine/network/_index.md)

2
content/config/daemon/logs.md → content/engine/daemon/logs.md
View File

@ -2,6 +2,8 @@
title: Read the daemon logs
description: How to read the event logs for the Docker daemon
keywords: docker, daemon, configuration, troubleshooting, logging
aliases:
- /config/daemon/logs/
---
The daemon logs may help you diagnose problems. The logs may be saved in one of

1
content/config/daemon/prometheus.md → content/engine/daemon/prometheus.md
View File

@ -6,6 +6,7 @@ aliases:
- /engine/admin/prometheus/
- /config/thirdparty/monitoring/
- /config/thirdparty/prometheus/
- /config/daemon/prometheus/
---
[Prometheus](https://prometheus.io/) is an open-source systems monitoring and

3
content/config/daemon/proxy.md → content/engine/daemon/proxy.md
View File

@ -8,6 +8,7 @@ aliases:
- /engine/admin/systemd/
- /engine/articles/systemd/
- /config/daemon/systemd/
- /config/daemon/proxy/
---
<a name="httphttps-proxy"><!-- included for deep-links to old section --></a>
@ -19,7 +20,7 @@ and to reach other nodes in a Docker swarm.
This page describes how to configure a proxy for the Docker daemon. For
instructions on configuring proxy settings for the Docker CLI, see [Configure
Docker to use a proxy server](../../network/proxy.md).
Docker CLI to use a proxy server](/engine/cli/proxy.md).
There are two ways you can configure these settings:

2
content/config/daemon/remote-access.md → content/engine/daemon/remote-access.md
View File

@ -5,6 +5,8 @@ description:
socket
keywords: configuration, daemon, remote access, engine
title: Configure remote access for Docker daemon
aliases:
- /config/daemon/remote-access/
---
By default, the Docker daemon listens for connections on a Unix socket to accept

4
content/config/daemon/start.md → content/engine/daemon/start.md
View File

@ -2,6 +2,8 @@
title: Start the daemon
description: Starting the Docker daemon manually
keywords: docker, daemon, configuration, troubleshooting
aliases:
- /config/daemon/start/
---
This page shows how to start the daemon, either manually or using OS utilities.
@ -45,4 +47,4 @@ INFO[0000] Listening for HTTP on unix (/var/run/docker.sock)
```
To stop Docker when you have started it manually, issue a `Ctrl+C` in your
terminal.
terminal.

1
content/config/daemon/troubleshoot.md → content/engine/daemon/troubleshoot.md
View File

@ -8,6 +8,7 @@ keywords: |
aliases:
- /engine/install/troubleshoot/
- /storage/troubleshooting_volume_errors/
- /config/daemon/troubleshooting/
tags: [Troubleshooting]
---

4
content/engine/faq.md
View File

@ -101,14 +101,14 @@ thousands or even millions of containers.
### How do I connect Docker containers?
Currently the recommended way to connect containers is via the Docker network
feature. You can see details of [how to work with Docker networks](../network/drivers/bridge.md).
feature. You can see details of [how to work with Docker networks](/engine/network/drivers/bridge.md).
### How do I run more than one process in a Docker container?
This approach is discouraged for most use cases. For maximum efficiency and
isolation, each container should address one specific area of concern. However,
if you need to run multiple services within a single container, see
[Run multiple services in a container](../config/containers/multi-service_container.md).
[Run multiple services in a container](/engine/containers/multi-service_container.md).
### How do I report a security issue with Docker?

4
content/engine/install/debian.md
View File

@ -29,12 +29,12 @@ To get started with Docker Engine on Debian, make sure you
- If you use ufw or firewalld to manage firewall settings, be aware that
when you expose container ports using Docker, these ports bypass your
firewall rules. For more information, refer to
[Docker and ufw](../../network/packet-filtering-firewalls.md#docker-and-ufw).
[Docker and ufw](/engine/network/packet-filtering-firewalls.md#docker-and-ufw).
- Docker is only compatible with `iptables-nft` and `iptables-legacy`.
Firewall rules created with `nft` are not supported on a system with Docker installed.
Make sure that any firewall rulesets you use are created with `iptables` or `ip6tables`,
and that you add them to the `DOCKER-USER` chain,
see [Packet filtering and firewalls](../../network/packet-filtering-firewalls.md).
see [Packet filtering and firewalls](/engine/network/packet-filtering-firewalls.md).
### OS requirements

12
content/engine/install/linux-postinstall.md
View File

@ -117,11 +117,11 @@ $ sudo systemctl disable containerd.service
You can use systemd unit files to configure the Docker service on startup,
for example to add an HTTP proxy, set a different directory or partition for the
Docker runtime files, or other customizations. For an example, see
[Configure the daemon to use a proxy](../../config/daemon/proxy.md#systemd-unit-file).
[Configure the daemon to use a proxy](/engine/daemon/proxy.md#systemd-unit-file).
## Configure default logging driver
Docker provides [logging drivers](../../config/containers/logging/index.md) for
Docker provides [logging drivers](/engine/logging/_index.md) for
collecting and viewing log data from all containers running on a host. The
default logging driver, `json-file`, writes log data to JSON-formatted files on
the host filesystem. Over time, these log files expand in size, leading to
@ -131,13 +131,13 @@ To avoid issues with overusing disk for log data, consider one of the following
options:
- Configure the `json-file` logging driver to turn on
[log rotation](../../config/containers/logging/json-file.md).
[log rotation](/engine/logging/drivers/json-file.md).
- Use an
[alternative logging driver](../../config/containers/logging/configure.md#configure-the-default-logging-driver)
such as the ["local" logging driver](../../config/containers/logging/local.md)
[alternative logging driver](/engine/logging/configure.md#configure-the-default-logging-driver)
such as the ["local" logging driver](/engine/logging/drivers/local.md)
that performs log rotation by default.
- Use a logging driver that sends logs to a remote logging aggregator.
## Next steps
- Take a look at the [Docker workshop](../../guides/workshop/_index.md) to learn how to build an image and run it as a containerized application.
- Take a look at the [Docker workshop](/guides/workshop/_index.md) to learn how to build an image and run it as a containerized application.

4
content/engine/install/raspberry-pi-os.md
View File

@ -35,12 +35,12 @@ To get started with Docker Engine on Raspberry Pi OS, make sure you
- If you use ufw or firewalld to manage firewall settings, be aware that
when you expose container ports using Docker, these ports bypass your
firewall rules. For more information, refer to
[Docker and ufw](../../network/packet-filtering-firewalls.md#docker-and-ufw).
[Docker and ufw](/engine/network/packet-filtering-firewalls.md#docker-and-ufw).
- Docker is only compatible with `iptables-nft` and `iptables-legacy`.
Firewall rules created with `nft` are not supported on a system with Docker installed.
Make sure that any firewall rulesets you use are created with `iptables` or `ip6tables`,
and that you add them to the `DOCKER-USER` chain,
see [Packet filtering and firewalls](../../network/packet-filtering-firewalls.md).
see [Packet filtering and firewalls](/engine/network/packet-filtering-firewalls.md).
### OS requirements

4
content/engine/install/ubuntu.md
View File

@ -37,12 +37,12 @@ To get started with Docker Engine on Ubuntu, make sure you
- If you use ufw or firewalld to manage firewall settings, be aware that
when you expose container ports using Docker, these ports bypass your
firewall rules. For more information, refer to
[Docker and ufw](../../network/packet-filtering-firewalls.md#docker-and-ufw).
[Docker and ufw](/engine/network/packet-filtering-firewalls.md#docker-and-ufw).
- Docker is only compatible with `iptables-nft` and `iptables-legacy`.
Firewall rules created with `nft` are not supported on a system with Docker installed.
Make sure that any firewall rulesets you use are created with `iptables` or `ip6tables`,
and that you add them to the `DOCKER-USER` chain,
see [Packet filtering and firewalls](../../network/packet-filtering-firewalls.md).
see [Packet filtering and firewalls](/engine/network/packet-filtering-firewalls.md).
### OS requirements

1
content/config/containers/logging/_index.md → content/engine/logging/_index.md
View File

@ -5,6 +5,7 @@ title: View container logs
aliases:
- /engine/admin/logging/
- /engine/admin/logging/view_container_logs/
- /config/containers/logging/
---
The `docker logs` command shows information logged by a running container. The

45
content/config/containers/logging/configure.md → content/engine/logging/configure.md
View File

@ -9,22 +9,23 @@ aliases:
- /engine/admin/reference/logging/
- /engine/admin/logging/logentries/
- /engine/admin/logging/overview/
- /engine/admin/logging/
---
Docker includes multiple logging mechanisms to help you
[get information from running containers and services](index.md).
These mechanisms are called logging drivers. Each Docker daemon has a default
logging driver, which each container uses unless you configure it to use a
different logging driver, or log driver for short.
Docker includes multiple logging mechanisms to help you get information from
running containers and services. These mechanisms are called logging drivers.
Each Docker daemon has a default logging driver, which each container uses
unless you configure it to use a different logging driver, or log driver for
short.
As a default, Docker uses the [`json-file` logging driver](json-file.md), which
As a default, Docker uses the [`json-file` logging driver](drivers/json-file.md), which
caches container logs as JSON internally. In addition to using the logging drivers
included with Docker, you can also implement and use [logging driver plugins](plugins.md).
> **Tip: use the `local` logging driver to prevent disk-exhaustion**
>
> By default, no log-rotation is performed. As a result, log-files stored by the
> default [`json-file` logging driver](json-file.md) logging driver can cause
> default [`json-file` logging driver](drivers/json-file.md) logging driver can cause
> a significant amount of disk space to be used for containers that generate much
> output, which can lead to disk space exhaustion.
>
@ -36,7 +37,7 @@ included with Docker, you can also implement and use [logging driver plugins](pl
> log-rotation by default, and uses a more efficient file format. Refer to the
> [Configure the default logging driver](#configure-the-default-logging-driver)
> section below to learn how to configure the `local` logging driver as a default,
> and the [local file logging driver](local.md) page for more details about the
> and the [local file logging driver](drivers/local.md) page for more details about the
> `local` logging driver.
{ .tip }
@ -49,7 +50,7 @@ configuration file. Refer to the "daemon configuration file" section in the
for details.
The default logging driver is `json-file`. The following example sets the default
logging driver to the [`local` log driver](local.md):
logging driver to the [`local` log driver](drivers/local.md):
```json
{
@ -185,19 +186,19 @@ documentation for its configurable options, if applicable. If you are using
[logging driver plugins](plugins.md), you may
see more options.
| Driver | Description |
| :---------------------------- | :---------------------------------------------------------------------------------------------------------- |
| `none` | No logs are available for the container and `docker logs` does not return any output. |
| [`local`](local.md) | Logs are stored in a custom format designed for minimal overhead. |
| [`json-file`](json-file.md) | The logs are formatted as JSON. The default logging driver for Docker. |
| [`syslog`](syslog.md) | Writes logging messages to the `syslog` facility. The `syslog` daemon must be running on the host machine. |
| [`journald`](journald.md) | Writes log messages to `journald`. The `journald` daemon must be running on the host machine. |
| [`gelf`](gelf.md) | Writes log messages to a Graylog Extended Log Format (GELF) endpoint such as Graylog or Logstash. |
| [`fluentd`](fluentd.md) | Writes log messages to `fluentd` (forward input). The `fluentd` daemon must be running on the host machine. |
| [`awslogs`](awslogs.md) | Writes log messages to Amazon CloudWatch Logs. |
| [`splunk`](splunk.md) | Writes log messages to `splunk` using the HTTP Event Collector. |
| [`etwlogs`](etwlogs.md) | Writes log messages as Event Tracing for Windows (ETW) events. Only available on Windows platforms. |
| [`gcplogs`](gcplogs.md) | Writes log messages to Google Cloud Platform (GCP) Logging. |
| Driver | Description |
| :------------------------------------ | :---------------------------------------------------------------------------------------------------------- |
| `none` | No logs are available for the container and `docker logs` does not return any output. |
| [`local`](drivers/local.md) | Logs are stored in a custom format designed for minimal overhead. |
| [`json-file`](drivers/json-file.md) | The logs are formatted as JSON. The default logging driver for Docker. |
| [`syslog`](drivers/syslog.md) | Writes logging messages to the `syslog` facility. The `syslog` daemon must be running on the host machine. |
| [`journald`](drivers/journald.md) | Writes log messages to `journald`. The `journald` daemon must be running on the host machine. |
| [`gelf`](drivers/gelf.md) | Writes log messages to a Graylog Extended Log Format (GELF) endpoint such as Graylog or Logstash. |
| [`fluentd`](drivers/fluentd.md) | Writes log messages to `fluentd` (forward input). The `fluentd` daemon must be running on the host machine. |
| [`awslogs`](drivers/awslogs.md) | Writes log messages to Amazon CloudWatch Logs. |
| [`splunk`](drivers/splunk.md) | Writes log messages to `splunk` using the HTTP Event Collector. |
| [`etwlogs`](drivers/etwlogs.md) | Writes log messages as Event Tracing for Windows (ETW) events. Only available on Windows platforms. |
| [`gcplogs`](drivers/gcplogs.md) | Writes log messages to Google Cloud Platform (GCP) Logging. |
## Limitations of logging drivers

1
content/config/containers/logging/awslogs.md → content/engine/logging/drivers/awslogs.md
View File

@ -5,6 +5,7 @@ title: Amazon CloudWatch Logs logging driver
aliases:
- /engine/reference/logging/awslogs/
- /engine/admin/logging/awslogs/
- /config/containers/logging/awslogs/
---
The `awslogs` logging driver sends container logs to

1
content/config/containers/logging/etwlogs.md → content/engine/logging/drivers/etwlogs.md
View File

@ -4,6 +4,7 @@ keywords: ETW, docker, logging, driver
title: ETW logging driver
aliases:
- /engine/admin/logging/etwlogs/
- /config/containers/logging/etwlogs/
---
The Event Tracing for Windows (ETW) logging driver forwards container logs as ETW events.

1
content/config/containers/logging/fluentd.md → content/engine/logging/drivers/fluentd.md
View File

@ -6,6 +6,7 @@ aliases:
- /engine/reference/logging/fluentd/
- /reference/logging/fluentd/
- /engine/admin/logging/fluentd/
- /config/containers/logging/fluentd/
---
The `fluentd` logging driver sends container logs to the

1
content/config/containers/logging/gcplogs.md → content/engine/logging/drivers/gcplogs.md
View File

@ -4,6 +4,7 @@ keywords: gcplogs, google, docker, logging, driver
title: Google Cloud Logging driver
aliases:
- /engine/admin/logging/gcplogs/
- /config/containers/logging/gcplogs/
---
The Google Cloud Logging driver sends container logs to

1
content/config/containers/logging/gelf.md → content/engine/logging/drivers/gelf.md
View File

@ -5,6 +5,7 @@ title: Graylog Extended Format logging driver
aliases:
- /engine/reference/logging/gelf/
- /engine/admin/logging/gelf/
- /config/containers/logging/gelf/
---
The `gelf` logging driver is a convenient format that's understood by a number of tools such as

1
content/config/containers/logging/journald.md → content/engine/logging/drivers/journald.md
View File

@ -5,6 +5,7 @@ title: Journald logging driver
aliases:
- /engine/reference/logging/journald/
- /engine/admin/logging/journald/
- /config/containers/logging/journald/
---
The `journald` logging driver sends container logs to the

1
content/config/containers/logging/json-file.md → content/engine/logging/drivers/json-file.md
View File

@ -5,6 +5,7 @@ title: JSON File logging driver
aliases:
- /engine/reference/logging/json-file/
- /engine/admin/logging/json-file/
- /config/containers/logging/json-file/
---
By default, Docker captures the standard output (and standard error) of all your containers,

1
content/config/containers/logging/local.md → content/engine/logging/drivers/local.md
View File

@ -5,6 +5,7 @@ title: Local file logging driver
aliases:
- /engine/reference/logging/local/
- /engine/admin/logging/local/
- /config/containers/logging/local/
---
The `local` logging driver captures output from container's stdout/stderr and

1
content/config/containers/logging/splunk.md → content/engine/logging/drivers/splunk.md
View File

@ -5,6 +5,7 @@ title: Splunk logging driver
aliases:
- /engine/reference/logging/splunk/
- /engine/admin/logging/splunk/
- /config/containers/logging/splunk/
---
The `splunk` logging driver sends container logs to

1
content/config/containers/logging/syslog.md → content/engine/logging/drivers/syslog.md
View File

@ -5,6 +5,7 @@ title: Syslog logging driver
aliases:
- /engine/reference/logging/syslog/
- /engine/admin/logging/syslog/
- /config/containers/logging/syslog/
---
The `syslog` logging driver routes logs to a `syslog` server. The `syslog` protocol uses

8
content/config/containers/logging/dual-logging.md → content/engine/logging/dual-logging.md
View File

@ -6,12 +6,14 @@ keywords: >
docker, logging, driver, dual logging, dual logging, cache, ring-buffer,
configuration
title: Use docker logs with remote logging drivers
aliases:
- /config/containers/logging/dual-logging/
---
## Overview
You can use the `docker logs` command to read container logs regardless of the
configured logging driver or plugin. Docker Engine uses the [`local`](local.md)
configured logging driver or plugin. Docker Engine uses the [`local`](drivers/local.md)
logging driver to act as cache for reading the latest logs of your containers.
This is called dual logging. By default, the cache has log-file rotation
enabled, and is limited to a maximum of 5 files of 20 MB each (before
@ -109,7 +111,7 @@ as a default, with dual logging caching enabled:
### Configuration options
The dual logging cache accepts the same configuration options as the
[`local` logging driver](local.md), but with a `cache-` prefix. These options
[`local` logging driver](drivers/local.md), but with a `cache-` prefix. These options
can be specified per container, and defaults for new containers can be set using
the [daemon configuration file](/reference/cli/dockerd/#daemon-configuration-file).
@ -134,7 +136,7 @@ through a remote logging system, and if there is no need to read logs through
Caching can be disabled for individual containers or by default for new containers,
when using the [daemon configuration file](/reference/cli/dockerd/#daemon-configuration-file).
The following example uses the daemon configuration file to use the [`splunk`](splunk.md)
The following example uses the daemon configuration file to use the [`splunk`](drivers/splunk.md)
logging driver as a default, with caching disabled:
```console

1
content/config/containers/logging/log_tags.md → content/engine/logging/log_tags.md
View File

@ -5,6 +5,7 @@ title: Customize log driver output
aliases:
- /engine/reference/logging/log_tags/
- /engine/admin/logging/log_tags/
- /config/containers/logging/log_tags/
---
The `tag` log option specifies how to format a tag that identifies the

1
content/config/containers/logging/plugins.md → content/engine/logging/plugins.md
View File

@ -4,6 +4,7 @@ title: Use a logging driver plugin
keywords: logging, driver, plugins, monitoring
aliases:
- /engine/admin/logging/plugins/
- /engine/reference/logging/plugins/
---
Docker logging plugins allow you to extend and customize Docker's logging

2
content/engine/context/working-with-contexts.md → content/engine/manage-resources/contexts.md
View File

@ -2,6 +2,8 @@
title: Docker contexts
description: Learn about managing multiple daemons from a single client with contexts
keywords: engine, context, cli, daemons, remote
aliases:
- /engine/context/working-with-contexts/
---
## Introduction

41
content/config/labels-custom-metadata.md → content/engine/manage-resources/labels.md
View File

@ -4,6 +4,7 @@ keywords: labels, metadata, docker, annotations
title: Docker object labels
aliases:
- /engine/userguide/labels-custom-metadata/
- /config/labels-custom-metadata/
---
Labels are a mechanism for applying metadata to Docker objects, including:
@ -79,37 +80,37 @@ Labels on Swarm nodes and services can be updated dynamically.
- Images and containers
- [Adding labels to images](../reference/dockerfile.md#label)
- [Overriding a container's labels at runtime](../reference/cli/docker/container/run.md#label)
- [Inspecting labels on images or containers](../reference/cli/docker/inspect.md)
- [Filtering images by label](../reference/cli/docker/image/ls.md#filter)
- [Filtering containers by label](../reference/cli/docker/container/ls.md#filter)
- [Adding labels to images](/reference/dockerfile.md#label)
- [Overriding a container's labels at runtime](/reference/cli/docker/container/run.md#label)
- [Inspecting labels on images or containers](/reference/cli/docker/inspect.md)
- [Filtering images by label](/reference/cli/docker/image/ls.md#filter)
- [Filtering containers by label](/reference/cli/docker/container/ls.md#filter)
- Local Docker daemons
- [Adding labels to a Docker daemon at runtime](../reference/cli/dockerd.md)
- [Inspecting a Docker daemon's labels](../reference/cli/docker/system/info.md)
- [Adding labels to a Docker daemon at runtime](/reference/cli/dockerd.md)
- [Inspecting a Docker daemon's labels](/reference/cli/docker/system/info.md)
- Volumes
- [Adding labels to volumes](../reference/cli/docker/volume/create.md)
- [Inspecting a volume's labels](../reference/cli/docker/volume/inspect.md)
- [Filtering volumes by label](../reference/cli/docker/volume/ls.md#filter)
- [Adding labels to volumes](/reference/cli/docker/volume/create.md)
- [Inspecting a volume's labels](/reference/cli/docker/volume/inspect.md)
- [Filtering volumes by label](/reference/cli/docker/volume/ls.md#filter)
- Networks
- [Adding labels to a network](../reference/cli/docker/network/create.md)
- [Inspecting a network's labels](../reference/cli/docker/network/inspect.md)
- [Filtering networks by label](../reference/cli/docker/network/ls.md#filter)
- [Adding labels to a network](/reference/cli/docker/network/create.md)
- [Inspecting a network's labels](/reference/cli/docker/network/inspect.md)
- [Filtering networks by label](/reference/cli/docker/network/ls.md#filter)
- Swarm nodes
- [Adding or updating a Swarm node's labels](../reference/cli/docker/node/update.md#label-add)
- [Inspecting a Swarm node's labels](../reference/cli/docker/node/inspect.md)
- [Filtering Swarm nodes by label](../reference/cli/docker/node/ls.md#filter)
- [Adding or updating a Swarm node's labels](/reference/cli/docker/node/update.md#label-add)
- [Inspecting a Swarm node's labels](/reference/cli/docker/node/inspect.md)
- [Filtering Swarm nodes by label](/reference/cli/docker/node/ls.md#filter)
- Swarm services
- [Adding labels when creating a Swarm service](../reference/cli/docker/service/create.md#label)
- [Updating a Swarm service's labels](../reference/cli/docker/service/update.md)
- [Inspecting a Swarm service's labels](../reference/cli/docker/service/inspect.md)
- [Filtering Swarm services by label](../reference/cli/docker/service/ls.md#filter)
- [Adding labels when creating a Swarm service](/reference/cli/docker/service/create.md#label)
- [Updating a Swarm service's labels](/reference/cli/docker/service/update.md)
- [Inspecting a Swarm service's labels](/reference/cli/docker/service/inspect.md)
- [Filtering Swarm services by label](/reference/cli/docker/service/ls.md#filter)

11
content/config/pruning.md → content/engine/manage-resources/pruning.md
View File

@ -5,6 +5,7 @@ keywords: pruning, prune, images, volumes, containers, networks, disk, administr
title: Prune unused Docker objects
aliases:
- /engine/admin/pruning/
- /config/pruning/
---
Docker takes a conservative approach to cleaning up unused objects (often
@ -51,7 +52,7 @@ $ docker image prune -a --filter "until=24h"
```
Other filtering expressions are available. See the
[`docker image prune` reference](../reference/cli/docker/image/prune.md)
[`docker image prune` reference](/reference/cli/docker/image/prune.md)
for more examples.
## Prune containers
@ -82,7 +83,7 @@ $ docker container prune --filter "until=24h"
```
Other filtering expressions are available. See the
[`docker container prune` reference](../reference/cli/docker/container/prune.md)
[`docker container prune` reference](/reference/cli/docker/container/prune.md)
for more examples.
## Prune volumes
@ -110,7 +111,7 @@ $ docker volume prune --filter "label!=keep"
```
Other filtering expressions are available. See the
[`docker volume prune` reference](../reference/cli/docker/volume/prune.md)
[`docker volume prune` reference](/reference/cli/docker/volume/prune.md)
for more examples.
## Prune networks
@ -139,7 +140,7 @@ $ docker network prune --filter "until=24h"
```
Other filtering expressions are available. See the
[`docker network prune` reference](../reference/cli/docker/network/prune.md)
[`docker network prune` reference](/reference/cli/docker/network/prune.md)
for more examples.
## Prune everything
@ -187,5 +188,5 @@ $ docker system prune --filter "until=24h"
```
Other filtering expressions are available. See the
[`docker system prune` reference](../reference/cli/docker/system/prune.md)
[`docker system prune` reference](/reference/cli/docker/system/prune.md)
for more examples.

7
content/network/_index.md → content/engine/network/_index.md
View File

@ -11,6 +11,7 @@ aliases:
- /engine/userguide/networking/default_network/configure-dns/
- /engine/userguide/networking/default_network/container-communication/
- /engine/userguide/networking/dockernetworks/
- /network/
---
Container networking refers to the ability for containers to connect to and
@ -167,7 +168,7 @@ By default, containers inherit the DNS settings as defined in the
`/etc/resolv.conf` configuration file.
Containers that attach to the default `bridge` network receive a copy of this file.
Containers that attach to a
[custom network](network-tutorial-standalone.md#use-user-defined-bridge-networks)
[custom network](tutorials/standalone.md#use-user-defined-bridge-networks)
use Docker's embedded DNS server.
The embedded DNS server forwards external DNS lookups to the DNS servers configured on the host.
@ -189,10 +190,10 @@ Your container will have lines in `/etc/hosts` which define the hostname of the
container itself, as well as `localhost` and a few other common things. Custom
hosts, defined in `/etc/hosts` on the host machine, aren't inherited by
containers. To pass additional hosts into a container, refer to [add entries to
container hosts file](../reference/cli/docker/container/run.md#add-host) in the
container hosts file](/reference/cli/docker/container/run.md#add-host) in the
`docker run` reference documentation.
## Proxy server
If your container needs to use a proxy server, see
[Use a proxy server](proxy.md).
[Use a proxy server](/engine/daemon/proxy.md).

8
content/network/drivers/_index.md → content/engine/network/drivers/_index.md
View File

@ -70,7 +70,7 @@ exist by default, and provide core networking functionality:
Now that you understand the basics about Docker networks, deepen your
understanding using the following tutorials:
- [Standalone networking tutorial](../network-tutorial-standalone.md)
- [Host networking tutorial](../network-tutorial-host.md)
- [Overlay networking tutorial](../network-tutorial-overlay.md)
- [Macvlan networking tutorial](../network-tutorial-macvlan.md)
- [Standalone networking tutorial](/engine/network/tutorials/standalone.md)
- [Host networking tutorial](/engine/network/tutorials/host.md)
- [Overlay networking tutorial](/engine/network/tutorials/overlay.md)
- [Macvlan networking tutorial](/engine/network/tutorials/macvlan.md)

16
content/network/drivers/bridge.md → content/engine/network/drivers/bridge.md
View File

@ -91,8 +91,8 @@ network.**
compose file can define the shared variables.
- You can use swarm services instead of standalone containers, and take
advantage of shared [secrets](../../engine/swarm/secrets.md) and
[configs](../../engine/swarm/configs.md).
advantage of shared [secrets](/engine/swarm/secrets.md) and
[configs](/engine/swarm/configs.md).
Containers connected to the same user-defined bridge network effectively expose all ports
to each other. For a port to be accessible to containers or non-Docker hosts on
@ -132,7 +132,7 @@ daemon. The following table shows which options have equivalent flags in the
The Docker daemon supports a `--bridge` flag, which you can use to define
your own `docker0` bridge. Use this option if you want to run multiple daemon
instances on the same host. For details, see
[Run multiple daemons](../../reference/cli/dockerd.md#run-multiple-daemons).
[Run multiple daemons](/reference/cli/dockerd.md#run-multiple-daemons).
### Default host binding address
@ -166,7 +166,7 @@ $ docker network create my-net
You can specify the subnet, the IP address range, the gateway, and other
options. See the
[docker network create](../../reference/cli/docker/network/create.md#specify-advanced-options)
[docker network create](/reference/cli/docker/network/create.md#specify-advanced-options)
reference or the output of `docker network create --help` for details.
Use the `docker network rm` command to remove a user-defined bridge
@ -311,7 +311,7 @@ configured the IP address for the bridge.
## Next steps
- Go through the [standalone networking tutorial](../network-tutorial-standalone.md)
- Learn about [networking from the container's point of view](../index.md)
- Learn about [overlay networks](overlay.md)
- Learn about [Macvlan networks](macvlan.md)
- Go through the [standalone networking tutorial](/engine/network/tutorials/standalone.md)
- Learn about [networking from the container's point of view](../_index.md)
- Learn about [overlay networks](./overlay.md)
- Learn about [Macvlan networks](./macvlan.md)

12
content/network/drivers/host.md → content/engine/network/drivers/host.md
View File

@ -44,7 +44,7 @@ given swarm node.
## Docker Desktop
Host networking is also supported on Docker Desktop version 4.29 and later for Mac,
Windows, and Linux as a [beta feature](../../release-lifecycle.md#beta). To enable this feature, navigate to the **Features in development** tab in **Settings**, and then select **Enable host networking**.
Windows, and Linux as a [beta feature](/release-lifecycle.md#beta). To enable this feature, navigate to the **Features in development** tab in **Settings**, and then select **Enable host networking**.
This feature works in both directions. This means you can
access a server that is running in a container from your host and you can access
@ -98,8 +98,8 @@ network contradict each other.
## Next steps
- Go through the [host networking tutorial](../network-tutorial-host.md)
- Learn about [networking from the container's point of view](../index.md)
- Learn about [bridge networks](bridge.md)
- Learn about [overlay networks](overlay.md)
- Learn about [Macvlan networks](macvlan.md)
- Go through the [host networking tutorial](/engine/network/tutorials/host.md)
- Learn about [networking from the container's point of view](../_index.md)
- Learn about [bridge networks](./bridge.md)
- Learn about [overlay networks](./overlay.md)
- Learn about [Macvlan networks](./macvlan.md)

0
content/network/drivers/images/ipvlan-l3.gliffy → content/engine/network/drivers/images/ipvlan-l3.gliffy
View File

0
content/network/drivers/images/ipvlan-l3.webp → content/engine/network/drivers/images/ipvlan-l3.webp
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 34 KiB

After

Width:  |  Height:  |  Size: 34 KiB

0
content/network/drivers/images/ipvlan_l2_simple.gliffy → content/engine/network/drivers/images/ipvlan_l2_simple.gliffy
View File

0
content/network/drivers/images/ipvlan_l2_simple.png → content/engine/network/drivers/images/ipvlan_l2_simple.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 20 KiB

After

Width:  |  Height:  |  Size: 20 KiB

0
content/network/drivers/images/macvlan-bridge-ipvlan-l2.gliffy → content/engine/network/drivers/images/macvlan-bridge-ipvlan-l2.gliffy
View File

0
content/network/drivers/images/macvlan-bridge-ipvlan-l2.webp → content/engine/network/drivers/images/macvlan-bridge-ipvlan-l2.webp
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 36 KiB

After

Width:  |  Height:  |  Size: 36 KiB

0
content/network/drivers/images/vlans-deeper-look.gliffy → content/engine/network/drivers/images/vlans-deeper-look.gliffy
View File

0
content/network/drivers/images/vlans-deeper-look.webp → content/engine/network/drivers/images/vlans-deeper-look.webp
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 82 KiB

After

Width:  |  Height:  |  Size: 82 KiB

4
content/network/drivers/ipvlan.md → content/engine/network/drivers/ipvlan.md
View File

@ -11,7 +11,7 @@ The IPvlan driver gives users total control over both IPv4 and IPv6 addressing.
The VLAN driver builds on top of that in giving operators complete control of
layer 2 VLAN tagging and even IPvlan L3 routing for users interested in underlay
network integration. For overlay deployments that abstract away physical constraints
see the [multi-host overlay](../network-tutorial-overlay.md) driver.
see the [multi-host overlay](/engine/network/tutorials/overlay.md) driver.
IPvlan is a new twist on the tried and true network virtualization technique.
The Linux implementations are extremely lightweight because rather than using
@ -641,4 +641,4 @@ $ ip link del foo
As with all of the Libnetwork drivers, they can be mixed and matched, even as
far as running 3rd party ecosystem drivers in parallel for maximum flexibility
to the Docker user.
to the Docker user.

4
content/network/drivers/macvlan.md → content/engine/network/drivers/macvlan.md
View File

@ -107,7 +107,7 @@ $ docker network create -d ipvlan \
## Use IPv6
If you have [configured the Docker daemon to allow IPv6](../../config/daemon/ipv6.md),
If you have [configured the Docker daemon to allow IPv6](/engine/daemon/ipv6.md),
you can use dual-stack IPv4/IPv6 `macvlan` networks.
```console
@ -122,4 +122,4 @@ $ docker network create -d macvlan \
## Next steps
Learn how to use the Macvlan driver in the
[Macvlan networking tutorial](../network-tutorial-macvlan.md).
[Macvlan networking tutorial](/engine/network/tutorials/macvlan.md).

6
content/network/drivers/none.md → content/engine/network/drivers/none.md
View File

@ -31,8 +31,8 @@ $ docker run --rm --network none --name no-net-alpine alpine:latest ip addr show
## Next steps
- Go through the [host networking tutorial](../network-tutorial-host.md)
- Learn about [networking from the container's point of view](../index.md)
- Go through the [host networking tutorial](/engine/network/tutorials/host.md)
- Learn about [networking from the container's point of view](../_index.md)
- Learn about [bridge networks](bridge.md)
- Learn about [overlay networks](overlay.md)
- Learn about [Macvlan networks](macvlan.md)
- Learn about [Macvlan networks](macvlan.md)

10
content/network/drivers/overlay.md → content/engine/network/drivers/overlay.md
View File

@ -26,7 +26,7 @@ Swarm mode to establish a connection between the hosts.
This page describes overlay networks in general, and when used with standalone
containers. For information about overlay for Swarm services, see
[Manage Swarm service networks](../../engine/swarm/networking.md).
[Manage Swarm service networks](/engine/swarm/networking.md).
## Create an overlay network
@ -35,8 +35,8 @@ The following table lists ports that need to be open to each host participating
| Ports | Description |
| :--------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `2377/tcp` | The default Swarm control plane port, is configurable with [`docker swarm join --listen-addr`](../../reference/cli/docker/swarm/join.md#--listen-addr-value) |
| `4789/udp` | The default overlay traffic port, configurable with [`docker swarm init --data-path-addr`](../../reference/cli/docker/swarm/init.md#data-path-port) |
| `2377/tcp` | The default Swarm control plane port, is configurable with [`docker swarm join --listen-addr`](/reference/cli/docker/swarm/join.md#--listen-addr-value) |
| `4789/udp` | The default overlay traffic port, configurable with [`docker swarm init --data-path-addr`](/reference/cli/docker/swarm/init.md#data-path-port) |
| `7946/tcp`, `7946/udp` | Used for communication among nodes, not configurable |
To create an overlay network that containers on other Docker hosts can connect to,
@ -124,7 +124,7 @@ For more information about this limitation, see
## Next steps
- Go through the [overlay networking tutorial](../network-tutorial-overlay.md)
- Learn about [networking from the container's point of view](../index.md)
- Go through the [overlay networking tutorial](/engine/network/tutorials/overlay.md)
- Learn about [networking from the container's point of view](../_index.md)
- Learn about [standalone bridge networks](bridge.md)
- Learn about [Macvlan networks](macvlan.md)

3
content/network/links.md → content/engine/network/links.md
View File

@ -6,6 +6,7 @@ title: Legacy container links
aliases:
- /userguide/dockerlinks/
- /engine/userguide/networking/default_network/dockerlinks/
- /network/links/
---
>**Warning**
@ -415,4 +416,4 @@ root@aed84ee21bde:/opt/webapp# cat /etc/hosts
172.17.0.7 aed84ee21bde
<...>
172.17.0.9 db
```
```

1
content/network/packet-filtering-firewalls.md → content/engine/network/packet-filtering-firewalls.md
View File

@ -4,6 +4,7 @@ description: How Docker works with packet filtering, iptables, and firewalls
keywords: network, iptables, firewall
aliases:
- /network/iptables/
- /network/packet-filtering-firewalls/
---
On Linux, Docker creates `iptables` and `ip6tables` rules to implement network

14
content/network/network-tutorial-host.md → content/engine/network/tutorials/host.md
View File

@ -2,11 +2,13 @@
title: Networking using the host network
description: Tutorials for networking using the host network, disabling network isolation
keywords: networking, host, standalone
aliases:
- /network/network-tutorial-host/
---
This series of tutorials deals with networking standalone containers which bind
directly to the Docker host's network, with no network isolation. For other
networking topics, see the [overview](index.md).
networking topics, see the [overview](/engine/network/_index.md).
## Goal
@ -23,8 +25,8 @@ host.
Nginx listen on a different port, see the
[documentation for the `nginx` image](https://hub.docker.com/_/nginx/)
- The `host` networking driver only works on Linux hosts, but is availabe as a
[beta feature](../../release-lifecycle.md#beta) on Docker Desktop version 4.29
- The `host` networking driver only works on Linux hosts, but is available as a
[beta feature](/release-lifecycle.md#beta) on Docker Desktop version 4.29
and later for Mac, Windows, and Linux. To enable this feature, navigate to the
**Features in development** tab in **Settings**, and then select **Enable host networking**.
@ -63,6 +65,6 @@ host.
## Other networking tutorials
- [Standalone networking tutorial](network-tutorial-standalone.md)
- [Overlay networking tutorial](network-tutorial-overlay.md)
- [Macvlan networking tutorial](network-tutorial-macvlan.md)
- [Standalone networking tutorial](/engine/network/tutorials/standalone.md)
- [Overlay networking tutorial](/engine/network/tutorials/overlay.md)
- [Macvlan networking tutorial](/engine/network/tutorials/macvlan.md)

10
content/network/network-tutorial-macvlan.md → content/engine/network/tutorials/macvlan.md
View File

@ -3,13 +3,15 @@ title: Networking using a macvlan network
description: Tutorials for networking using a macvlan bridge network and 802.1Q trunk
bridge network
keywords: networking, macvlan, 802.1Q, standalone
aliases:
- /network/network-tutorial-macvlan/
---
This series of tutorials deals with networking standalone containers which
connect to `macvlan` networks. In this type of network, the Docker host accepts
requests for multiple MAC addresses at its IP address, and routes those requests
to the appropriate container. For other networking topics, see the
[overview](index.md).
[overview](/engine/network/_index.md).
## Goal
@ -218,6 +220,6 @@ be physically attached to the network.
## Other networking tutorials
- [Standalone networking tutorial](network-tutorial-standalone.md)
- [Overlay networking tutorial](network-tutorial-overlay.md)
- [Host networking tutorial](network-tutorial-host.md)
- [Standalone networking tutorial](/engine/network/tutorials/standalone.md)
- [Overlay networking tutorial](/engine/network/tutorials/overlay.md)
- [Host networking tutorial](/engine/network/tutorials/host.md)

13
content/network/network-tutorial-overlay.md → content/engine/network/tutorials/overlay.md
View File

@ -5,12 +5,13 @@ description: Tutorials for networking with swarm services and standalone contain
keywords: networking, bridge, routing, ports, swarm, overlay
aliases:
- /engine/userguide/networking/get-started-overlay/
- /network/network-tutorial-overlay/
---
This series of tutorials deals with networking for swarm services.
For networking with standalone containers, see
[Networking with standalone containers](network-tutorial-standalone.md). If you need to
learn more about Docker networking in general, see the [overview](index.md).
[Networking with standalone containers](/engine/network/tutorials/standalone.md). If you need to
learn more about Docker networking in general, see the [overview](/engine/network/_index.md).
This page includes the following tutorials. You can run each of them on
Linux, Windows, or a Mac, but for the last one, you need a second Docker
@ -59,7 +60,7 @@ If you don't have three hosts handy, an easy solution is to set up three
Ubuntu hosts on a cloud provider such as Amazon EC2, all on the same network
with all communications allowed to all hosts on that network (using a mechanism
such as EC2 security groups), and then to follow the
[installation instructions for Docker Engine - Community on Ubuntu](../engine/install/ubuntu.md).
[installation instructions for Docker Engine - Community on Ubuntu](/engine/install/ubuntu.md).
### Walkthrough
@ -436,6 +437,6 @@ example also uses Linux hosts, but the same commands work on Windows.
## Other networking tutorials
- [Host networking tutorial](network-tutorial-host.md)
- [Standalone networking tutorial](network-tutorial-standalone.md)
- [Macvlan networking tutorial](network-tutorial-macvlan.md)
- [Host networking tutorial](/engine/network/tutorials/host.md)
- [Standalone networking tutorial](/engine/network/tutorials/standalone.md)
- [Macvlan networking tutorial](/engine/network/tutorials/macvlan.md)

16
content/network/network-tutorial-standalone.md → content/engine/network/tutorials/standalone.md
View File

@ -2,12 +2,14 @@
title: Networking with standalone containers
description: Tutorials for networking with standalone containers
keywords: networking, bridge, routing, ports, overlay
aliases:
- /network/network-tutorial-standalone/
---
This series of tutorials deals with networking for standalone Docker containers.
For networking with swarm services, see
[Networking with swarm services](network-tutorial-overlay.md). If you need to
learn more about Docker networking in general, see the [overview](index.md).
[Networking with swarm services](/engine/network/tutorials/overlay.md). If you need to
learn more about Docker networking in general, see the [overview](_index.md).
This topic includes two different tutorials. You can run each of them on
Linux, Windows, or a Mac, but for the last one, you need a second Docker
@ -22,9 +24,9 @@ host running elsewhere.
running on the same Docker host. This is recommended for standalone containers
running in production.
Although [overlay networks](drivers/overlay.md) are generally used for swarm services,
Although [overlay networks](/engine/network/drivers/overlay.md) are generally used for swarm services,
you can also use an overlay network for standalone containers. That's covered as
part of the [tutorial on using overlay networks](network-tutorial-overlay.md#use-an-overlay-network-for-standalone-containers).
part of the [tutorial on using overlay networks](/engine/network/tutorials/overlay.md#use-an-overlay-network-for-standalone-containers).
## Use the default bridge network
@ -615,6 +617,6 @@ connected to both networks.
## Other networking tutorials
- [Host networking tutorial](network-tutorial-host.md)
- [Overlay networking tutorial](network-tutorial-overlay.md)
- [Macvlan networking tutorial](network-tutorial-macvlan.md)
- [Host networking tutorial](/engine/network/tutorials/host.md)
- [Overlay networking tutorial](/engine/network/tutorials/overlay.md)
- [Macvlan networking tutorial](/engine/network/tutorials/macvlan.md)

2
content/engine/release-notes/17.11.md
View File

@ -11,7 +11,7 @@ toc_max: 2
[containerd 1.0 beta](https://github.com/containerd/containerd/releases/tag/v1.0.0-beta.2).
Docker CE 17.11 and later don't recognize containers started with
previous Docker versions. If using
[Live Restore](../../config/containers/live-restore.md),
[Live Restore](/engine/containers/live-restore.md),
you must stop all containers before upgrading to Docker CE 17.11.
If you don't, any containers started by Docker versions that predate
17.11 aren't recognized by Docker after the upgrade and keep

2
content/engine/release-notes/18.06.md
View File

@ -184,7 +184,7 @@ toc_max: 2
* Set item-type for ExecIDs. [moby/moby#37121](https://github.com/moby/moby/pull/37121)
* Use go-systemd const instead of magic string in Linux version of dockerd. [moby/moby#37136](https://github.com/moby/moby/pull/37136)
* Use stdlib TLS dialer. [moby/moby#36687](https://github.com/moby/moby/pull/36687)
* Warn when an engine label using a reserved namespace (com.docker.\*, io.docker.\*, or org.dockerproject.\*) is configured, as per [Docker object labels](../../config/labels-custom-metadata.md). [moby/moby#36921](https://github.com/moby/moby/pull/36921)
* Warn when an engine label using a reserved namespace (com.docker.\*, io.docker.\*, or org.dockerproject.\*) is configured, as per [Docker object labels](/engine/manage-resources/labels.md). [moby/moby#36921](https://github.com/moby/moby/pull/36921)
- Fix missing plugin name in message. [moby/moby#37052](https://github.com/moby/moby/pull/37052)
- Fix link anchors in CONTRIBUTING.md. [moby/moby#37276](https://github.com/moby/moby/pull/37276)
- Fix link to Docker Toolbox. [moby/moby#37240](https://github.com/moby/moby/pull/37240)

Some files were not shown because too many files have changed in this diff Show More