With UniFi OS - Dream Machines 4.x.x. in EA, does nspawn-container still work?

[waffles0042]

Unify recently released 4.0.3 to EA. . I was wondering if the method for creating a custom container on UnifiOS 3.x+ and consequently installing things like PiHole still works.
Has anyone tried it yet and could share their findings? TIA!

[waffles0042]

To answer my own question, in case s.o. is wondering:
I just upgraded my UDM-Pro to 4.0.6 Release Candidate and everything (e.g. PiHole) still seems to have survived the upgrade and is running fine.

[hart-NTP]

I've been using the original on boot script with https://github.com/telnetdoogie/UDMP-ipv6 on a UDM Pro and just upgraded to the final UniFi OS 4.06 (not EA).

I believe the on boot stuff didn't survive the upgrade, Perhaps it would have if I used the newer on boot repo instead, I didn't know about it. Reinstalling on boot using pipe download to sh fixed it, and after a reboot my IPv6 tunnel came back up.

[robigan]

On Boot works but ultimately failed as my scripts failed. The only script that failed is 10-setup-network.sh as this line

unifios-utilities/nspawn-container/scripts/10-setup-network.sh

Lines 60 to 64 in 6c899cb

	# Make DNSMasq listen to the container network for split horizon or conditional forwarding
	if ! grep -qxF "interface=br${VLAN}.mac" /run/dnsmasq.conf.d/custom.conf; then
	echo "interface=br${VLAN}.mac" >>/run/dnsmasq.conf.d/custom.conf
	kill -9 "$(cat /run/dnsmasq.pid)"
	fi

produces the following error:
grep: /run/dnsmasq.conf.d/custom.conf: No such file or directory

[m4n63]

In my experience, that message is just the if clause failing, and while it does spit out the message, the script should still exit with a success as long as the other part are ok.

[robigan]

In my experience, that message is just the if clause failing, and while it does spit out the message, the script should still exit with a success as long as the other part are ok.

Realized this later. Then yeah all works