daemon: Fix not initialized network controller#54
Merged
Conversation
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
rumpl
approved these changes
Aug 10, 2022
Collaborator
|
This should be squashed with #51 when upstreaming |
Collaborator
|
@vvoland do you know which PR this was upstreamed in? (Or was this one skipped / superseded?) |
Collaborator
Author
|
This is a fixup for #51 (which won't be upstreamed), so this one is not needed. |
Collaborator
|
Ah, gotcha, thanks! |
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
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.
After #51 the container creation fails:
Error spoiler
Turns out the
Daemon.restoreactually does also initialize the network devices because it also does register links for the restored containers.I just changed the guard to make the code in this function think there are no containers at all.