Cirrus: Update VM images #415
Closed
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
|
Now...this is curious. Looks like the same/similar failures as in #408 So I would hazard to guess, the problems are due to new packages/changes in the base-level image (which was fully updated). So...new kernel, different default kernel options/capibilities...that kind of thing. |
|
(I need help with a fix here and in #408...in case that wasn't clear) |
These were produced as an intended byproduct of: containers/podman#3754 Where 'systemd_banish.sh' was run during base-image production. This is a short-term fix, as there is much setup duplication here which can (hopefully) be avoided with: containers#408 Signed-off-by: Chris Evich <[email protected]>
|
@cevich Does this need to be updated 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.
These were produced as an intended byproduct of:
containers/podman#3754
Where 'systemd_banish.sh' was run during base-image production.
This is a short-term fix, as there is much setup duplication
here which can (hopefully) be avoided with:
#408
Signed-off-by: Chris Evich [email protected]