deploy: provide a systemd unit managing containers. #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When attempting to run in a podman namespace through a udev-triggered script, filesystem mounting does not work out-of-the-box. When configured with overlayfs, a permission denied occurs when remouting `containers/storage/overlay/` with flags 0x40000. Similar issues happen with vfs, and probably other filesystems. Launching the container under systemd does not provoke such not understood issues. Let's provide a systemd-unit to be started by udev when the IOC must be run. This is similar to the AFC EPICS IOC deploy, also making services management uniform. During stop, a timeout of zero is provided to use SIGKILL right away, since the SIGTERM signal does not reach the procServ process and its childs for a yet unknown reason.
|
This is going to happen as part of #14 , so closing now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When attempting to run in a podman namespace through a udev-triggered script, filesystem mounting does not work out-of-the-box. When configured with overlayfs, a permission denied occurs when remouting
containers/storage/overlay/with flags 0x40000. Similar issues happen with vfs, and probably other filesystems.Launching the container under systemd does not provoke such not understood issues. Let's provide a systemd-unit to be started by udev when the IOC must be run. This is similar to the AFC EPICS IOC deploy, also making services management uniform.
During stop, a timeout of zero is provided to use SIGKILL right away, since the SIGTERM signal does not reach the procServ process and its childs for a yet unknown reason.