Closed i-raise-issues closed 12 months ago
podman-compose is not a part of the podman project.
If you can figure out the podman command podman-compose is generating we could look at it.
podman-compose is not a part of the podman project.
If you can figure out the podman command podman-compose is generating we could look at it.
Thanks for the reply @rhatdan. I've translated the issue into podman
only commands and updated the entire Issue.
@Luap99 PTAL
you need to have a read write /proc mount, see https://github.com/containers/podman/issues/19991 and https://github.com/containers/netavark/issues/825
Issue Description
Running Podman in a network fails:
podman run --rm -d --network=my network -p 80:80 -v /sys:/sys --name web nginx:latest
. However other podman commands work fine most of the time (build, run etc). Network created viapodman network create mynetwork
Steps to reproduce the issue
Steps to reproduce the issue
podman network create mynetwork
podman --log-level=debug run --rm -d --network=mynetwork -p 8080:80 -v /sys:/sys --name web nginx:latest
Describe the results you received
Describe the results you received
Describe the results you expected
The nginx container to come up successfully.
podman info output
Podman in a container
Yes
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Linux container running in Kubernetes (Amazon EKS), with Podman 4.6.1 installed Home Directory mounted via NFS Share
/home/my-user
rootless_storage_path mounted under$HOME/.local/share/containers/storage
with an Amazon EBS backed Kubernetes PVCAdditional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting