I have a TrueNAS Scale - on the latest release (Bluefin) version and have been using jailmaker as a test for a while.
I have a single jail running portainer
When the jail is not running I do not have the issue shown here - but when I start the jail i get spammed with the following messages in the console log. [apologies for formatting - it looks good when I am editing the issue - so I have added some extra spaces]
`Sep 28 21:45:03 newnas.sendarian.co.uk kernel: br0: port 3(vb-docker-jail) entered blocking state
Sep 28 21:45:03 newnas.sendarian.co.uk kernel: br0: port 3(vb-docker-jail) entered disabled state
Sep 28 21:45:03 newnas.sendarian.co.uk kernel: device vb-docker-jail entered promiscuous mode
Sep 28 21:45:03 newnas.sendarian.co.uk kernel: br0: port 3(vb-docker-jail) entered blocking state
Sep 28 21:45:03 newnas.sendarian.co.uk kernel: br0: port 3(vb-docker-jail) entered listening state
Sep 28 21:45:03 newnas.sendarian.co.uk kernel: br0: port 3(vb-docker-jail) entered disabled state
Sep 28 21:45:08 newnas.sendarian.co.uk kernel: IPv6: ADDRCONF(NETDEV_CHANGE): host0: link becomes ready
Sep 28 21:45:08 newnas.sendarian.co.uk kernel: br0: port 3(vb-docker-jail) entered blocking state
Sep 28 21:45:08 newnas.sendarian.co.uk kernel: br0: port 3(vb-docker-jail) entered listening state
Sep 28 21:45:23 newnas.sendarian.co.uk kernel: br0: port 3(vb-docker-jail) entered learning state
Sep 28 21:45:25 newnas.sendarian.co.uk kernel: docker0: port 1(veth9aba5b5) entered blocking state
Sep 28 21:45:25 newnas.sendarian.co.uk kernel: docker0: port 1(veth9aba5b5) entered disabled state
Sep 28 21:45:25 newnas.sendarian.co.uk kernel: device veth9aba5b5 entered promiscuous mode
Sep 28 21:45:25 newnas.sendarian.co.uk kernel: docker0: port 1(veth9aba5b5) entered blocking state
Sep 28 21:45:25 newnas.sendarian.co.uk kernel: docker0: port 1(veth9aba5b5) entered forwarding state
Sep 28 21:45:25 newnas.sendarian.co.uk kernel: IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
Sep 28 21:45:25 newnas.sendarian.co.uk kernel: docker0: port 1(veth9aba5b5) entered disabled state
Sep 28 21:45:27 newnas.sendarian.co.uk kernel: eth0: renamed from vethe8b166a
Sep 28 21:45:27 newnas.sendarian.co.uk kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth9aba5b5: link becomes ready
Sep 28 21:45:27 newnas.sendarian.co.uk kernel: docker0: port 1(veth9aba5b5) entered blocking state
Sep 28 21:45:27 newnas.sendarian.co.uk kernel: docker0: port 1(veth9aba5b5) entered forwarding state
Sep 28 21:45:38 newnas.sendarian.co.uk kernel: br0: port 3(vb-docker-jail) entered forwarding state
Sep 28 21:45:38 newnas.sendarian.co.uk kernel: br0: topology change detected, sending tcn bpdu
Sep 28 21:46:52 newnas.sendarian.co.uk kernel: br-be2b02c1ea85: port 1(veth9390273) entered blocking state
Sep 28 21:46:52 newnas.sendarian.co.uk kernel: br-be2b02c1ea85: port 1(veth9390273) entered disabled state
Sep 28 21:46:52 newnas.sendarian.co.uk kernel: device veth9390273 entered promiscuous mode
Sep 28 21:46:53 newnas.sendarian.co.uk kernel: eth0: renamed from veth989bad2
Sep 28 21:46:53 newnas.sendarian.co.uk kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth9390273: link becomes ready
Sep 28 21:46:53 newnas.sendarian.co.uk kernel: br-be2b02c1ea85: port 1(veth9390273) entered blocking state
Sep 28 21:46:53 newnas.sendarian.co.uk kernel: br-be2b02c1ea85: port 1(veth9390273) entered forwarding state
Sep 28 21:46:53 newnas.sendarian.co.uk kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-be2b02c1ea85: link becomes ready
Sep 28 21:46:53 newnas.sendarian.co.uk kernel: br-be2b02c1ea85: port 1(veth9390273) entered disabled state
Sep 28 21:46:53 newnas.sendarian.co.uk kernel: veth989bad2: renamed from eth0
Sep 28 21:46:53 newnas.sendarian.co.uk kernel: br-be2b02c1ea85: port 1(veth9390273) entered disabled state
Sep 28 21:46:53 newnas.sendarian.co.uk kernel: device veth9390273 left promiscuous mode
Sep 28 21:46:53 newnas.sendarian.co.uk kernel: br-be2b02c1ea85: port 1(veth9390273) entered disabled state`
I start docker-jail with the following command (actually "./jlmakr.py start docker-jail")
systemd-run --property=KillMode=mixed --property=Type=notify --property=RestartForceExitStatus=133 --property=SuccessExitStatus=133 --property=Delegate=yes --property=TasksMax=infinity --collect --setenv=SYSTEMD_NSPAWN_LOCK=0 --unit=jlmkr-docker-jail --working-directory=./jails/docker-jail '--description=My nspawn jail docker-jail [created with jailmaker]' --setenv=SYSTEMD_SECCOMP=0 --property=DevicePolicy=auto -- systemd-nspawn --keep-unit --quiet --boot --machine=docker-jail --directory=rootfs --capability=all '--system-call-filter=add_key keyctl bpf' --network-bridge=br0 --resolv-conf=bind-host
The jail has its own IP address on my network. I am using advanced networking (from the manual) to give the jail its own IP seperate from the host
docker-jail config file:
`docker_compatible=1
gpu_passthrough_intel=0
gpu_passthrough_nvidia=0
systemd_nspawn_user_args=--network-bridge=br0 --resolv-conf=bind-host
You generally will not need to change the options below
systemd_run_default_args=--property=KillMode=mixed --property=Type=notify --property=RestartForceExitStatus=133 --property=SuccessExitStatus=133 --property=Delegate=yes --property=TasksMax=infinity --collect --setenv=SYSTEMD_NSPAWN_LOCK=0
systemd_nspawn_default_args=--keep-unit --quiet --boot`
80-container-host0.network file in container
`[Match]
Virtualization=container
Name=host0
[Network]
DHCP=false
Address=192.168.38.191/24
Gateway=192.168.38.15
LinkLocalAddressing=no
LLDP=yes
EmitLLDP=customer-bridge
[DHCP]
UseTimezone=yes
`
Anything else I can provide?