Skip to content
This repository was archived by the owner on Nov 27, 2023. It is now read-only.

Ensure down continues (removes networks) even if containers have been removed already #1021

Merged
merged 1 commit into from
Dec 7, 2020

Conversation

gtardif
Copy link
Contributor

@gtardif gtardif commented Dec 7, 2020

Signed-off-by: Guillaume Tardif [email protected]

What I did

  • Avoid returning nil error and nil project in projectFromContainerLabels, return project with a name and no service if there are no containers
  • Test compose networks get removed after deleting compose containers separately (or compose up that created the network and failed on containers)

Related issue

(not mandatory) A picture of a cute animal, if possible in relation with what you did

… removed already. Avoid returning nil error and nil project in `projectFromContainerLabels`

Signed-off-by: Guillaume Tardif <[email protected]>
@gtardif gtardif requested review from ulyssessouza and rumpl December 7, 2020 14:51
@github-actions github-actions bot added the local Local context (moby) label Dec 7, 2020
@gtardif gtardif merged commit 8ee2286 into docker-archive:main Dec 7, 2020
@gtardif gtardif deleted the fix_down_no_containers branch December 7, 2020 16:33
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
local Local context (moby)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants