[acdha]

Does this actually work for you? I tried it and networking was broken out of the box – it couldn’t even pull a container image. I didn’t have time to spend digging into it, however, and would not rule out that being an artifact of our VPN.

[mroche]

Networking is working just fine over here; I rebuilt the machine to be using the latest (Sept 4) FCOS stream, but it was fine on the previous version (Aug 21) as well.

Are you using short names to pull your images, i.e. 'requarks/wiki:latest' rather than the full path 'docker.io/requarks/wiki:latest'? (Note: official images in Docker Hub are under the 'library/' namespace, e.g. 'library/fedora')

Other networking issues, like the port publishing through the host bridging by default without needing to pass '--network' I believe are slated for the upcoming 3.3.2 patch release.

[studmuffin650]

One issue still apparently is that it can’t mount volumes. Though I haven’t had to do that yet. When you attempt to mount a volume it will attempt to do it from within the virtual machine not your machine.

[drzaiusx11]

The issue to watch is here: https://github.com/containers/podman/issues/8016

To be clear volumes are supported, what aren't are "bind mounts" which are not recommended over named volumes: https://docs.docker.com/storage/volumes/ https://docs.docker.com/storage/bind-mounts/

[mroche]

This is a known issue and is in the process of being figure out how to proceed: https://github.com/containers/podman/issues/8016

[acdha]

Good to know - I’ll give it another run when I have more time later this week.

[pilif]

If this is using the macOS native virtualization, then, yes, networking will be broken while a vpn is active.

This is a known issue that also was present in the Docker for Apple Silicon public preview where they eventually fixed it by dropping built-in virtualization for qemu