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 alternative that is even more useful is to allow for any service that specifies PrivateNetwork= also specify how that network should be initialized and connected to the outside world using the same options that are available with nspawn. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
