What were you trying to do that didn't work?

- When defining variables in container.conf [engine]table the variables are passed on to the container

What is the impact of this issue to you?

• Setting a proxy server in in the container.conf [engine]table also sets it within the container
• Web Services that should only communicate within a podman network will try to connect through the outside proxy

Please provide the package NVR for which the bug is seen:

podman-5.4.0-13.el10_0.x86_64

How reproducible is this bug?:

Everytime

Steps to reproduce

1. Add [engine]section to /etc/containers/containers.conf
2. Add 

   env = ["http_proxy=http://blahblub:3128", "https_proxy=https://blahblub:3128"]

   to the file

3. Start a container 

   podman run -rm -it --name ubi10 -d ubi10

1. Attach to the container and check for set variables

[root@test:/etc/containers]# podman attach ubi10
[root@2693629b8cf3 /]# env|grep proxy
https_proxy=https://blahblub:3128
http_proxy=http://blahblub:3128   

Expected results

The manual for the [engine] table states: 

env=[] 
Environment variables to be used when running the container engine (e.g., Podman, Buildah). For example "http_proxy=internal.proxy.company.com". Note these environment variables will not be used within the container. Set the env section under [containers] table, if you want to set environment variables for the container.

 

Actual results

Variables are passed on to the containers but shouldn't.