Fix potential panic in createLCOWSpec when no network ns is set #908
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.
Previously, if no network information was set on the given spec, we would hit a panic trying to set the new spec's windows devices since we relied on
setWindowsNetworkNamespace
to create the windows field. This PR fixes that by checking if the windows field is nil and creating it if so.Signed-off-by: Kathryn Baldauf [email protected]