[SOLVED] Unable to start custom-built LXC container

BlueLineSwinger

New Member
Sep 11, 2017
29
2
1
For various reasons, I'm looking to run containers that aren't based on the prepackaged templates (either through Proxmox or the 'lxc-create' command). To that end, I've created a basic Ubuntu Zesty container using debootstrap under fakeroot/fakechroot.

This works fine if I run the container under straight LXC (i.e., 'lxc-start') on an Ubuntu host, but it will not run under Proxmox. Best I can tell, the issue is with getting the network interfaces for the container configured and/or started. It doesn't matter if set up for static or DHCP addressing. Switching between privileged/unprivileged also makes no difference.

Various logs and configs are below. Thanks for the help.


Code:
arch: amd64
cores: 1
hostname: ct-test
memory: 1024
net0: name=eth0,bridge=vmbr0,hwaddr=AA:BB:CC:7E:C3:E1,ip=dhcp,tag=10,type=veth
ostype: ubuntu
rootfs: local-lvm:vm-105-disk-1,size=8G
swap: 1024
unprivileged: 1

Code:
Job for lxc@105.service failed because the control process exited with error code.
See "systemctl status lxc@105.service" and "journalctl -xe" for details.
command 'systemctl start lxc@105' failed: exit code 1

Code:
● lxc@105.service - LXC Container: 105
   Loaded: loaded (/lib/systemd/system/lxc@.service; disabled; vendor preset: enabled)
  Drop-In: /usr/lib/systemd/system/lxc@.service.d
           └─pve-reboot.conf
   Active: failed (Result: exit-code) since Thu 2017-10-19 20:58:19 PDT; 28s ago
     Docs: man:lxc-start
           man:lxc
  Process: 10082 ExecStopPost=/usr/share/lxc/lxc-pve-reboot-trigger 105 (code=exited, status=0/SUCCESS)
  Process: 789 ExecStart=/usr/bin/lxc-start -n 105 (code=exited, status=1/FAILURE)
 Main PID: 23862 (code=exited, status=1/FAILURE)

Oct 19 20:58:13 vm1 ovs-vsctl[853]: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl add-port vmbr0 veth105i0 tag=10
Oct 19 20:58:14 vm1 ovs-vsctl[937]: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port fwln105i0
Oct 19 20:58:14 vm1 ovs-vsctl[939]: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port veth105i0
Oct 19 20:58:19 vm1 lxc-start[789]: lxc-start: tools/lxc_start.c: main: 366 The container failed to start.
Oct 19 20:58:19 vm1 lxc-start[789]: lxc-start: tools/lxc_start.c: main: 368 To get more details, run the container in foreground mode.
Oct 19 20:58:19 vm1 lxc-start[789]: lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options.
Oct 19 20:58:19 vm1 systemd[1]: lxc@105.service: Control process exited, code=exited status=1
Oct 19 20:58:19 vm1 systemd[1]: Failed to start LXC Container: 105.
Oct 19 20:58:19 vm1 systemd[1]: lxc@105.service: Unit entered failed state.
Oct 19 20:58:19 vm1 systemd[1]: lxc@105.service: Failed with result 'exit-code'.

