This repository was archived by the owner on Feb 24, 2020. It is now read-only.
stage1: propagate app exit code to rkt exit code #2201
Closed
Conversation
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
If the version of the systemd running in stage1 is >=v229, the command "systemctl exit STATUS" will set the exit status of the container. If not, we will continue with the previous logic, so we can merge this now and benefit from it when we actually update to v229.
Modify functions that wait for rkt to expect a particular exit code instead of only success and fail.
|
I guess I need more caffeine. This had a PR already (#2198). Closing. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
If the version of the systemd running in stage1 is >=v229, the command
"systemctl exit STATUS" will set the exit status of the container. If
not, we will continue with the previous logic, so we can merge this now
and benefit from it when we actually update to v229.
Refs #1460