- regular install @@ -81,187 +54,176 @@ you need to add this configuration in the Docker systemd service file.
-1. Create a systemd drop-in directory for the docker service:
+1. Create a systemd drop-in directory for the `docker` service:
- ```console
- $ sudo mkdir -p /etc/systemd/system/docker.service.d
- ```
+ ```console
+ $ sudo mkdir -p /etc/systemd/system/docker.service.d
+ ```
-2. Create a file named `/etc/systemd/system/docker.service.d/http-proxy.conf`
- that adds the `HTTP_PROXY` environment variable:
+2. Create a file named `/etc/systemd/system/docker.service.d/http-proxy.conf`
+ that adds the `HTTP_PROXY` environment variable:
- ```systemd
- [Service]
- Environment="HTTP_PROXY=http://proxy.example.com:80"
- ```
+ ```systemd
+ [Service]
+ Environment="HTTP_PROXY=http://proxy.example.com:80"
+ ```
- If you are behind an HTTPS proxy server, set the `HTTPS_PROXY` environment
- variable:
+ If you are behind an HTTPS proxy server, set the `HTTPS_PROXY` environment
+ variable:
- ```systemd
- [Service]
- Environment="HTTPS_PROXY=https://proxy.example.com:443"
- ```
-
- Multiple environment variables can be set; to set both a non-HTTPS and
- a HTTPs proxy;
+ ```systemd
+ [Service]
+ Environment="HTTPS_PROXY=https://proxy.example.com:443"
+ ```
- ```systemd
- [Service]
- Environment="HTTP_PROXY=http://proxy.example.com:80"
- Environment="HTTPS_PROXY=https://proxy.example.com:443"
- ```
-
- > **Note**
- >
- > Special characters in the proxy value, such as `#?!()[]{}`, must be double
- > escaped using `%%`. For example:
- >
- > ```
- > [Service]
- > Environment="HTTP_PROXY=http://domain%%5Cuser:complex%%23pass@proxy.example.com:8080/"
- > ```
-
-3. If you have internal Docker registries that you need to contact without
- proxying you can specify them via the `NO_PROXY` environment variable.
+ Multiple environment variables can be set; to set both a non-HTTPS and a
+ HTTPs proxy;
- The `NO_PROXY` variable specifies a string that contains comma-separated
- values for hosts that should be excluded from proxying. These are the
- options you can specify to exclude hosts:
- * IP address prefix (`1.2.3.4`)
- * Domain name, or a special DNS label (`*`)
- * A domain name matches that name and all subdomains. A domain name with
- a leading "." matches subdomains only. For example, given the domains
- `foo.example.com` and `example.com`:
- * `example.com` matches `example.com` and `foo.example.com`, and
- * `.example.com` matches only `foo.example.com`
- * A single asterisk (`*`) indicates that no proxying should be done
- * Literal port numbers are accepted by IP address prefixes (`1.2.3.4:80`)
- and domain names (`foo.example.com:80`)
-
- Config example:
+ ```systemd
+ [Service]
+ Environment="HTTP_PROXY=http://proxy.example.com:80"
+ Environment="HTTPS_PROXY=https://proxy.example.com:443"
+ ```
- ```systemd
- [Service]
- Environment="HTTP_PROXY=http://proxy.example.com:80"
- Environment="HTTPS_PROXY=https://proxy.example.com:443"
- Environment="NO_PROXY=localhost,127.0.0.1,docker-registry.example.com,.corp"
- ```
+ > **Note**
+ >
+ > Special characters in the proxy value, such as `#?!()[]{}`, must be double
+ > escaped using `%%`. For example:
+ >
+ > ```
+ > [Service]
+ > Environment="HTTP_PROXY=http://domain%%5Cuser:complex%%23pass@proxy.example.com:8080/"
+ > ```
-4. Flush changes and restart Docker
+3. If you have internal Docker registries that you need to contact without
+ proxying, you can specify them via the `NO_PROXY` environment variable.
- ```console
- $ sudo systemctl daemon-reload
- $ sudo systemctl restart docker
- ```
+ The `NO_PROXY` variable specifies a string that contains comma-separated
+ values for hosts that should be excluded from proxying. These are the options
+ you can specify to exclude hosts:
-5. Verify that the configuration has been loaded and matches the changes you
- made, for example:
+ - IP address prefix (`1.2.3.4`)
+ - Domain name, or a special DNS label (`*`)
+ - A domain name matches that name and all subdomains. A domain name with a
+ leading "." matches subdomains only. For example, given the domains
+ `foo.example.com` and `example.com`:
+ - `example.com` matches `example.com` and `foo.example.com`, and
+ - `.example.com` matches only `foo.example.com`
+ - A single asterisk (`*`) indicates that no proxying should be done
+ - Literal port numbers are accepted by IP address prefixes (`1.2.3.4:80`) and
+ domain names (`foo.example.com:80`)
- ```console
- $ sudo systemctl show --property=Environment docker
-
- Environment=HTTP_PROXY=http://proxy.example.com:80 HTTPS_PROXY=https://proxy.example.com:443 NO_PROXY=localhost,127.0.0.1,docker-registry.example.com,.corp
- ```
+ Config example:
+
+ ```systemd
+ [Service]
+ Environment="HTTP_PROXY=http://proxy.example.com:80"
+ Environment="HTTPS_PROXY=https://proxy.example.com:443"
+ Environment="NO_PROXY=localhost,127.0.0.1,docker-registry.example.com,.corp"
+ ```
+
+4. Flush changes and restart Docker
+
+ ```console
+ $ sudo systemctl daemon-reload
+ $ sudo systemctl restart docker
+ ```
+
+5. Verify that the configuration has been loaded and matches the changes you
+ made, for example:
+
+ ```console
+ $ sudo systemctl show --property=Environment docker
+
+ Environment=HTTP_PROXY=http://proxy.example.com:80 HTTPS_PROXY=https://proxy.example.com:443 NO_PROXY=localhost,127.0.0.1,docker-registry.example.com,.corp
+ ```
-1. Create a systemd drop-in directory for the docker service:
+1. Create a systemd drop-in directory for the `docker` service:
- ```console
- $ mkdir -p ~/.config/systemd/user/docker.service.d
- ```
+ ```console
+ $ mkdir -p ~/.config/systemd/user/docker.service.d
+ ```
-2. Create a file named `~/.config/systemd/user/docker.service.d/http-proxy.conf`
- that adds the `HTTP_PROXY` environment variable:
+2. Create a file named `~/.config/systemd/user/docker.service.d/http-proxy.conf`
+ that adds the `HTTP_PROXY` environment variable:
- ```systemd
- [Service]
- Environment="HTTP_PROXY=http://proxy.example.com:80"
- ```
+ ```systemd
+ [Service]
+ Environment="HTTP_PROXY=http://proxy.example.com:80"
+ ```
- If you are behind an HTTPS proxy server, set the `HTTPS_PROXY` environment
- variable:
+ If you are behind an HTTPS proxy server, set the `HTTPS_PROXY` environment
+ variable:
- ```systemd
- [Service]
- Environment="HTTPS_PROXY=https://proxy.example.com:443"
- ```
-
- Multiple environment variables can be set; to set both a non-HTTPS and
- a HTTPs proxy;
+ ```systemd
+ [Service]
+ Environment="HTTPS_PROXY=https://proxy.example.com:443"
+ ```
- ```systemd
- [Service]
- Environment="HTTP_PROXY=http://proxy.example.com:80"
- Environment="HTTPS_PROXY=https://proxy.example.com:443"
- ```
-
- > **Note**
- >
- > Special characters in the proxy value, such as `#?!()[]{}`, must be double
- > escaped using `%%`. For example:
- >
- > ```
- > [Service]
- > Environment="HTTP_PROXY=http://domain%%5Cuser:complex%%23pass@proxy.example.com:8080/"
- > ```
-
-3. If you have internal Docker registries that you need to contact without
- proxying, you can specify them via the `NO_PROXY` environment variable.
+ Multiple environment variables can be set; to set both a non-HTTPS and a
+ HTTPs proxy;
- The `NO_PROXY` variable specifies a string that contains comma-separated
- values for hosts that should be excluded from proxying. These are the
- options you can specify to exclude hosts:
- * IP address prefix (`1.2.3.4`)
- * Domain name, or a special DNS label (`*`)
- * A domain name matches that name and all subdomains. A domain name with
- a leading "." matches subdomains only. For example, given the domains
- `foo.example.com` and `example.com`:
- * `example.com` matches `example.com` and `foo.example.com`, and
- * `.example.com` matches only `foo.example.com`
- * A single asterisk (`*`) indicates that no proxying should be done
- * Literal port numbers are accepted by IP address prefixes (`1.2.3.4:80`)
- and domain names (`foo.example.com:80`)
-
- Config example:
+ ```systemd
+ [Service]
+ Environment="HTTP_PROXY=http://proxy.example.com:80"
+ Environment="HTTPS_PROXY=https://proxy.example.com:443"
+ ```
- ```systemd
- [Service]
- Environment="HTTP_PROXY=http://proxy.example.com:80"
- Environment="HTTPS_PROXY=https://proxy.example.com:443"
- Environment="NO_PROXY=localhost,127.0.0.1,docker-registry.example.com,.corp"
- ```
+ > **Note**
+ >
+ > Special characters in the proxy value, such as `#?!()[]{}`, must be double
+ > escaped using `%%`. For example:
+ >
+ > ```
+ > [Service]
+ > Environment="HTTP_PROXY=http://domain%%5Cuser:complex%%23pass@proxy.example.com:8080/"
+ > ```
-4. Flush changes and restart Docker
+3. If you have internal Docker registries that you need to contact without
+ proxying, you can specify them via the `NO_PROXY` environment variable.
- ```console
- $ systemctl --user daemon-reload
- $ systemctl --user restart docker
- ```
+ The `NO_PROXY` variable specifies a string that contains comma-separated
+ values for hosts that should be excluded from proxying. These are the options
+ you can specify to exclude hosts:
-5. Verify that the configuration has been loaded and matches the changes you
- made, for example:
+ - IP address prefix (`1.2.3.4`)
+ - Domain name, or a special DNS label (`*`)
+ - A domain name matches that name and all subdomains. A domain name with a
+ leading "." matches subdomains only. For example, given the domains
+ `foo.example.com` and `example.com`:
+ - `example.com` matches `example.com` and `foo.example.com`, and
+ - `.example.com` matches only `foo.example.com`
+ - A single asterisk (`*`) indicates that no proxying should be done
+ - Literal port numbers are accepted by IP address prefixes (`1.2.3.4:80`) and
+ domain names (`foo.example.com:80`)
- ```console
- $ systemctl --user show --property=Environment docker
+ Config example:
- Environment=HTTP_PROXY=http://proxy.example.com:80 HTTPS_PROXY=https://proxy.example.com:443 NO_PROXY=localhost,127.0.0.1,docker-registry.example.com,.corp
- ```
+ ```systemd
+ [Service]
+ Environment="HTTP_PROXY=http://proxy.example.com:80"
+ Environment="HTTPS_PROXY=https://proxy.example.com:443"
+ Environment="NO_PROXY=localhost,127.0.0.1,docker-registry.example.com,.corp"
+ ```
+
+4. Flush changes and restart Docker
+
+ ```console
+ $ systemctl --user daemon-reload
+ $ systemctl --user restart docker
+ ```
+
+5. Verify that the configuration has been loaded and matches the changes you
+ made, for example:
+
+ ```console
+ $ systemctl --user show --property=Environment docker
+
+ Environment=HTTP_PROXY=http://proxy.example.com:80 HTTPS_PROXY=https://proxy.example.com:443 NO_PROXY=localhost,127.0.0.1,docker-registry.example.com,.corp
+ ```
+
+
## Licensing
-Docker is licensed under the Apache License, Version 2.0. See
-[LICENSE](https://github.com/moby/moby/blob/master/LICENSE) for the full
-license text.
+The Docker Engine is licensed under the Apache License, Version 2.0. See
+[LICENSE](https://github.com/moby/moby/blob/master/LICENSE) for the full license
+text.
+
diff --git a/engine/install/centos.md b/engine/install/centos.md
index cb54951400..d644327ab1 100644
--- a/engine/install/centos.md
+++ b/engine/install/centos.md
@@ -1,5 +1,5 @@
---
-description: Instructions for installing Docker Engine on CentOS
+description: Install Docker Engine on CentOS
keywords: requirements, apt, installation, centos, rpm, install, uninstall, upgrade, update
redirect_from:
- /ee/docker-ee/centos/
diff --git a/engine/install/linux-postinstall.md b/engine/install/linux-postinstall.md
index 46395ad244..8b3361a3c7 100644
--- a/engine/install/linux-postinstall.md
+++ b/engine/install/linux-postinstall.md
@@ -3,7 +3,7 @@ description: Optional post-installation steps for Linux
keywords: >
Docker, Docker documentation, requirements, apt, installation, ubuntu,
install, uninstall, upgrade, update
-title: Post-installation steps for Linux
+title: Docker Engine post-installation steps
redirect_from:
- /engine/installation/linux/docker-ee/linux-postinstall/
- /engine/installation/linux/linux-postinstall/
@@ -136,95 +136,6 @@ options:
that performs log rotation by default
- Use a logging driver that sends logs to a remote logging aggregator.
-## Configure where the Docker daemon listens for connections
-
-By default, the Docker daemon listens for connections on a Unix socket to accept
-requests from local clients. It's possible to allow Docker to accept requests
-from remote hosts by configuring it to listen on an IP address and port as well
-as the Unix socket. For more detailed information on this configuration option,
-refer to the
-[dockerd CLI reference](/engine/reference/commandline/dockerd/#bind-docker-to-another-hostport-or-a-unix-socket).
-
-
-> Secure your connection
->
-> Before configuring Docker to accept connections from remote hosts it's
-> critically important that you understand the security implications of opening
-> Docker to the network. If steps aren't taken to secure the connection, it's
-> possible for remote non-root users to gain root access on the host. For more
-> information on how to use TLS certificates to secure this connection, check
-> [Protect the Docker daemon socket](../security/protect-access.md).
-{: .warning}
-
-You can configure Docker to accept remote connections. This can be done using
-the `docker.service` systemd unit file for Linux distributions using systemd. Or
-you can use the `daemon.json` file, if your distribution doesn't use systemd.
-
-> systemd vs `daemon.json`
->
-> Configuring Docker to listen for connections using both the systemd unit file
-> and the `daemon.json` file causes a conflict that prevents Docker from
-> starting.
-
-### Configuring remote access with systemd unit file
-
-1. Use the command `sudo systemctl edit docker.service` to open an override file
- for `docker.service` in a text editor.
-
-2. Add or modify the following lines, substituting your own values.
-
- ```systemd
- [Service]
- ExecStart=
- ExecStart=/usr/bin/dockerd -H fd:// -H tcp://127.0.0.1:2375
- ```
-
-3. Save the file.
-
-4. Reload the `systemctl` configuration.
-
- ```console
- $ sudo systemctl daemon-reload
- ```
-
-5. Restart Docker.
-
- ```console
- $ sudo systemctl restart docker.service
- ```
-
-6. Verify that the change has gone through.
-
- ```console
- $ sudo netstat -lntp | grep dockerd
- tcp 0 0 127.0.0.1:2375 0.0.0.0:* LISTEN 3758/dockerd
- ```
-
-### Configuring remote access with `daemon.json`
-
-1. Set the `hosts` array in the `/etc/docker/daemon.json` to connect to the UNIX
- socket and an IP address, as follows:
-
- ```json
- {
- "hosts": ["unix:///var/run/docker.sock", "tcp://127.0.0.1:2375"]
- }
- ```
-
-2. Restart Docker.
-
-3. Verify that the change has gone through.
-
- ```console
- $ sudo netstat -lntp | grep dockerd
- tcp 0 0 127.0.0.1:2375 0.0.0.0:* LISTEN 3758/dockerd
- ```
-
-## Enable IPv6 on the Docker daemon
-
-To enable IPv6 on the Docker daemon, see
-[Enable IPv6 support](../../config/daemon/ipv6.md).
-
## Next steps
- Take a look at the [Get started](../../get-started/index.md) training modules
diff --git a/engine/install/troubleshoot.md b/engine/install/troubleshoot.md
index c1cfa1b8b3..502ed25b7a 100644
--- a/engine/install/troubleshoot.md
+++ b/engine/install/troubleshoot.md
@@ -1,5 +1,5 @@
---
-title: Troubleshoot Docker Engine
+title: Troubleshoot Docker Engine installation
description:
Diagnose and resolve error messages related to the Docker Engine installation
keywords: Docker Engine, troubleshooting, error, Linux
diff --git a/storage/bind-mounts.md b/storage/bind-mounts.md
index 334010d705..87cdce190a 100644
--- a/storage/bind-mounts.md
+++ b/storage/bind-mounts.md
@@ -1,6 +1,6 @@
---
description: Using bind mounts
-title: Use bind mounts
+title: Bind mounts
keywords: storage, persistence, data persistence, mounts, bind mounts
redirect_from:
- /engine/admin/volumes/bind-mounts/
diff --git a/storage/tmpfs.md b/storage/tmpfs.md
index 545dd5a2ad..ed3640e420 100644
--- a/storage/tmpfs.md
+++ b/storage/tmpfs.md
@@ -1,6 +1,6 @@
---
description: Using tmpfs mounts
-title: Use tmpfs mounts
+title: tmpfs mounts
keywords: storage, persistence, data persistence, tmpfs
redirect_from:
- /engine/admin/volumes/tmpfs/
diff --git a/storage/volumes.md b/storage/volumes.md
index f765adc9ce..df64b6d47d 100644
--- a/storage/volumes.md
+++ b/storage/volumes.md
@@ -1,6 +1,6 @@
---
description: Using volumes
-title: Use volumes
+title: Volumes
keywords: storage, persistence, data persistence, volumes
redirect_from:
- /userguide/dockervolumes/
+
+
+
+
+
+
+
+ 
+
+
+ Install Docker Engine
+Learn how to install the open source Docker Engine for your distribution.
+
+
+
+ 
+
+
+ 
+
+
+
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+
+
+ 
+
+
+ 
+
+
+ 