OK so we are getting clearer on the problem now, the issue is that systemd-networkd cannot start without security.nesting=true being set.
So we can say that something that systemd-networkd is trying to do inside Arch container is being blocked without that setting.
Perhaps check your AppArmor logs to see what is being blocked when security.nesting=false and you try to start systemd-networkd.