Code:
Oct 19 20:58:12 vm1 kernel: EXT4-fs (dm-13): mounted filesystem with ordered data mode. Opts: (null)
Oct 19 20:58:12 vm1 systemd-udevd[808]: Could not generate persistent MAC address for vethTND4PP: No such file or directory
Oct 19 20:58:12 vm1 kernel: IPv6: ADDRCONF(NETDEV_UP): veth105i0: link is not ready
Oct 19 20:58:13 vm1 ovs-vsctl[851]: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port veth105i0
Oct 19 20:58:13 vm1 ovs-vsctl[851]: ovs|00002|db_ctl_base|ERR|no port named veth105i0
Oct 19 20:58:13 vm1 ovs-vsctl[852]: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port fwln105i0
Oct 19 20:58:13 vm1 ovs-vsctl[852]: ovs|00002|db_ctl_base|ERR|no port named fwln105i0
Oct 19 20:58:13 vm1 ovs-vsctl[853]: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl add-port vmbr0 veth105i0 tag=10
Oct 19 20:58:13 vm1 kernel: device veth105i0 entered promiscuous mode
Oct 19 20:58:13 vm1 kernel: eth0: renamed from vethTND4PP
Oct 19 20:58:13 vm1 kernel: device veth105i0 left promiscuous mode
Oct 19 20:58:14 vm1 ovs-vsctl[937]: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port fwln105i0
Oct 19 20:58:14 vm1 ovs-vsctl[937]: ovs|00002|db_ctl_base|ERR|no port named fwln105i0
Oct 19 20:58:14 vm1 ovs-vsctl[939]: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port veth105i0
Oct 19 20:58:19 vm1 lxc-start[789]: lxc-start: tools/lxc_start.c: main: 366 The container failed to start.
Oct 19 20:58:19 vm1 lxc-start[789]: lxc-start: tools/lxc_start.c: main: 368 To get more details, run the container in foreground mode.
Oct 19 20:58:19 vm1 lxc-start[789]: lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options.
Oct 19 20:58:19 vm1 systemd[1]: lxc@105.service: Control process exited, code=exited status=1
Oct 19 20:58:19 vm1 systemd[1]: Failed to start LXC Container: 105.
-- Subject: Unit lxc@105.service has failed
-- Defined-By: systemd
-- Support: 
--
-- Unit lxc@105.service has failed.
--
-- The result is failed.
Oct 19 20:58:19 vm1 systemd[1]: lxc@105.service: Unit entered failed state.
Oct 19 20:58:19 vm1 systemd[1]: lxc@105.service: Failed with result 'exit-code'.
Oct 19 20:58:19 vm1 pct[787]: command 'systemctl start lxc@105' failed: exit code 1
Oct 19 20:58:19 vm1 pct[786]: <root@pam> end task UPID:vm1:00000313:140D75D9:59E97454:vzstart:105:root@pam: command 'systemctl start lxc@105' failed: exit code 1
Oct 19 20:59:00 vm1 systemd[1]: Starting Proxmox VE replication runner...
-- Subject: Unit pvesr.service has begun start-up
-- Defined-By: systemd
-- Support: 
--
-- Unit pvesr.service has begun starting up.
Oct 19 20:59:00 vm1 systemd[1]: Started Proxmox VE replication runner.
-- Subject: Unit pvesr.service has finished start-up
-- Defined-By: systemd
-- Support: 
--
-- Unit pvesr.service has finished starting up.
--
-- The start-up result is done.

Code:
lxc-start: sync.c: __sync_wait: 57 An error occurred in another process (expected sequence number 5)
lxc-start: start.c: __lxc_start: 1381 Failed to spawn container "105".
lxc-start: tools/lxc_start.c: main: 366 The container failed to start.
lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options.

