Your message dated Sat, 13 Aug 2022 10:23:37 +0200
with message-id
and subject line Re: Bug#1016195:
has caused the Debian Bug report #1016195,
regarding podman: fails to run any container
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1016195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: podman
Version: 3.0.1+dfsg1-3+deb11u1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: vincent.olivert.ri...@gmail.com
Dear Maintainer,
I'm strictly running Debian stable with no packages from testing or
unstable.
When trying to run any container with podman I see the following error:
$ podman run --rm -it debian:bullseye-slim bash
Error: OCI runtime error: container_linux.go:367: starting container process
caused: process_linux.go:340: applying cgroup configuration for process caused:
error while starting unit
"libpod-410aba7b65566d9ddf2f0d2f188a22ed53577b90eea67e773c8294fa8bd252f3.scope"
with properties [{Name:Description Value:"libcontainer container
410aba7b65566d9ddf2f0d2f188a22ed53577b90eea67e773c8294fa8bd252f3"} {Name:Slice
Value:"user.slice"} {Name:PIDs Value:@au [69240]} {Name:Delegate Value:true}
{Name:MemoryAccounting Value:true} {Name:CPUAccounting Value:true}
{Name:IOAccounting Value:true} {Name:DefaultDependencies Value:false}
{Name:DevicePolicy Value:"strict"} {Name:DeviceAllow Value:@a(ss) []}
{Name:DeviceAllow Value:["INVALID", "INVALID", "INVALID", "INVALID", "INVALID",
"INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID"]}
{Name:TasksAccounting Value:true} {Name:TasksMax Value:@t 2048}]: error
creating systemd unit
`libpod-410aba7b65566d9ddf2f0d2f188a22ed53577b90eea67e773c8294fa8bd252f3.scope`:
got `failed`
I tried replacing runc with crun, but the same problem persist, although
the error message is shorter:
$ podman run --rm -it debian:bullseye-slim bash
Error: OCI runtime error: error creating systemd unit
`libpod-df9c347e24f4ea213f8c81d6211f60e015e48b2f4b9118558f9fa95f8c7610fd.scope`:
got `failed`
Just in case it matters, my system is up to date and the version of
systemd I have installed is 247.3-7.
-- System Information:
Debian Release: 11.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Kernel: Linux 5.10.0-16-arm64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages podman depends on:
ii conmon 2.0.25+ds1-1.1
ii containernetworking-plugins 0.9.0-1+b6
ii golang-github-containers-common 0.33.4+ds1-1+deb11u1
ii init-system-helpers 1.60
ii iptables 1.8.7-1
ii libc62.31-13+deb11u3
ii libdevmapper1.02.1 2:1.02.175-2.1
ii libgpgme11 1.14.0-1+b2
ii libseccomp2 2.5.1-1+deb11u1
ii runc 1.0.0~rc93+ds1-5+deb11u2
Versions of packages podman recommends:
ii buildah 1.19.6+dfsg1-1+b6
ii fuse-overlayfs1.4.0-1
ii golang-github-containernetworking-plugin-dnsname 1.1.1+ds1-4+b7
ii slirp4netns 1.0.1-2
ii tini 0.19.0-1
ii uidmap1:4.8.1-1
Versions of packages podman suggests:
pn containers-storage
pn docker-compose
-- no debconf information
--- End Message ---
--- Begin Message ---
Thanks for reporting back. I was quite puzzled by your report and couldn't
reproduce it.
On Mon, Aug 8, 2022 at 3:09 AM V O wrote:
> I don't know why, but the problem seems to be fixed after a reboot and I'm
> no longer able to reproduce it.
>
> I guess this bug can be closed.
>
--
regards,
Reinhard
--- End Message ---
