PCT CREATE doesn't start on PVE 5.1

[Arthur]

Good evening.

This weird behavior is happening after installing a fresh new server on PVE 5.1

Command to produce the error:

pct create 100 local:YOUR_TEMPLATE.tar.gz --cores 1 --hostname test --memory 2048 --net0 name=eth0,bridge=vmbr0,ip=dhcp --onboot 0 --rootfs local:20 --swap 512

Nov 09 03:06:07 fender systemd-udevd[3879]: Could not generate persistent MAC address for vethBFAGET: No such file or directory
Nov 09 03:06:07 fender kernel: IPv6: ADDRCONF(NETDEV_UP): veth100i0: link is not ready
Nov 09 03:06:07 fender lxc-start[3861]: lxc-start: 100: lxccontainer.c: wait_on_daemonized_start: 760 Received container state "STOPPING" instead of "RU
Nov 09 03:06:07 fender lxc-start[3861]: lxc-start: 100: tools/lxc_start.c: main: 368 The container failed to start.
Nov 09 03:06:07 fender lxc-start[3861]: lxc-start: 100: tools/lxc_start.c: main: 370 To get more details, run the container in foreground mode.
Nov 09 03:06:07 fender lxc-start[3861]: lxc-start: 100: tools/lxc_start.c: main: 372 Additional information can be obtained by setting the --logfile and
Nov 09 03:06:07 fender systemd[1]: pve-container@100.service: Control process exited, code=exited status=1
Nov 09 03:06:07 fender pvedaemon[15634]: unable to get PID for CT 100 (not running?)
Nov 09 03:06:07 fender systemd[1]: pve-container@100.service: Killing process 3863 (lxc-start) with signal SIGKILL.
Nov 09 03:06:07 fender systemd[1]: pve-container@100.service: Killing process 3909 (sh) with signal SIGKILL.
Nov 09 03:06:08 fender systemd[1]: Failed to start PVE LXC Container: 100.
-- Subject: Unit pve-container@100.service has failed

Is there any very apparent mistake I am committing when calling this command in this new version?

Best.

 

[Arthur]

I also tried running this container in foreground mode as suggested in the logs by running the following command:

lxc-start -n 100 --logfile debug --logpriority TRACE


This was the output of the debug file:


lxc-start 100 20171109083420.414 ERROR lxc_network - network.c:lxc_create_network_priv:2401 - Failed to create network device
lxc-start 100 20171109083420.414 ERROR lxc_start - start.c:lxc_spawn:1185 - Failed to create the network.
lxc-start 100 20171109083420.414 ERROR lxc_start - start.c:__lxc_start:1469 - Failed to spawn container "100".

 

[Arthur]

I also tried running this container in foreground mode as suggested in the logs by running the following command:

lxc-start -n 100 --logfile debug --logpriority TRACE


This was the output of the debug file:


lxc-start 100 20171109083420.414 ERROR lxc_network - network.c:lxc_create_network_priv:2401 - Failed to create network device
lxc-start 100 20171109083420.414 ERROR lxc_start - start.c:lxc_spawn:1185 - Failed to create the network.
lxc-start 100 20171109083420.414 ERROR lxc_start - start.c:__lxc_start:1469 - Failed to spawn container "100".

Ok, this was entirely my fault. Reference for people who run into this in the future. We currently use the hypervisor where proxmox is installed also to act as a dhcp server to the VMs. This allows other apps to define which IP each vm would take.

isc-dhcp-server needs to be listening in the vmbr0 interface, otherwise LXC won't be able to pick an ip from the allocation table and thus failing to start.