MeisterBob
Cadet
- Joined
- Jan 15, 2022
- Messages
- 1
Hello,
I managed to setup my network so the apps and my homeassistant VM can be access by the LAN/WAN. To achieve this I disabled DHCP and removed the IP settings from the network interface (enp0s31f6) and created a bridge (br0) with dhcp enabled.
But now docker containers I run on the truenas host can't acces the network anymore:
what can I do give network access to the container? Using --network host isn't a good option, because that causes conflicts with ports already in use by other apps.
I managed to setup my network so the apps and my homeassistant VM can be access by the LAN/WAN. To achieve this I disabled DHCP and removed the IP settings from the network interface (enp0s31f6) and created a bridge (br0) with dhcp enabled.
But now docker containers I run on the truenas host can't acces the network anymore:
Code:
meisterbob@truenas:~$ docker run --rm alpine ping google.de ping: bad address 'google.de' meisterbob@truenas:~$ docker run --rm alpine ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever
what can I do give network access to the container? Using --network host isn't a good option, because that causes conflicts with ports already in use by other apps.