Code:
lxc-start 20171020040036.860 INFO     lxc_start_ui - tools/lxc_start.c:main:275 - using rcfile /var/lib/lxc/105/config
lxc-start 20171020040036.860 WARN     lxc_confile - confile.c:config_pivotdir:2022 - lxc.pivotdir is ignored.  It will soon become an error.
lxc-start 20171020040036.860 INFO     lxc_confile - confile.c:config_idmap:1643 - read uid map: type u nsid 0 hostid 100000 range 65536
lxc-start 20171020040036.860 INFO     lxc_confile - confile.c:config_idmap:1643 - read uid map: type g nsid 0 hostid 100000 range 65536
lxc-start 20171020040036.861 INFO     lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:418 - processing: .reject_force_umount  # comment this to allow umount -f;  not recommended.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:590 - Adding native rule for reject_force_umount action 0.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:259 - Setting Seccomp rule to reject force umounts.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:593 - Adding compat rule for reject_force_umount action 0.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:259 - Setting Seccomp rule to reject force umounts.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:259 - Setting Seccomp rule to reject force umounts.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:418 - processing: .[all].
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:418 - processing: .kexec_load errno 1.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:590 - Adding native rule for kexec_load action 327681.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:593 - Adding compat rule for kexec_load action 327681.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:418 - processing: .open_by_handle_at errno 1.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:590 - Adding native rule for open_by_handle_at action 327681.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:593 - Adding compat rule for open_by_handle_at action 327681.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:418 - processing: .init_module errno 1.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:590 - Adding native rule for init_module action 327681.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:593 - Adding compat rule for init_module action 327681.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:418 - processing: .finit_module errno 1.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:590 - Adding native rule for finit_module action 327681.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:593 - Adding compat rule for finit_module action 327681.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:418 - processing: .delete_module errno 1.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:590 - Adding native rule for delete_module action 327681.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:593 - Adding compat rule for delete_module action 327681.
lxc-start 20171020040036.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:603 - Merging in the compat Seccomp ctx into the main one.
lxc-start 20171020040036.861 INFO     lxc_conf - conf.c:run_script_argv:483 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "105", config section "lxc".
lxc-start 20171020040037.367 DEBUG    lxc_start - start.c:setup_signal_fd:273 - Set SIGCHLD handler with file descriptor: 5.
lxc-start 20171020040037.367 DEBUG    console - console.c:lxc_console_peer_default:447 - using "/dev/tty" as peer tty device
lxc-start 20171020040037.367 DEBUG    console - console.c:lxc_console_sigwinch_init:144 - 1306 got SIGWINCH fd 9
lxc-start 20171020040037.367 DEBUG    console - console.c:lxc_console_winsz:71 - set winsz dstfd:6 cols:181 rows:45
lxc-start 20171020040037.367 INFO     lxc_start - start.c:lxc_init:475 - Container "105" is initialized.
lxc-start 20171020040037.367 DEBUG    lxc_start - start.c:__lxc_start:1352 - Not dropping CAP_SYS_BOOT or watching utmp.
lxc-start 20171020040037.371 INFO     lxc_conf - conf.c:run_script:534 - Executing script "/usr/share/lxc/lxcnetaddbr" for container "105", config section "net".
lxc-start 20171020040037.660 DEBUG    lxc_conf - conf.c:instantiate_veth:2849 - instantiated veth 'veth105i0/vethQOM5OX', index is '83'
lxc-start 20171020040037.660 INFO     lxc_cgroup - cgroups/cgroup.c:cgroup_init:68 - cgroup driver cgroupfs-ng initing for 105
lxc-start 20171020040037.660 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:filter_and_set_cpus:481 - No isolated cpus detected.
lxc-start 20171020040037.660 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:handle_cpuset_hierarchy:651 - "cgroup.clone_children" was already set to "1".
lxc-start 20171020040037.660 INFO     lxc_start - start.c:lxc_spawn:1169 - Cloned CLONE_NEWUSER.
lxc-start 20171020040037.660 INFO     lxc_start - start.c:lxc_spawn:1169 - Cloned CLONE_NEWNS.
lxc-start 20171020040037.660 INFO     lxc_start - start.c:lxc_spawn:1169 - Cloned CLONE_NEWPID.
lxc-start 20171020040037.660 INFO     lxc_start - start.c:lxc_spawn:1169 - Cloned CLONE_NEWUTS.
lxc-start 20171020040037.660 INFO     lxc_start - start.c:lxc_spawn:1169 - Cloned CLONE_NEWIPC.
lxc-start 20171020040037.660 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newuidmap" does have the setuid bit set.
lxc-start 20171020040037.660 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newgidmap" does have the setuid bit set.
lxc-start 20171020040037.660 DEBUG    lxc_conf - conf.c:lxc_map_ids:3469 - Functional newuidmap and newgidmap binary found.
lxc-start 20171020040037.663 INFO     lxc_start - start.c:do_start:745 - Unshared CLONE_NEWNET.
lxc-start 20171020040037.663 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2031 - cgroup 'memory.limit_in_bytes' set to '1073741824'
lxc-start 20171020040037.663 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2031 - cgroup 'memory.memsw.limit_in_bytes' set to '2147483648'
lxc-start 20171020040037.663 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2031 - cgroup 'cpu.shares' set to '1024'
lxc-start 20171020040037.663 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2031 - cgroup 'cpuset.cpus' set to '5'
lxc-start 20171020040037.663 INFO     lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2035 - cgroup has been setup
lxc-start 20171020040037.663 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newuidmap" does have the setuid bit set.
lxc-start 20171020040037.663 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newgidmap" does have the setuid bit set.
lxc-start 20171020040037.663 DEBUG    lxc_conf - conf.c:lxc_map_ids:3469 - Functional newuidmap and newgidmap binary found.
lxc-start 20171020040037.706 DEBUG    lxc_conf - conf.c:lxc_assign_network:3356 - move 'vethQOM5OX'/'eth0' to '1390': .
lxc-start 20171020040037.706 NOTICE   lxc_utils - utils.c:lxc_switch_uid_gid:2062 - Switched to gid 0.
lxc-start 20171020040037.706 NOTICE   lxc_utils - utils.c:lxc_switch_uid_gid:2068 - Switched to uid 0.
lxc-start 20171020040037.706 NOTICE   lxc_utils - utils.c:lxc_setgroups:2080 - Dropped additional groups.
lxc-start 20171020040037.708 DEBUG    lxc_conf - conf.c:setup_rootfs:1260 - Mounted rootfs "/var/lib/lxc/105/rootfs" onto "/usr/lib/x86_64-linux-gnu/lxc/rootfs" with options "(null)".
lxc-start 20171020040037.708 INFO     lxc_conf - conf.c:setup_utsname:881 - 'ct-test' hostname has been setup
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:setup_hw_addr:2340 - mac address 'AA:BB:CC:7E:C3:E1' on 'eth0' has been setup
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:setup_netdev:2567 - 'eth0' has been setup
lxc-start 20171020040037.738 INFO     lxc_conf - conf.c:setup_network:2588 - network has been setup
lxc-start 20171020040037.738 INFO     lxc_conf - conf.c:mount_autodev:1110 - Mounting container /dev
lxc-start 20171020040037.738 INFO     lxc_conf - conf.c:mount_autodev:1133 - Mounted tmpfs onto /usr/lib/x86_64-linux-gnu/lxc/rootfs/dev
lxc-start 20171020040037.738 INFO     lxc_conf - conf.c:mount_autodev:1151 - Mounted container /dev
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1830 - remounting /sys/fs/fuse/connections on /usr/lib/x86_64-linux-gnu/lxc/rootfs/sys/fs/fuse/connections to respect bind or remount options
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1845 - (at remount) flags for /sys/fs/fuse/connections was 4096, required extra flags are 0
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1854 - mountflags already was 4096, skipping remount
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1880 - mounted '/sys/fs/fuse/connections' on '/usr/lib/x86_64-linux-gnu/lxc/rootfs/sys/fs/fuse/connections', type 'none'
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1830 - remounting /sys/kernel/debug on /usr/lib/x86_64-linux-gnu/lxc/rootfs/sys/kernel/debug to respect bind or remount options
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1845 - (at remount) flags for /sys/kernel/debug was 4096, required extra flags are 0
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1854 - mountflags already was 4096, skipping remount
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1880 - mounted '/sys/kernel/debug' on '/usr/lib/x86_64-linux-gnu/lxc/rootfs/sys/kernel/debug', type 'none'
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1830 - remounting /sys/kernel/security on /usr/lib/x86_64-linux-gnu/lxc/rootfs/sys/kernel/security to respect bind or remount options
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1845 - (at remount) flags for /sys/kernel/security was 4110, required extra flags are 14
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1880 - mounted '/sys/kernel/security' on '/usr/lib/x86_64-linux-gnu/lxc/rootfs/sys/kernel/security', type 'none'
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1830 - remounting /sys/fs/pstore on /usr/lib/x86_64-linux-gnu/lxc/rootfs/sys/fs/pstore to respect bind or remount options
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1845 - (at remount) flags for /sys/fs/pstore was 4110, required extra flags are 14
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1880 - mounted '/sys/fs/pstore' on '/usr/lib/x86_64-linux-gnu/lxc/rootfs/sys/fs/pstore', type 'none'
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1880 - mounted 'mqueue' on '/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/mqueue', type 'mqueue'
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1830 - remounting /dev/full on /usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/full to respect bind or remount options
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1845 - (at remount) flags for /dev/full was 4098, required extra flags are 2
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1880 - mounted '/dev/full' on '/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/full', type 'none'
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1830 - remounting /dev/null on /usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/null to respect bind or remount options
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1845 - (at remount) flags for /dev/null was 4098, required extra flags are 2
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1880 - mounted '/dev/null' on '/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/null', type 'none'
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1830 - remounting /dev/random on /usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/random to respect bind or remount options
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1845 - (at remount) flags for /dev/random was 4098, required extra flags are 2
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1880 - mounted '/dev/random' on '/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/random', type 'none'
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1830 - remounting /dev/tty on /usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/tty to respect bind or remount options
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1845 - (at remount) flags for /dev/tty was 4098, required extra flags are 2
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1880 - mounted '/dev/tty' on '/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/tty', type 'none'
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1830 - remounting /dev/urandom on /usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/urandom to respect bind or remount options
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1845 - (at remount) flags for /dev/urandom was 4098, required extra flags are 2
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1880 - mounted '/dev/urandom' on '/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/urandom', type 'none'
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1830 - remounting /dev/zero on /usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/zero to respect bind or remount options
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1845 - (at remount) flags for /dev/zero was 4098, required extra flags are 2
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1880 - mounted '/dev/zero' on '/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/zero', type 'none'
lxc-start 20171020040037.738 INFO     lxc_conf - conf.c:mount_entry:1819 - failed to mount '/sys/firmware/efi/efivars' on '/usr/lib/x86_64-linux-gnu/lxc/rootfs/sys/firmware/efi/efivars' (optional): No such file or directory
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1830 - remounting /proc/sys/fs/binfmt_misc on /usr/lib/x86_64-linux-gnu/lxc/rootfs/proc/sys/fs/binfmt_misc to respect bind or remount options
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1845 - (at remount) flags for /proc/sys/fs/binfmt_misc was 4096, required extra flags are 0
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1854 - mountflags already was 4096, skipping remount
lxc-start 20171020040037.738 DEBUG    lxc_conf - conf.c:mount_entry:1880 - mounted '/proc/sys/fs/binfmt_misc' on '/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc/sys/fs/binfmt_misc', type 'none'
lxc-start 20171020040037.738 INFO     lxc_conf - conf.c:mount_file_entries:2100 - mount points have been setup
lxc-start 20171020040037.738 INFO     lxc_conf - conf.c:run_script_argv:483 - Executing script "/usr/share/lxcfs/lxc.mount.hook" for container "105", config section "lxc".
lxc-start 20171020040037.748 INFO     lxc_conf - conf.c:run_script_argv:483 - Executing script "/usr/share/lxc/hooks/lxc-pve-autodev-hook" for container "105", config section "lxc".
lxc-start 20171020040037.850 INFO     lxc_conf - conf.c:lxc_fill_autodev:1188 - populating container /dev
lxc-start 20171020040037.850 DEBUG    lxc_conf - conf.c:lxc_fill_autodev:1203 - "/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/null" device already existed
lxc-start 20171020040037.850 DEBUG    lxc_conf - conf.c:lxc_fill_autodev:1203 - "/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/zero" device already existed
lxc-start 20171020040037.850 DEBUG    lxc_conf - conf.c:lxc_fill_autodev:1203 - "/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/full" device already existed
lxc-start 20171020040037.850 DEBUG    lxc_conf - conf.c:lxc_fill_autodev:1203 - "/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/urandom" device already existed
lxc-start 20171020040037.850 DEBUG    lxc_conf - conf.c:lxc_fill_autodev:1203 - "/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/random" device already existed
lxc-start 20171020040037.850 DEBUG    lxc_conf - conf.c:lxc_fill_autodev:1203 - "/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/tty" device already existed
lxc-start 20171020040037.850 INFO     lxc_conf - conf.c:lxc_fill_autodev:1230 - populated container /dev
lxc-start 20171020040037.850 DEBUG    lxc_conf - conf.c:lxc_setup_dev_console:1549 - mounted pts device "/dev/pts/4" onto "/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/console"
lxc-start 20171020040037.850 INFO     lxc_utils - utils.c:lxc_mount_proc_if_needed:1773 - I am 1, /proc/self points to "1"
lxc-start 20171020040037.866 DEBUG    lxc_conf - conf.c:setup_rootfs_pivot_root:1088 - pivot_root syscall to '/usr/lib/x86_64-linux-gnu/lxc/rootfs' successful
lxc-start 20171020040037.866 DEBUG    lxc_conf - conf.c:setup_pivot_root:1390 - finished pivot root
lxc-start 20171020040037.866 DEBUG    lxc_conf - conf.c:lxc_setup_devpts:1448 - created dummy "/dev/ptmx" file as bind mount target
lxc-start 20171020040037.866 DEBUG    lxc_conf - conf.c:lxc_setup_devpts:1453 - bind mounted "/dev/pts/ptmx" to "/dev/ptmx"
lxc-start 20171020040037.866 DEBUG    lxc_conf - conf.c:lxc_create_tty:3670 - allocated pty '/dev/pts/0' (11/14)
lxc-start 20171020040037.866 DEBUG    lxc_conf - conf.c:lxc_create_tty:3670 - allocated pty '/dev/pts/1' (15/16)
lxc-start 20171020040037.866 INFO     lxc_conf - conf.c:lxc_create_tty:3681 - tty's configured
lxc-start 20171020040037.866 INFO     lxc_conf - conf.c:setup_tty:1033 - 2 tty(s) has been setup
lxc-start 20171020040037.866 INFO     lxc_conf - conf.c:setup_personality:1489 - set personality to '0x0'
lxc-start 20171020040037.866 DEBUG    lxc_conf - conf.c:setup_caps:2250 - drop capability 'mac_admin' (33)
lxc-start 20171020040037.866 DEBUG    lxc_conf - conf.c:setup_caps:2250 - drop capability 'mac_override' (32)
lxc-start 20171020040037.866 DEBUG    lxc_conf - conf.c:setup_caps:2250 - drop capability 'sys_time' (25)
lxc-start 20171020040037.866 DEBUG    lxc_conf - conf.c:setup_caps:2250 - drop capability 'sys_module' (16)
lxc-start 20171020040037.866 DEBUG    lxc_conf - conf.c:setup_caps:2250 - drop capability 'sys_rawio' (17)
lxc-start 20171020040037.866 DEBUG    lxc_conf - conf.c:setup_caps:2259 - capabilities have been setup
lxc-start 20171020040037.866 NOTICE   lxc_conf - conf.c:lxc_setup:4217 - '105' is setup.
lxc-start 20171020040037.866 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2031 - cgroup 'memory.limit_in_bytes' set to '1073741824'
lxc-start 20171020040037.866 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2031 - cgroup 'memory.memsw.limit_in_bytes' set to '2147483648'
lxc-start 20171020040037.866 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2031 - cgroup 'cpu.shares' set to '1024'
lxc-start 20171020040037.866 DEBUG    lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2031 - cgroup 'cpuset.cpus' set to '5'
lxc-start 20171020040037.866 INFO     lxc_cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2035 - cgroup has been setup
lxc-start 20171020040037.866 INFO     lxc_start - start.c:do_start:836 - Unshared CLONE_NEWCGROUP.
lxc-start 20171020040037.866 INFO     lxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:238 - changed apparmor profile to lxc-container-default-cgns
lxc-start 20171020040037.866 NOTICE   lxc_start - start.c:start:1463 - Exec'ing "/sbin/init".
lxc-start 20171020040037.866 ERROR    lxc_start - start.c:start:1466 - No such file or directory - Failed to exec "/sbin/init".
lxc-start 20171020040037.867 ERROR    lxc_sync - sync.c:__sync_wait:57 - An error occurred in another process (expected sequence number 5)
lxc-start 20171020040037.867 ERROR    lxc_start - start.c:__lxc_start:1381 - Failed to spawn container "105".
lxc-start 20171020040037.867 INFO     lxc_conf - conf.c:run_script_argv:483 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "105", config section "lxc".
lxc-start 20171020040038.368 INFO     lxc_conf - conf.c:run_script_argv:483 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "105", config section "lxc".
lxc-start 20171020040038.724 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newuidmap" does have the setuid bit set.
lxc-start 20171020040038.724 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newgidmap" does have the setuid bit set.
lxc-start 20171020040038.724 DEBUG    lxc_conf - conf.c:lxc_map_ids:3469 - Functional newuidmap and newgidmap binary found.
lxc-start 20171020040038.726 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newuidmap" does have the setuid bit set.
lxc-start 20171020040038.726 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newgidmap" does have the setuid bit set.
lxc-start 20171020040038.726 DEBUG    lxc_conf - conf.c:lxc_map_ids:3469 - Functional newuidmap and newgidmap binary found.
lxc-start 20171020040038.729 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newuidmap" does have the setuid bit set.
lxc-start 20171020040038.729 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newgidmap" does have the setuid bit set.
lxc-start 20171020040038.729 DEBUG    lxc_conf - conf.c:lxc_map_ids:3469 - Functional newuidmap and newgidmap binary found.
lxc-start 20171020040038.731 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newuidmap" does have the setuid bit set.
lxc-start 20171020040038.731 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newgidmap" does have the setuid bit set.
lxc-start 20171020040038.731 DEBUG    lxc_conf - conf.c:lxc_map_ids:3469 - Functional newuidmap and newgidmap binary found.
lxc-start 20171020040038.734 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newuidmap" does have the setuid bit set.
lxc-start 20171020040038.734 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newgidmap" does have the setuid bit set.
lxc-start 20171020040038.734 DEBUG    lxc_conf - conf.c:lxc_map_ids:3469 - Functional newuidmap and newgidmap binary found.
lxc-start 20171020040038.736 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newuidmap" does have the setuid bit set.
lxc-start 20171020040038.736 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newgidmap" does have the setuid bit set.
lxc-start 20171020040038.736 DEBUG    lxc_conf - conf.c:lxc_map_ids:3469 - Functional newuidmap and newgidmap binary found.
lxc-start 20171020040038.739 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newuidmap" does have the setuid bit set.
lxc-start 20171020040038.739 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newgidmap" does have the setuid bit set.
lxc-start 20171020040038.739 DEBUG    lxc_conf - conf.c:lxc_map_ids:3469 - Functional newuidmap and newgidmap binary found.
lxc-start 20171020040038.741 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newuidmap" does have the setuid bit set.
lxc-start 20171020040038.741 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newgidmap" does have the setuid bit set.
lxc-start 20171020040038.741 DEBUG    lxc_conf - conf.c:lxc_map_ids:3469 - Functional newuidmap and newgidmap binary found.
lxc-start 20171020040038.743 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newuidmap" does have the setuid bit set.
lxc-start 20171020040038.743 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newgidmap" does have the setuid bit set.
lxc-start 20171020040038.743 DEBUG    lxc_conf - conf.c:lxc_map_ids:3469 - Functional newuidmap and newgidmap binary found.
lxc-start 20171020040038.746 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newuidmap" does have the setuid bit set.
lxc-start 20171020040038.746 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newgidmap" does have the setuid bit set.
lxc-start 20171020040038.746 DEBUG    lxc_conf - conf.c:lxc_map_ids:3469 - Functional newuidmap and newgidmap binary found.
lxc-start 20171020040038.748 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newuidmap" does have the setuid bit set.
lxc-start 20171020040038.748 DEBUG    lxc_conf - conf.c:idmaptool_on_path_and_privileged:3408 - The binary "/usr/bin/newgidmap" does have the setuid bit set.
lxc-start 20171020040038.748 DEBUG    lxc_conf - conf.c:lxc_map_ids:3469 - Functional newuidmap and newgidmap binary found.
lxc-start 20171020040038.751 ERROR    lxc_start_ui - tools/lxc_start.c:main:366 - The container failed to start.
lxc-start 20171020040038.751 ERROR    lxc_start_ui - tools/lxc_start.c:main:370 - Additional information can be obtained by setting the --logfile and --logpriority options.
 
