Lennart Poettering wrote:
> One option could be to add --same-network= or so to nspawn
It seems it would be better to refer to the service unit that executed
nspawn, not the container running in the namespace created with
nspawn. This way I can refer to that unit using a stable name. Another
alt
On Thu, 28.07.16 20:19, Igor Bukanov ([email protected]) wrote:
> Hello,
>
> I am trying to see how to implement with systemd-nspawn a version of
> docker's pod when a group of very lightweight containers use a
> loopback interface or unix sockets to communicate with each other and
> a shared network
Hello,
I am trying to see how to implement with systemd-nspawn a version of
docker's pod when a group of very lightweight containers use a
loopback interface or unix sockets to communicate with each other and
a shared network interface to communicate with the outside world.
Otherwise the container
