mirror of
https://github.com/containers/podman.git
synced 2025-05-23 10:07:33 +08:00
2dde30b93a
The remote client should be allowed to specify if the container should be run with the proxy env vars. It will still use the proxy vars from the server process and not the client. This makes podman-remote more consistent with the local version and easier to use in environments where a proxy is required. Fixes #16520 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
21 lines
1.0 KiB
Markdown
21 lines
1.0 KiB
Markdown
####> This option file is used in:
|
|
####> podman build, create, run
|
|
####> If file is edited, make sure the changes
|
|
####> are applicable to all of those.
|
|
#### **--http-proxy**
|
|
|
|
By default proxy environment variables are passed into the container if set
|
|
for the Podman process. This can be disabled by setting the value to **false**.
|
|
The environment variables passed in include **http_proxy**,
|
|
**https_proxy**, **ftp_proxy**, **no_proxy**, and also the upper case versions of
|
|
those. This option is only needed when the host system must use a proxy but
|
|
the container should not use any proxy. Proxy environment variables specified
|
|
for the container in any other way will override the values that would have
|
|
been passed through from the host. (Other ways to specify the proxy for the
|
|
container include passing the values with the **--env** flag, or hard coding the
|
|
proxy environment at container build time.)
|
|
When used with the remote client it will use the proxy environment variables
|
|
that are set on the server process.
|
|
|
|
Defaults to **true**.
|