4 ms·

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) a

by mroche 5y ago

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.

acdha 5y ago
Good to know - I’ll give it another run when I have more time later this week.
studmuffin650 5y ago
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.
- mroche 5y ago
  This is a known issue and is in the process of being figure out how to proceed: https://github.com/containers/podman/issues/8016 https://github.com/containers/podman/issues/8016
- drzaiusx11 5y ago
  The issue to watch is here: https://github.com/containers/podman/issues/8016 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/volumes/ https://docs.docker.com/storage/bind-mounts/ https://docs.docker.com/storage/bind-mounts/