podman: f37 rootless: pod create: creating cgroup, already exists

on f37:

$ podman pod create
Error: unable to create pod cgroup for pod SHA:
    creating cgroup user.slice/user-libpod_pod_SHA.slice: 
   Unit user-libpod_pod_SHA.slice already exists.

Infinitely repeatable, each time with a different SHA.

podman-4.3.0~rc1-3.fc37.x86_64 on 5.19.12-300.fc37.x86_64

also built from sources, main @ bb0b1849d7102c2f9212ebaaeb332519a92c5d3c

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 31 (14 by maintainers)

Commits related to this issue

Cirrus: Workaround #16107 Signed-off-by: Chris Evich <cevich@redhat.com> — committed to cevich/podman by cevich 2 years ago
manager: allow transient units to have drop-ins In https://github.com/containers/podman/issues/16107, starting of a transient slice unit fails because there's a "global" drop-in /usr/lib/systemd/user... — committed to keszybz/systemd by keszybz 2 years ago
manager: allow transient units to have drop-ins In https://github.com/containers/podman/issues/16107, starting of a transient slice unit fails because there's a "global" drop-in /usr/lib/systemd/user... — committed to keszybz/systemd by keszybz 2 years ago
manager: allow transient units to have drop-ins In https://github.com/containers/podman/issues/16107, starting of a transient slice unit fails because there's a "global" drop-in /usr/lib/systemd/user... — committed to keszybz/systemd by keszybz 2 years ago
manager: allow transient units to have drop-ins In https://github.com/containers/podman/issues/16107, starting of a transient slice unit fails because there's a "global" drop-in /usr/lib/systemd/user... — committed to systemd/systemd-stable by keszybz 2 years ago
manager: allow transient units to have drop-ins In https://github.com/containers/podman/issues/16107, starting of a transient slice unit fails because there's a "global" drop-in /usr/lib/systemd/user... — committed to systemd/systemd-stable by keszybz 2 years ago
manager: allow transient units to have drop-ins In https://github.com/containers/podman/issues/16107, starting of a transient slice unit fails because there's a "global" drop-in /usr/lib/systemd/user... — committed to lnykryn/rhel-8 by keszybz 2 years ago
manager: allow transient units to have drop-ins In https://github.com/containers/podman/issues/16107, starting of a transient slice unit fails because there's a "global" drop-in /usr/lib/systemd/user... — committed to dtardon/systemd-rhel8 by keszybz 2 years ago
manager: allow transient units to have drop-ins In https://github.com/containers/podman/issues/16107, starting of a transient slice unit fails because there's a "global" drop-in /usr/lib/systemd/user... — committed to dtardon/systemd-rhel8 by keszybz 2 years ago
manager: allow transient units to have drop-ins In https://github.com/containers/podman/issues/16107, starting of a transient slice unit fails because there's a "global" drop-in /usr/lib/systemd/user... — committed to dtardon/systemd-rhel8 by keszybz 2 years ago
manager: allow transient units to have drop-ins In https://github.com/containers/podman/issues/16107, starting of a transient slice unit fails because there's a "global" drop-in /usr/lib/systemd/user... — committed to dtardon/systemd-rhel8 by keszybz 2 years ago
manager: allow transient units to have drop-ins In https://github.com/containers/podman/issues/16107, starting of a transient slice unit fails because there's a "global" drop-in /usr/lib/systemd/user... — committed to dtardon/systemd-rhel8 by keszybz 2 years ago
manager: allow transient units to have drop-ins In https://github.com/containers/podman/issues/16107, starting of a transient slice unit fails because there's a "global" drop-in /usr/lib/systemd/user... — committed to redhat-plumbers/systemd-rhel8 by keszybz 2 years ago

Most upvoted comments

The issue is new in podman 4.3. podman 4.2 works fine on f37. This is a regression. No matter whose fault it is, podman 4.3 cannot ship on f37 right now.

Ok, this makes me think it is a podman 4.3 inclusion. Unless a major change in systemd also shipped in that timeframe? I am going to investigate the cgroup creation path this afternoon to see if I can pinpoint it

cdoern on Oct 12, 2022