Support networks

[iamluc]

Hello,

I just discovered this project and I like it !

I have a little project that updates the /etc/hosts automatically (https://github.com/iamluc/docker-hostmanager) and I think it could be replaced by nss-docker.

However, IMHO, you should support docker networks.
For example, when a container app is launched in a network myproject_default, I would like to access my container with hostname app.myproject_default instead of app.docker.
Especially since there can be several networks for the same container, with differents IP address.

En bonus, it could manage alias and labels.

As a reference, this is how I manage the hosts in my project https://github.com/iamluc/docker-hostmanager/blob/master/src/Synchronizer.php#L115

Kind regards

[rooterkyberian]

Not sure if this is needed, as container name which seems to be used here by default does contain project name when docker-compose is used. It is also globally unique, so no additional name-spacing seems to be needed.

Aliases are indeed a use case for this tho.

[hansbogert]

However, IMHO, you should support docker networks.
For example, when a container app is launched in a network myproject_default, I would like to access my container with hostname app.myproject_default instead of app.docker.
Especially since there can be several networks for the same container, with differents IP address.

Do you mean it works currently, just not namespaced? Because I can't seem to get it to resolve if a container is in a non-default network