-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
generate systemd: add network dependency #4130
Comments
This issue had no activity for 30 days. In the absence of activity or the "do-not-close" label, the issue will be automatically closed within 7 days. |
@vrothberg @baude We may want to exclude anything with a |
@mheon, I think the bot only supports one exempt label. I think it doesn't hurt to be reminded of inactivity - adding the "do-not-close" label will prevent it from being closed in the future. |
@vrothberg Did you ever get around to this? Shouldn't this be a simple fix? |
Didn't do it yet. I planned to tackle it when working on a bigger item for systemd generation. |
Add network dependencies to generated systemd services to allow for enabling them at system startup and have a working network if needed. Fixes: containers#4130 Signed-off-by: Valentin Rothberg <[email protected]>
Add network dependencies to generated systemd services to allow for enabling them at system startup and have a working network if needed. Fixes: containers#4130 Signed-off-by: Valentin Rothberg <[email protected]>
To support enabling services at system startup, the generated services need to add networking dependencies, namely:
Can be tested with enabling a generated service and testing the network connection of the container after reboot. Should also make sure that exposed ports are reachable.
The text was updated successfully, but these errors were encountered: