From 0dea18fb40e51e1b5945029b954235d9f0994f19 Mon Sep 17 00:00:00 2001 From: Nicolas.Schodet Date: Tue, 3 Oct 2017 19:08:57 +0000 Subject: --- doc/forum/Using_ip_address_in_a_container.mdwn | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 doc/forum/Using_ip_address_in_a_container.mdwn (limited to 'doc') diff --git a/doc/forum/Using_ip_address_in_a_container.mdwn b/doc/forum/Using_ip_address_in_a_container.mdwn new file mode 100644 index 00000000..57b8a2e1 --- /dev/null +++ b/doc/forum/Using_ip_address_in_a_container.mdwn @@ -0,0 +1,22 @@ +Hello, + +I would like to create a systemd container using the --network-bridge option +to systemd-nspawn and fixed addresses. + +Previously I used lxc containers but I'm afraid adding lxc support is quite a +large task. + +My previous setup includes: + - static ip addresses per container (set using LXC, but + /etc/network/interface will do), + - different hostname for each of the containers, + - configuration of a bind zone for my local container network, + - configuration of the firewall using ferm, + - proxy from host to containers using nginx. + +If I understand correctly, alias or ipv4 are propagated to the host and are +not part of the container definition, is that right? + +I am also not sure about the setting of the hostname. + +Do you have some hints about how this could be done? -- cgit v1.2.3