-
Bug
-
Resolution: Done-Errata
-
Undefined
-
rhel-9.1.0
-
None
-
None
-
rhel-sst-container-tools
-
None
-
False
-
-
None
-
None
-
If docs needed, set a value
-
-
All
-
None
Description of problem:
When running `podman system service` Podman fails with the following error:
Error: mkdir /sys/fs/cgroup/init: read-only file system
Version-Release number of selected component (if applicable):
ubi9/podman:9.1.0-5@sha256:3a9d42016fdd273fb37d053644792aba1268638dd2a066d186c91fa8a357e365
podman-4.2.0-7.el9_1.x86_64
How reproducible:
Always
Steps to Reproduce:
1. podman run --rm registry.access.redhat.com/ubi9/podman:9.1.0-5@sha256:3a9d42016fdd273fb37d053644792aba1268638dd2a066d186c91fa8a357e365 podman system service
Actual results:
time="2023-04-11T05:17:01Z" level=warning msg="\"/\" is not a shared mount, this could cause issues or missing mounts with rootless containers"
time="2023-04-11T05:17:01Z" level=warning msg="Using rootless single mapping into the namespace. This might break some images. Check /etc/subuid and /etc/subgid for adding sub*ids if not using a network user"
Error: mkdir /sys/fs/cgroup/init: read-only file system
Expected results:
Podman should start as a service and listen for incoming connections
Additional info:
This has been fixed upstream and released in 4.3.0
- external trackers
- links to
-
RHSA-2023:116097 podman security and bug fix update