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

Use external UDN docker network #51

Open
suranap opened this issue Dec 21, 2016 · 1 comment
Open

Use external UDN docker network #51

suranap opened this issue Dec 21, 2016 · 1 comment

Comments

@suranap
Copy link

suranap commented Dec 21, 2016

In my use case, I want to start several containers that handle my testing infrastructure: test drivers, logging, monitoring, alerting, etc. I want to use blockade to start and manipulate a set of nodes under test.

I want to start and destroy the blockade network between different tests. The problem is that blockade tries and fails to remove the user-defined network because my test infra is still connected to that network. Then it raises an exception and stops. Also, it creates a brand new network with the same name when I start blockade. So I've got multiple networks with the same name now.

I think one solution is to use the idea of an external network from docker-compose. I want to tell blockade to use an externally defined network, then it should not create and destroy it every time. It should just work on the containers. In docker-compose I'd do this:

networks:
  blockade:
    external:
      name: testinfra_net
@labisso
Copy link
Member

labisso commented Dec 21, 2016

I think this is a good idea. I don't have an immediate need for it, but will keep it in mind for future work in this area. In the meantime, pull requests are welcome. :-)

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

No branches or pull requests

2 participants