-
### Issue Description
https://github.com/containers/podman/issues/17391 is still a valid problem.
```sh
podman pull --tls-verify=false registry.redhat.io/redhat/community-operator-index:v4.14
…
-
### Issue Description
Running with RHEL 8.8 and Podman 4.4.1 using CNI network backend with dnsname installed. When containers that share the same network attempt to communicate with each other by na…
-
I personally prefer using https://podman.io instead of Docker (because containers dont' run as root, on the host; although you can still be root inside the container..), and when I tried that with thi…
-
### Issue Description
After rebooting a server a rootless container is spawned by systemd service and failed with information: IP address is already allocated.
### Steps to reproduce the issue
Step…
-
Would it be possible for Flatpak to offer more options for the `--share=network` permission?
For cases where you want to offer access to the local network without allowing external connections. I u…
ghost updated
7 months ago
-
### Issue Description
I'm trying to launch a custom script with the Nextcloud linuxserver.io container to install the dlib, pdlib and bzip2 APKs at launch to support the Face Recognition application,…
-
### Issue Description
Create a podman machine with a volume mount and it's there. Then install qemu-user-static for cross-compilation, and the volume mount is gone.
### Steps to reproduce the issue
…
kgibm updated
7 months ago
-
### Issue Description
The maximum number of open files does not match between `podman run` and `podman build`
I am running "rootless", Podman 4.3.1.
On my System, I get max open files of 1M (…
-
### Issue Description
On MacOS (at least), volume mounts appear to be owned by `root` when running containers (such as [neo4j](https://hub.docker.com/_/neo4j/)) which run as a non-root user and attem…
-
### Issue Description
If an image exists in Podman that is no longer in use and the command "docker image prune -a" is executed via the Forward API and Docker CLI, the error message "Error response…