Replies: 2 comments 1 reply
-
You have two layers of issues:
Combing the two you
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Or the alternative if the env var does not need to be in the container at all you can set it under the systemd service section.
With that systemd should replace the var before passing that to podman. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Issue Description
With Quadlet, environment variables introduced via
EnvironmentFile=
are available inside the container, but it doesn't seem like they can be used to supply command line arguments to the container's command viaExec=
.Maybe this is expected behavior and I'm just missing something about how this is supposed to work?
Steps to reproduce the issue
Describe the results you received
In the log output, there is a helpful warning:
And the output of the
Exec=
command itself:Describe the results you expected
I would have expected
${FOO}
to be available at theExec=
command line as well, the way regular systemd service files behave AFAIK.podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
No response
Additional information
No response
Beta Was this translation helpful? Give feedback.
All reactions