You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
podman build has a --cgroup-manager. Add the same flag to podman run.
Suggest potential solution
Change the code to add the flag to podman run.
Have you considered any alternatives?
My current workaround is to modify the containers.conf with sed -i 's/\[engine\]/\[engine\]\ncgroup_manager = "cgroupfs"/' /usr/share/containers/containers.conf
While this works, its harder than just passing the option, which is also more explicit.
Additional context
Context is a Jenkins build agent which is itself a pod (running container) It does a docker-in-docker build, followed by a podman run. `
podman run -it ACCOUNT.dkr.ecr.us-east-2.amazonaws.com/POD:qa_1_0-1c1b272-89
time="2024-09-06T21:32:39-04:00"
level=warning msg="Failed to add conmon to systemd sandbox cgroup:
dial unix /run/systemd/private: connect: no such file or directory"
The text was updated successfully, but these errors were encountered:
Feature request description
podman build has a --cgroup-manager. Add the same flag to podman run.
Suggest potential solution
Change the code to add the flag to podman run.
Have you considered any alternatives?
My current workaround is to modify the containers.conf with
sed -i 's/\[engine\]/\[engine\]\ncgroup_manager = "cgroupfs"/' /usr/share/containers/containers.conf
While this works, its harder than just passing the option, which is also more explicit.
Additional context
Context is a Jenkins build agent which is itself a pod (running container) It does a docker-in-docker build, followed by a podman run. `
The text was updated successfully, but these errors were encountered: