I am running the gitea runner directly (so, not through a container). The tasks are running on container, and many of these tasks are to build podman containers or to run them using podman-compose. The problem I am facing is: For podman to be able to assess the health of the containers, it needs systemd running. I have thought in extending my container image to execute CMD [ "/sbin/init" ], but this would be overwritten by the commands issued when the container gets created (I see in the create stage the entrypoint and the cmd are fixed, one of them to a sleep).
How can this be worked out?
I am running the gitea runner directly (so, not through a container). The tasks are running on container, and many of these tasks are to build podman containers or to run them using podman-compose. The problem I am facing is: For podman to be able to assess the health of the containers, it needs systemd running. I have thought in extending my container image to execute ```CMD [ "/sbin/init" ]```, but this would be overwritten by the commands issued when the container gets created (I see in the create stage the entrypoint and the cmd are fixed, one of them to a sleep).
How can this be worked out?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I am running the gitea runner directly (so, not through a container). The tasks are running on container, and many of these tasks are to build podman containers or to run them using podman-compose. The problem I am facing is: For podman to be able to assess the health of the containers, it needs systemd running. I have thought in extending my container image to execute
CMD [ "/sbin/init" ], but this would be overwritten by the commands issued when the container gets created (I see in the create stage the entrypoint and the cmd are fixed, one of them to a sleep).How can this be worked out?