Starting impossible of container under Ubuntu 17.04

M

mateofix

Member
Jan 14, 2017
8
0
6
27
Hello,

I migred my container under Ubuntu 16.10 to Ubuntu 17.04, but impossible of start my container, i this message :

Job for lxc@202.service failed. See 'systemctl status lxc@202.service' and 'journalctl -xn' for details.​
TASK ERROR: command 'systemctl start lxc@202' failed: exit code 1​

systemctl status lxc@202.service
● lxc@202.service - LXC Container: 202
Loaded: loaded (/lib/systemd/system/lxc@.service; disabled)
Drop-In: /usr/lib/systemd/system/lxc@.service.d
└─pve-reboot.conf
Active: failed (Result: exit-code) since lun. 2017-05-01 19:24:34 CEST; 10min ago
Docs: man:lxc-start
man:lxc
Process: 22918 ExecStopPost=/usr/share/lxc/lxc-pve-reboot-trigger %i (code=exited, status=0/SUCCESS)
Process: 24114 ExecStart=/usr/bin/lxc-start -n %i (code=exited, status=1/FAILURE)
Main PID: 22066 (code=exited, status=1/FAILURE)

mai 01 19:24:34 Scarif lxc-start[24114]: lxc-start: tools/lxc_start.c: main: 366 The container failed to start.
mai 01 19:24:34 Scarif lxc-start[24114]: lxc-start: tools/lxc_start.c: main: 368 To get more details, run the container in foreground mode.
mai 01 19:24:34 Scarif lxc-start[24114]: lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options.
mai 01 19:24:34 Scarif systemd[1]: lxc@202.service: control process exited, code=exited status=1
mai 01 19:24:34 Scarif systemd[1]: Failed to start LXC Container: 202.
mai 01 19:24:34 Scarif systemd[1]: Unit lxc@202.service entered failed state.​

Proxmox VE 4.4-13/7ea56165 at Kimsufi

Thanks for your help
 
When will it be released on a stable release? There is a quick fix to allow Ubuntu 17.04 on 4.4 version?
 
You must log in or register to reply here.
Top Bottom