update docker cpi cloud_provider section to start containers with systemd#496
Draft
update docker cpi cloud_provider section to start containers with systemd#496
Conversation
* set systemd config on cloudconfig section
cf-foundation-community-automation
bot
moved this to Inbox
in Foundational Infrastructure Working Group
KauzClay
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I noticed with the docker CPI image at least, we only set start_containers_with_systemd on the bosh instance group, but not in the cloud provider section like we do for warden in the bosh-lite.yml opsfile.
Perhaps this is part of the many CI issues we have with these CPI images and noble?