summaryrefslogtreecommitdiff
path: root/docs/source/markdown/podman-volume-export.1.md
diff options
context:
space:
mode:
authoresendjer <esendjer@gmail.com>2022-02-11 02:58:53 +0500
committeresendjer <esendjer@gmail.com>2022-02-12 21:24:15 +0500
commita8928a3caa432c9523070f790eb15b733ab44753 (patch)
tree53f1eba5226d2aa9b0455201ad99b799fb7f7bd3 /docs/source/markdown/podman-volume-export.1.md
parent12836a5610ea6d4f6844d4fbdc222b439ccbc746 (diff)
downloadpodman-a8928a3caa432c9523070f790eb15b733ab44753.tar.gz
podman-a8928a3caa432c9523070f790eb15b733ab44753.tar.bz2
podman-a8928a3caa432c9523070f790eb15b733ab44753.zip
ignition: propagate proxy settings from a host into a vm
Set proxy settings (such as `HTTP_PROXY`, and others) for the whole guest OS with setting up `DefaultEnvironment` with a `systemd` configuration file `default-env.conf`, a `profile.d` scenario file - `default-env.sh` and a `environment.d` configuration file `default-env.conf` The **actual** environment variables are read by podman at a start, then they are encrypted with base64 into a single string and after are provided into a VM through QEMU Firmware Configuration (fw_cfg) Device Inside a VM a systemd service `envset-fwcfg.service` reads the providead encrypted string from fw_cfg, decrypts and then adds to the files - `/etc/systemd/system.conf.d/default-env.conf` - `/etc/profile.d/default-env.sh` - `/etc/environment.d/default-env.conf` At the end this service execute `systemctl daemon-reload` to propagate new variables for systemd manager [NO NEW TESTS NEEDED] Closes #13168 Signed-off-by: esendjer <esendjer@gmail.com>
Diffstat (limited to 'docs/source/markdown/podman-volume-export.1.md')
0 files changed, 0 insertions, 0 deletions