lxc-start 20171020040037.866 NOTICE lxc_start - start.c:start:1463 - Exec'ing "/sbin/init". lxc-start 20171020040037.866 ERROR lxc_start - start.c:start:1466 - No such file or directory - Failed to exec "/sbin/init".
your template seems to be missing an /sbin/init ?
 
Yeah, but it's not really. Where '/tmp/test' is the install path used for debootstrap (i.e., the contents of the template):

Code:
$ ls -l /tmp/test/sbin/init
lrwxrwxrwx 1 user users 29 Mar 28  2017 ./test/sbin/init -> /tmp/test/lib/systemd/systemd

$ ls -l /tmp/test/lib/systemd/systemd
-rwxr-xr-x 1 user users 1.1M Mar 28  2017 /tmp/test/lib/systemd/systemd

I verified those made it into the template .tgz

Thanks.
 
This confuses me. These commands & outputs seem to have been pasted together wrongly. You run `ls` on /tmp/test/sbin/init but it shows ./test/sbin/init.In addition to that the symlink is an absolute path that includes the /tmp/test folder which I'm pretty sure doesn't show up in the template.

It would be helpful to see the unmodified output of the following command
Code:
$ tar tvf /path/to/the.tgz | grep sbin/init
This should be run on the template you use when creating the container with `pct` (or the pve gui)
 
