You are not logged in.

#1 2016-02-29 17:09:06

OlafLostViking
Member
From: Lost
Registered: 2013-01-30
Posts: 58

nspawn machine names resolution inside of containers

Hi!

Adding

mymachines

to nsswitch.conf enables a host to use names of containers started by systemd-nspawn to reach them over the (internal) network. But how do I get this kind of resolution inside of my containers? I want to ping (or whatever) from within container1 to container2. As all containers are connected to one bridge on the host, they can reach each other without problems. (Pinging the internal IP addresses of container2 inside of container1 works, f.ex.)

Last edited by OlafLostViking (2016-02-29 18:07:13)

Offline

#2 2016-08-12 11:28:34

mkov
Member
Registered: 2015-06-28
Posts: 6

Re: nspawn machine names resolution inside of containers

Have you manage to solve this problem? I have exact same one and I can't find any solution.

Offline

#3 2016-08-12 17:11:45

OlafLostViking
Member
From: Lost
Registered: 2013-01-30
Posts: 58

Re: nspawn machine names resolution inside of containers

Sorry, no. My current plan is to setup a central DNS VM which will provide these informations in the future.

Offline

#4 2016-08-16 11:11:30

mkov
Member
Registered: 2015-06-28
Posts: 6

Re: nspawn machine names resolution inside of containers

Containers should be connected to a virtual bridge, that they are in the same broadcast network. It can be automated by parameter "zone" it will create bridge automatically (systemd-networkd is required for this I think).

Offline

Board footer

Powered by FluxBB