Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Networks (and probably other things) are never cleaned up and docker has limits #15

Open
atamon opened this issue Oct 31, 2016 · 1 comment

Comments

@atamon
Copy link
Contributor

atamon commented Oct 31, 2016

I ran into the following while running build-contract locally:

Creating network "yoleanlive3yoleanliveclientunittests_default" with the default driver
ERROR: failed to parse pool request for address space "LocalDefault" pool "" subpool "": could not find an available predefined network

It seems related to moby/moby#23971 where they conclude that docker-compose down removes any created networks from the docker-compose run. Might we want to do this instead of docker-compose kill at https://github.com/Yolean/build-contract/blob/master/build-contract#L66?

@atamon
Copy link
Contributor Author

atamon commented Nov 25, 2016

We now do docker-compose rm -f. But #18 suggests that we actually use down as it not only helps with removing networks, but also (anonymous) volumes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant