"File exists" error while starting container
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
On a freshly installed Ubuntu 20.04.1 VM, while starting a container created using
sudo lxc-create -t ubuntu -n testlxc
the following messages are shown:
lxc-start: testlxc: cgroups/cgfsng.c: mkdir_eexist_
lxc-start: testlxc: conf.c: lxc_setup_boot_id: 3249 Permission denied - Failed to mount /dev/.lxc-boot-id to /proc/sys/
The container starts correctly but it would be nice find out why those errors are being issued.
lxc-checkconfig output follows:
Kernel configuration not found at /proc/config.gz; searching...
Kernel configuration found at /boot/config-
--- Namespaces ---
Namespaces: enabled
Utsname namespace: enabled
Ipc namespace: enabled
Pid namespace: enabled
User namespace: enabled
Network namespace: enabled
--- Control groups ---
Cgroups: enabled
Cgroup v1 mount points:
/sys/fs/
/sys/fs/
/sys/fs/
/sys/fs/
/sys/fs/
/sys/fs/
/sys/fs/
/sys/fs/
/sys/fs/cgroup/pids
/sys/fs/
/sys/fs/
/sys/fs/cgroup/rdma
Cgroup v2 mount points:
/sys/fs/
Cgroup v1 clone_children flag: enabled
Cgroup device: enabled
Cgroup sched: enabled
Cgroup cpu account: enabled
Cgroup memory controller: enabled
Cgroup cpuset: enabled
--- Misc ---
Veth pair device: enabled, loaded
Macvlan: enabled, not loaded
Vlan: enabled, not loaded
Bridges: enabled, loaded
Advanced netfilter: enabled, not loaded
CONFIG_NF_NAT_IPV4: missing
CONFIG_NF_NAT_IPV6: missing
CONFIG_
CONFIG_
CONFIG_
CONFIG_
FUSE (for use with lxcfs): enabled, not loaded
--- Checkpoint/Restore ---
checkpoint restore: enabled
CONFIG_FHANDLE: enabled
CONFIG_EVENTFD: enabled
CONFIG_EPOLL: enabled
CONFIG_UNIX_DIAG: enabled
CONFIG_INET_DIAG: enabled
CONFIG_PACKET_DIAG: enabled
CONFIG_
File capabilities:
Note : Before booting a new kernel, you can check its configuration
usage : CONFIG=
The cpuset "error" is normal, it just means the directory was already there and is getting recycled. The boot_id permission problem has already been fixed upstream.