I can confirm that:
* The issue is present in Debian 11 (podman3.0.1+dfsg1-3+b2), I ran
into it with fedora:latest.
* And the issue is fixed in Debian Testing (podman 3.4.1+ds1-2).
However Debian Testing's podman is not practical to install on Debian 11
(requires a newer libc), so it would
Yes, after installing podman_3.0.1+dfsg1-4_amd64.deb and
golang-github-containers-common_0.33.4+ds1-2_all.deb from that page, the
Fedora 35 examples work as expected.
– Will
On Sat, 9 Oct 2021 at 23:14, Reinhard Tartler wrote:
> Control: fixed -1 3.3.1+ds2-1
> Control: tags -1 bullseye
>
>
Control: fixed -1 3.3.1+ds2-1
Control: tags -1 bullseye
Thank you for your bugreport.
On Tue, Oct 5, 2021 at 10:51 AM Will Thompson wrote:
> Package: podman
> Version: 3.0.1+dfsg1-3+b2
> Severity: important
>
> podman embeds a default seccomp policy, which based on my research is
> identical
Package: podman
Version: 3.0.1+dfsg1-3+b2
Severity: important
podman embeds a default seccomp policy, which based on my research is
identical to that used by docker. The policy embedded in the bullseye
version of podman is buggy when used to run a container whose glibc is
2.33.9000 or newer, due
4 matches
Mail list logo
