LXD container fails when switching to privileged

When changing an arch or ubuntu 18.04 containers to priviledged. It will either not start or loose network connection.

my network setup is:

lxc profile show lan-br0
config: {}
description: “”
devices:
eth0:
name: eth0
nictype: bridged
parent: br0
type: nic
root:
path: /
pool: lxd
type: disk
name: lan-br0
used_by:

  • /1.0/instances/u-18
  • /1.0/instances/arch1
  • /1.0/instances/arch2

lxc start u-18 # ubuntu 18.04

Error: Failed to run: /snap/lxd/current/bin/lxd forkstart u-18 /var/snap/lxd/common/lxd/containers /var/snap/lxd/common/lxd/logs/u-18/lxc.conf:
Try lxc info --show-log u-18 for more info

lxc info --show-log u-18
ame: u-18
Location: none
Remote: unix://
Architecture: x86_64
Created: 2020/04/12 18:33 UTC
Status: Stopped
Type: container
Profiles: lan-br0, x11
Snapshots:
ubuntu-18.04-base (taken at 2020/04/20 03:45 UTC) (stateless)

Log:

lxc u-18 20200425211820.314 ERROR cgfsng - cgroups/cgfsng.c:mkdir_eexist_on_last:1143 - File exists - Failed to create directory “/sys/fs/cgroup/cpuset//lxc.monitor.u-18”
lxc u-18 20200425211820.316 ERROR cgfsng - cgroups/cgfsng.c:mkdir_eexist_on_last:1143 - File exists - Failed to create directory “/sys/fs/cgroup/cpuset//lxc.payload.u-18”
lxc u-18 20200425211820.458 ERROR conf - conf.c:run_buffer:323 - Script exited with status 1
lxc u-18 20200425211820.458 ERROR conf - conf.c:lxc_setup:3364 - Failed to run mount hooks
lxc u-18 20200425211820.458 ERROR start - start.c:do_start:1231 - Failed to setup container “u-18”
lxc u-18 20200425211820.458 ERROR sync - sync.c:__sync_wait:41 - An error occurred in another process (expected sequence number 5)
lxc u-18 20200425211820.461 WARN network - network.c:lxc_delete_network_priv:3213 - Failed to rename interface with index 0 from “eth0” to its initial name “veth780a6dbb”
lxc u-18 20200425211820.461 ERROR start - start.c:__lxc_start:1952 - Failed to spawn container “u-18”
lxc u-18 20200425211820.461 ERROR lxccontainer - lxccontainer.c:wait_on_daemonized_start:852 - Received container state “ABORTING” instead of “RUNNING”
lxc u-18 20200425211820.461 WARN start - start.c:lxc_abort:1025 - No such process - Failed to send SIGKILL via pidfd 31 for process 181480
lxc 20200425211820.623 WARN commands - commands.c:lxc_cmd_rsp_recv:122 - Connection reset by peer - Failed to receive response for command “get_state”

for the arch container I get a different error (? different issue)

lxc start arch1 #archlinux

Error: Common start logic: Failed to change ACLs on /var/snap/lxd/common/lxd/storage-pools/lxd/containers/arch1/rootfs/var/log/journal
Try lxc info --show-log arch1 for more info

lxc info --show-log arch1

Name: arch1
Location: none
Remote: unix://
Architecture: x86_64
Created: 2020/04/24 15:58 UTC
Status: Stopped
Type: container
Profiles: lan-br0

Log:

lxc arch1 20200425204456.580 ERROR cgfsng - cgroups/cgfsng.c:mkdir_eexist_on_last:1143 - File exists - Failed to create directory “/sys/fs/cgroup/cpuset//lxc.monitor.arch1”
lxc arch1 20200425204456.600 ERROR cgfsng - cgroups/cgfsng.c:mkdir_eexist_on_last:1143 - File exists - Failed to create directory “/sys/fs/cgroup/cpuset//lxc.payload.arch1”
lxc arch1 20200425204456.641 WARN cgfsng - cgroups/cgfsng.c:fchowmodat:1455 - No such file or directory - Failed to fchownat(17, memory.oom.group, 1000000000, 0, AT_EMPTY_PATH | AT_SYMLINK_NOFOLLOW )

But when creating the container as privileged (unlike changing existing to privileged)
the ubuntu container is running with network. The archlinux container runs, but fails to create a network connection (ipv4 network). It does create an ipv6 network)
.

What LXD version is that?

The shift issue makes it sound like 3.0

The latest snap on 20.04. 4.0.1

I was able to start network on the arch manually with the ip command.

raw.lxc: |
lxc.mount.auto = proc:rw sys:ro

did not help.