mirror of
https://github.com/docker/docs.git
synced 2026-10-29 20:39:05 +03:00
Desktop: update with latest HTTP proxy info (#16269)
* Desktop: we now try to configure HTTP proxies consistently It's not 100% yet but it's not necessary to configure every component separately as it was before. Signed-off-by: David Scott <dave.scott@docker.com> * Desktop: update HTTP proxy section In the latest 4.15 it should - work with Proxy Auto-Configuration - dynamically ask the developer for username and password, if the proxy requires auth - support TLS 1.3 for talking to the proxy - be controllable with settings management Signed-off-by: David Scott <dave.scott@docker.com> * Update desktop/settings/windows.md * Update desktop/settings/linux.md * Update desktop/settings/mac.md * Update desktop/settings/mac.md * Update desktop/settings/linux.md * Update desktop/settings/windows.md Signed-off-by: David Scott <dave.scott@docker.com> Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>
This commit is contained in:
David Scott
GitHub
@@ -99,23 +99,15 @@ File share settings are:
|
||||
### Proxies
|
||||
|
||||
To configure HTTP proxies, switch on the **Manual proxy configuration** setting.
|
||||
This setting is used for logging into Docker, for pulling and pushing images, and for
|
||||
container Internet access. If the proxy requires authorization then Docker Desktop dynamically asks
|
||||
the developer for a username and password. All passwords are stored securely in the OS credential store.
|
||||
Note that only the `Basic` proxy authentication method is supported so we recommend using an `https://`
|
||||
URL for your HTTP/HTTPS proxies to protect passwords while in transit on the network. Docker Desktop
|
||||
supports TLS 1.3 when communicating with proxies.
|
||||
|
||||
Your proxy settings, however, are not propagated into the containers you start.
|
||||
If you wish to set the proxy settings for your containers, you need to define
|
||||
environment variables for them, just like you would do on Linux, for example:
|
||||
|
||||
```console
|
||||
$ docker run -e HTTP_PROXY=http://proxy.example.com:3128 alpine env
|
||||
|
||||
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
|
||||
HOSTNAME=b7edf988b2b5
|
||||
TERM=xterm
|
||||
HOME=/root
|
||||
HTTP_PROXY=http://proxy.example.com:3128
|
||||
```
|
||||
|
||||
For more information on configuring the Docker CLI to automatically set proxy variables for both `docker run` and `docker build`
|
||||
see [Configure the Docker client](../../network/proxy.md#configure-the-docker-client).
|
||||
To prevent developers from accidentally changing the proxy settings, see
|
||||
[Settings Management](../hardened-desktop/settings-management/index.md#what-features-can-i-configure-with-settings-management).
|
||||
|
||||
### Network
|
||||
|
||||
|
||||
@@ -134,18 +134,20 @@ HTTP/HTTPS proxies can be used when:
|
||||
- Containers interact with the external network
|
||||
- Scanning images
|
||||
|
||||
Each use case above is configured slightly differently.
|
||||
If the host uses a HTTP/HTTPS proxy configuration (static or via Proxy Auto-Configuration), Docker Desktop reads
|
||||
this configuration
|
||||
and automatically uses these settings for logging into Docker, for pulling and pushing images, and for
|
||||
container Internet access. If the proxy requires authorization then Docker Desktop dynamically asks
|
||||
the developer for a username and password. All passwords are stored securely in the OS credential store.
|
||||
Note that only the `Basic` proxy authentication method is supported so we recommend using an `https://`
|
||||
URL for your HTTP/HTTPS proxies to protect passwords while in transit on the network. Docker Desktop
|
||||
supports TLS 1.3 when communicating with proxies.
|
||||
|
||||
If the host uses a static HTTP/HTTPS proxy configuration, Docker Desktop reads this configuration
|
||||
and automatically uses these settings for logging into Docker and for pulling and pushing images.
|
||||
To set a different proxy for Docker Desktop, enable **Manual proxy configuration** and enter a single
|
||||
upstream proxy URL of the form `http://proxy:port` or `https://proxy:port`.
|
||||
|
||||
If the host uses a more sophisticated HTTP/HTTPS configuration, enable **Manual proxy configuration** and enter a single upstream proxy URL
|
||||
of the form `http://username:password@proxy:port`.
|
||||
|
||||
HTTP/HTTPS traffic from image builds and running containers is forwarded transparently to the same
|
||||
upstream proxy used for logging in and image pulls.
|
||||
If you want to override this behaviour and use different HTTP/HTTPS proxies for image builds and
|
||||
running containers, see [Configure the Docker client](../../network/proxy.md#configure-the-docker-client).
|
||||
To prevent developers from accidentally changing the proxy settings, see
|
||||
[Settings Management](../hardened-desktop/settings-management/index.md#what-features-can-i-configure-with-settings-management).
|
||||
|
||||
The HTTPS proxy settings used for scanning images are set using the `HTTPS_PROXY` environment variable.
|
||||
|
||||
|
||||
@@ -158,16 +158,20 @@ HTTP/HTTPS proxies can be used when:
|
||||
- Containers interact with the external network
|
||||
- Scanning images
|
||||
|
||||
Each use case above is configured slightly differently.
|
||||
If the host uses a HTTP/HTTPS proxy configuration (static or via Proxy Auto-Configuration), Docker Desktop reads
|
||||
this configuration
|
||||
and automatically uses these settings for logging into Docker, for pulling and pushing images, and for
|
||||
container Internet access. If the proxy requires authorization then Docker Desktop dynamically asks
|
||||
the developer for a username and password. All passwords are stored securely in the OS credential store.
|
||||
Note that only the `Basic` proxy authentication method is supported so we recommend using an `https://`
|
||||
URL for your HTTP/HTTPS proxies to protect passwords while in transit on the network. Docker Desktop
|
||||
supports TLS 1.3 when communicating with proxies.
|
||||
|
||||
If the host uses a static HTTP/HTTPS proxy configuration, Docker Desktop reads this configuration
|
||||
and automatically uses these settings for logging into Docker and for pulling and pushing images.
|
||||
To set a different proxy for Docker Desktop, enable **Manual proxy configuration** and enter a single
|
||||
upstream proxy URL of the form `http://proxy:port` or `https://proxy:port`.
|
||||
|
||||
If the host uses a more sophisticated HTTP/HTTPS configuration, enable **Manual proxy configuration** and enter a single upstream proxy URL
|
||||
of the form `http://username:password@proxy:port`.
|
||||
|
||||
The HTTP/HTTPS proxy settings used for fetching artifacts during builds and for running containers
|
||||
are set via the `.docker/config.json` file, see [Configure the Docker client](../../network/proxy.md#configure-the-docker-client).
|
||||
To prevent developers from accidentally changing the proxy settings, see
|
||||
[Settings Management](../hardened-desktop/settings-management/index.md#what-features-can-i-configure-with-settings-management).
|
||||
|
||||
The HTTPS proxy settings used for scanning images are set using the `HTTPS_PROXY` environment variable.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user