-
### Issue Description
When running podman machine init with HyperV on my French Windows, I have this:
```
Downloading VM image: fedora-coreos-38.20231027.2.0-hyperv.x86_64.vhdx.zip: done
Extract…
-
### Issue Description
I noticed that when I am using a podman endpoint (through `--url`), then I execute
a command against a running container, `podman --url exec ...` two conmon
processes are lef…
-
### Issue Description
Multi-arch images created by podman and signed by cosign can not be pulled and the signature verified by podman, but they are reported valid by `cosign verify`.
Pushing and…
-
### Issue Description
`idmap` option on Quadlet `Mount` option is handled incorrectly, resulting in an invalid `podman run` call in the generated `ExecStart`: The arguments to `idmap` are truncated…
-
### Issue Description
I'm trying to use distrobox on a fresh OpenSuse MicroOS install (with a reused home partition) and I am trying to run a container. I've seen issues on distrobox which led me t…
-
### Discussed in https://github.com/containers/podman/discussions/19519
Originally posted by **telometto** August 4, 2023
I've been having major issues trying to run AdGuard Home on my home s…
-
### Issue Description
After my fedora coreos device updated itself yesterday from `38.20231027.3.2` to `39.20231101.3.0`, one of my containers failed to start. It is a rootless container with a rea…
-
### Issue Description
On MacOS M1, creating a QEMU machine with `podman machine init ` will fail if user generated key `~/.ssh/` already exists.
Although the default name is fairly specific (`podm…
-
### Issue Description
In Podman 4.6.1 and Podman 4.7.0 it will not pass the DNS resolvers options specified on the network to the container when the DNS plugin is enabled using bridge network. Howe…
-
### Issue Description
I had symlinked `~/.config/containers/systemd/` to the directory `~/containers/quadlet` which worked fine in podman version v4.6.2 and before. My setup broke with podman v4.7.…