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

None network with null driver #2221

Closed
arun-gupta opened this Issue Nov 8, 2015 · 5 comments

Comments

Projects
None yet
4 participants
@arun-gupta
Copy link

arun-gupta commented Nov 8, 2015

The default set of networks created on Docker Machine are:

docker network ls
NETWORK ID          NAME                DRIVER
1d4d4152b99a        bridge              bridge              
8396171e6bbc        none                null                
8b50dda5fe61        host                host 

The "none" and "null" network seems wrong.

@dmp42

This comment has been minimized.

Copy link
Contributor

dmp42 commented Nov 8, 2015

@nathanleclaire

This comment has been minimized.

Copy link
Contributor

nathanleclaire commented Nov 9, 2015

I think it's intended behavior of libnetwork. That's what I get out of the box creating with Machine on an Ubuntu server and we haven't done any funny business setting up the network. @dave-tucker @mavenugo @mrjana let me know if you can confirm/deny this is expected behavior. Thanks.

@arun-gupta

This comment has been minimized.

Copy link
Author

arun-gupta commented Nov 9, 2015

Not sure if we reached closure on this issue :)

The "none" and "null" seems wrong independent of the operating system. How should a user interpret them and what are they for?

@mavenugo

This comment has been minimized.

Copy link

mavenugo commented Nov 9, 2015

@arun-gupta the none network is required to provide backward compatibility.... same as we do for host and bridge network.
this is equivalent to the --net=none option that the user is familiar with when running a container using docker run.

The reason the driver is called null is because, it is a null driver which doesnt do anything (as intended by the user).... the only thing it does is add a loopback interface (again as intended by the user for backward compatibility purposes).

@nathanleclaire

This comment has been minimized.

Copy link
Contributor

nathanleclaire commented Nov 9, 2015

Thanks @mavenugo !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.