This confuses me. These commands & outputs seem to have been pasted together wrongly. You run `ls` on /tmp/test/sbin/init but it shows ./test/sbin/init.In addition to that the symlink is an absolute path that includes the /tmp/test folder which I'm pretty sure doesn't show up in the template.


Bleh, sorry. I botched up the attempt to clarify the output by manually changing the relative paths to full. Checking the actual full paths:
Code:
$ ls -l /tmp/test/sbin/init
lrwxrwxrwx 1 user users 29 Mar 28  2017 /tmp/test/sbin/init -> /tmp/test/lib/systemd/systemd

$ ls -l /tmp/test/lib/systemd/systemd
-rwxr-xr-x 1 user users 1.1M Mar 28  2017 /tmp/test/lib/systemd/systemd

Where '/tmp/test' is the chroot directory where debootstrap installed to.

Further, if I chroot into /tmp/test:
Code:
# ls -l /sbin/init
lrwxrwxrwx 1 root root 20 Mar 28  2017 /sbin/init -> /lib/systemd/systemd

# ls -l /lib/systemd/systemd
-rwxr-xr-x 1 root root 1141448 Mar 28  2017 /lib/systemd/systemd

So it seems OK...

It would be helpful to see the unmodified output of the following command
Code:
$ tar tvf /path/to/the.tgz | grep sbin/init
This should be run on the template you use when creating the container with `pct` (or the pve gui)


Huh, now it gets interesting:
Code:
$ tar -tvf zesty-lxc.tar.gz | grep sbin/init
lrwxrwxrwx user/users       0 2017-03-28 08:59 sbin/init -> /tmp/test/lib/systemd/systemd

So that looks like that could be mucking things up. I'll see if I can get it straightened out.
 
I ran into this thread after facing the exact same problem (Failed to exec "/sbin/init" on container creation after creating stretch image with debootstrap).


To follow up, once I got the tarball creation corrected all's well. Thanks for the pointers.
Could you clarify what changes did you make exactly in the tarball creation to fix the issue?
 
For me, this was due to the fact that the container in lxc used a link to /lib/systemd/systemd since the lxc container is located in the host file system directory.
When restoring in proxmox, the container gets its own file system in which the path specified in the link is missing.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!