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

Explicitly remove all launched containers from the default Docker bridge network #21

Closed
yousefamar opened this issue Mar 28, 2017 · 3 comments
Labels

Comments

@yousefamar
Copy link
Contributor

Issue by yousefamar
Thursday Mar 16, 2017 at 17:40 GMT # Sample: Friday Sep 13, 2013 at 22:58 GMT
Originally opened as me-box-archive/databox-netdev#57


By default, Docker connects all launched containers to the default Docker bridge network. This is bad for us, since although the container can't use Docker DNS to resolve the IPs of other containers, it can still communicate with them directly by IP, which it could just enumerate.

If you override this by setting NetworkMode to none, then the container can't connect to anything ever. The solution is to explicitly disconnect every container from the default Docker bridge network (by name — it's just called "bridge") on launching.

This should be pretty simple; we just need to add an extra step in the container launch Promise chain to disconnect it.

@yousefamar
Copy link
Contributor Author

Comment by yousefamar
Tuesday Mar 21, 2017 at 16:12 GMT # Sample: Friday Sep 13, 2013 at 22:58 GMT


We need this on the branch backupPlan too ideally. The default bridge (docker0) lets all containers have internet by default. Otherwise they're isolated.

@yousefamar yousefamar added the bug label Mar 28, 2017
@haddadi
Copy link
Contributor

haddadi commented Mar 28, 2017

maybe something for @sevenEng to also keep an eye out for ?

@yousefamar
Copy link
Contributor Author

Ah, @sevenEng did in fact implement this on databox-netdev, then @Toshbrown got it onto databox manually, so actually this resolved but we never closed the issue. Closing now.

pooyadav pushed a commit to pooyadav/databox that referenced this issue Oct 16, 2017
Bring branch up to date and connect self to CM-arbiter network on init
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants