You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the name ends with .container, the container will reuse the network stack of another container created by $name.container. The generated systemd service contains a dependency on $name.service. Note: the corresponding .container file must exist.
However, if your [Container] Network= references a templated container (i.e. [email protected]), the service fails to generate at systemctl daemon-reload.
Issue Description
Manual says
However, if your [Container] Network= references a templated container (i.e. [email protected]), the service fails to generate at systemctl daemon-reload.
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
anothercontainer.service fails to generate
Describe the results you expected
anothercontainer.service should reference --network container:[name of [email protected]]
podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
No
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: