This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
virtualisation:start [2018/08/03 12:58] – [Example Containers] preisig | virtualisation:start [2021/06/15 19:40] – [Networking] juraschek | ||
---|---|---|---|
Line 36: | Line 36: | ||
+ | ==== Serial-Interface | ||
+ | | ||
===== Networking ===== | ===== Networking ===== | ||
Line 43: | Line 45: | ||
Generally you can either create a routed interface, where you set your own IP settings that will connect the router (through a virtual interface, virt0) to the guest interface of your cotnainer. The other option is that you bridge the containers interface to an existing one on the router. | Generally you can either create a routed interface, where you set your own IP settings that will connect the router (through a virtual interface, virt0) to the guest interface of your cotnainer. The other option is that you bridge the containers interface to an existing one on the router. | ||
+ | |||
+ | If you are using a routed interface please be sure you networking file is setting the ethernet interface into manual mode and not dhcp: | ||
+ | |||
+ | Example on an alpine guest: | ||
+ | |||
+ | Default in alpine template from linuxcontainers: | ||
+ | < | ||
+ | / $ cat / | ||
+ | auto eth0 | ||
+ | iface eth0 inet dhcp | ||
+ | hostname $(hostname) | ||
+ | / $ | ||
+ | </ | ||
+ | |||
+ | Need to be switched to | ||
+ | |||
+ | < | ||
+ | / $ cat / | ||
+ | auto eth0 | ||
+ | iface eth0 inet manual | ||
+ | hostname $(hostname) | ||
+ | / $ | ||
+ | </ | ||
+ | |||
+ | |||
+ | |||
===== Container Templates ===== | ===== Container Templates ===== |