[CI DEBUG] Debugging docker failure #3616
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
apostasie
force-pushed
the
debug-docker-bug-early-start
branch
9 times, most recently
from
737e8e8 to
e175054
Compare
Signed-off-by: apostasie <[email protected]>
apostasie
force-pushed
the
debug-docker-bug-early-start
branch
from
e175054 to
3524efa
Compare
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.
It appears that in certain conditions, short of pulling first, docker will fail to start the container.
Debugging shows container exited immediately. Nothing in the container logs. Not much in journalctl.
It is not clear what is happening.
Discussion at #3574 (comment)