Fedora 33 user here. Whenever I run a rootful container I can perform
df -t overlay
mount -t overlay
....in the host and I can clearly see where the root filesystem of the
container is actually mounted (the "merged" one).
Now, with the new native overlay filesystem support for rootless
containers, whenever I run a rootless one I don't see the same behavior
with the mount or df commands (either as regular user or the root user).
In fact, there's no overlay fs shown. I know it's there because I found
them somewhere hidden in /proc/*/mounts and I also performed the "podman
system reset" that Dan & Giuseppe mentioned in a recent blog post.
There's got to be some explanation like perhaps it's under another
"mount namespace" ...but then why do the overlay entries appear in the
host when rootful containers are running?
We've recently been going over old work items. One of them was to collect
code-coverage in CI.
I gave it a shot last year and opened a PR  but quickly ran into the
problem of uploading the thousands of coverage profiles during the
end-to-end tests (i.e., test/e2e/*). They accumulated to over a dozen
gigabytes. I tried trimming these down in various attempts but never
managed to tame the beast. Priorities shifted and I went on to work on
That being said. If some of you are coverage experts in Go and want to
give it a shot. Feel free to pick up the PR  and kick it over the
finish line. As you may see, the instrumented podman binary to collect
coverage has some issues related to signal handling that need to get ironed
out as well.
No time pressure, it's a nice-to-have.
I'm very late getting the agenda out, but I think we've a great
line up of topics for next Tuesday's Podman Community Meeting! We'll be
talking about updates on the Debian/Ubuntu package, DIY Networking in
rootless containers, Containerized DNS Analysis, Using Podman in an IDE,
and an open forum at the end.
The meeting starts at 11:00 a.m. EDT (UTC-4) on Tuesday September
7, 2021 and will be free to attend via BlueJeans
(https://bluejeans.com/880216278/2568). The full agenda is here:
For those in the US, enjoy your labor day holiday!
Sorry to bother you with this. I cannot reach a running container via network using podman machine.
I installed podman (3.3.0) via homebrew on macos (bigsur 11.5.2).
I created a machine using
> podman machine init
which I then started using
> podman machine start
I then started a nginx container
> podman run -p 8000:80 --rm docker://nginx
I’d expect to reach the container on localhost:8000 via curl
> curl localhost:8000
> curl: (7) Failed to connect to localhost port 8000: Connection refused
But the port forwarding is configured for the machine only
Inside the machine the port is forwarded:
> podman machine ssh
> curl localhost:8000
> <!DOCTYPE html>
If automatic port forwarding is not possible I’d expect to be able to reach the machine on it’s ip address. I don’t reach the machines ip (got it from it ip addr from inside the machine) either.
I didn’t find anything on this matter in the docs https://docs.podman.io/en/latest/ . What am I missing?
Thank you so much for your time!
(My first post here)
Newbie question... I'm playing out with rootless container based on:
If I run this image (without specifying ports or volumes) it will create
a volume automatically. I did "inspect" the image and I see the volume
is defined there. I also noticed the ExposedPorts as well but podman
didn't create theses. Why would it create the volume but not expose the
ports (if they're available and above 1024)?