Network Bridge Not Created When TrueNAS VM Based On Hyper-V

Apps and Virtualization
, , ,
1

I am waiting on hardware, and whilst waiting I am messing around with TrueNAS Scale in Hyper-V based VMs, along with other nas/virtualisation options to gauge what is best for me.

I want to run docker compose based application stacks and have had some success with Electric Eel due to it having the support needed but given I am not sure when exactly it will be released I wanted to get a docker jail working in Dragonfish too, to prove out things there.

For this to work I think I need to have a network bridge setup in TrueNAS which I can then bind to with the jail, as any attempt to use the macvlan through the github template for docker fails to have internet connectivity. However…a network bridge will not take no matter how much time I allow for the test, I think due to Hyper-V not supporting it, so am in a bit of a pickle.

If I setup a jail without the docker template it has internet connectivity (default network bindings) but then docker will not start, I think due to it needing it’s own network interface.

I’ve been reading into systemd-spawn and what I could do there to get things working but I am at a loss, it’s all very complex and I am new to this area of things, I have a very small amount of experience of chroot and that’s it.

Has anyone managed to get a Hyper-V based TrueNAS setup working with a network bridge, I assume the virtual switch needs some modifications to allow for it? Any other ideas? I am at a loss…thanks for any input you can give!

2

When running complicated networking (bridges/macvlan etc) in a VM, the hypervisor needs to allow advanced network configuration to the guest.

This is involves enabling settings like “promiscuous mode” or “network snooping” on the guest network interface in the hypervisor

BUT I have specifically had trouble getting the latest version of jailmaker to work with DHCP and bridges with the initial install. I found starting with macvlan, then switching to a bridge with static ip after initial setup worked.

1 Like
3

If I use macvlan it fails to resolve and apt installs fail…in the readme it says about setting static ip for mv-*…do you think that might help my cause here and is there any easy to use editor in the jail for that? Seems daft that the default rootfs has no simple editor like nano and I can’t install one…

edit:
I updated the mv-dhcp.network file using echo >/>> commands of what I needed to have a static ip setup which I confirmed with “ip a” but it still doesn’t ping/resolve successfully, also added 8.8.8.8 in the resolve.conf to be sure I had a known external nameserver and nope. A lack of promiscous mode support seems to be a blocker with Hyper-V maybe…