[Arch|AUR] After upgrading to 3.4 nginx won't start on container because it can't open /dev/null #4950
After update from 3.3 to 3.4 (I use the AUR
Note: At the same time as I upgraded I managed to get IPv6 finally working on my network, so it could possibly be related.
Steps to reproduce
Setting the container to a privileged one works around this.
The text was updated successfully, but these errors were encountered:
From my info:
I'd imagine this is the liblxc version? If not then am not sure how I'd go about upgrading it as I can't find any reference to it in the PKGBUILD https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=lxd
How do I even get which liblxc version I am using if it's not in the driver_version row I posted?
@stgraber, this is LXD running with liblxc 3.0.2 as the output shows. LXC is handling this case correctly otherwise the container wouldn't run.
This is caused by systemd's
I tried to fix this regression in the kernel as well as in systemd. Since we've decided to move forward with this change on the kernel side you should report this failure on my systemd PR ( systemd/systemd#9483 ) and lobby for a systemd change if they are open for it.