Ubuntu 15.04 template

D

dragon2611

Renowned Member
Jul 2, 2010
93
9
73
I'm not sure if it's something in my setup or if the Ubuntu 15.04 lxc template is broken, the containers create ok but when you start them they sit there using a few MB of ram and nothing else happens,

Nothing at all on the console and also no DHCP occurs either.

Debian 8 and Ubuntu 14.04 based containers seem to work fine so my LXC support is working.
 
works here. make sure you run very latest 4.0 beta and try again.
 
Hmm I wonder if I've broken apparmor when adding NFS to the exceptions

: type=1400 audit(1443957514.320:176): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default" name="/sys/fs/cgroup/" pid=14926 comm="systemd" flags="ro, nosuid, nodev, noexec, remount, strictatime"
Click to expand...

Weird thing is it's specifically the 15.04 container that causes that, the 14.04 image works perfectly even if I create a new container for it.
 
15.04 template is using systemd, 14.04 is not using systemd - maybe this hint helps for debugging.
 
Code: 
Oct  4 14:56:56 pve kernel: [56775.890084] device veth101i0 entered promiscuous modeOct  4 14:56:58 pve lxcfs[1728]: call to list_children (name=systemd:/) failed: invalid request
Oct  4 14:56:58 pve lxcfs[1728]: call to list_children (name=systemd:/) failed: invalid request
Oct  4 14:56:58 pve lxcfs[1728]: call to list_children (name=systemd:/) failed: invalid request
Oct  4 14:56:58 pve lxcfs[1728]: call to list_children (name=systemd:/) failed: invalid request
Oct  4 14:56:58 pve lxcfs[1728]: call to list_children (name=systemd:/) failed: invalid request
Oct  4 14:57:20 pve pvedaemon[2401]: <root@pam> starting task UPID:pve:00003058:005699AF:56113040:vzstop:101:root@pam:
Oct  4 14:57:20 pve pvedaemon[12376]: stopping CT 101: UPID:pve:00003058:005699AF:56113040:vzstop:101:root@pam:
Oct  4 14:57:21 pve pvedaemon[31872]: command 'lxc-attach -n 101 -- df -P -B 1 /' failed: exit code 1
Oct  4 14:57:25 pve pvedaemon[2401]: <root@pam> starting task UPID:pve:000030AF:00569B9A:56113045:vzstart:101:root@pam:
Oct  4 14:57:25 pve pvedaemon[12463]: starting CT 101: UPID:pve:000030AF:00569B9A:56113045:vzstart:101:root@pam:
Oct  4 14:57:26 pve kernel: [56805.740795] IPv6: ADDRCONF(NETDEV_UP): veth101i0: link is not ready
Oct  4 14:57:27 pve pvedaemon[31872]: command 'lxc-attach -n 101 -- df -P -B 1 /' failed: got timeout
Oct  4 14:57:27 pve pvedaemon[31872]: Use of uninitialized value in subtraction (-) at /usr/share/perl5/PVE/LXC.pm line 811.
Oct  4 14:57:27 pve pvedaemon[31872]: Use of uninitialized value in subtraction (-) at /usr/share/perl5/PVE/LXC.pm line 811.
Oct  4 14:57:27 pve kernel: [56806.849434] device veth101i0 entered promiscuous mode
Oct  4 14:57:29 pve lxcfs[1728]: call to list_children (name=systemd:/) failed: invalid request
Oct  4 14:57:29 pve lxcfs[1728]: call to list_children (name=systemd:/) failed: invalid request
Oct  4 14:57:29 pve lxcfs[1728]: call to list_children (name=systemd:/) failed: invalid request
Oct  4 14:57:29 pve lxcfs[1728]: call to list_children (name=systemd:/) failed: invalid request
Oct  4 14:57:29 pve lxcfs[1728]: call to list_children (name=systemd:/) failed: invalid request
Not sure if it's any use but that gets logged to /var/log/syslog on the host when trying to start the ubuntu 15.04 container.
 
Hmm it seems the old IT fix resolved it (Have you tried turning it off and then on again), rebooted the proxmox host and now it's starting.
 
You must log in or register to reply here.
Top Bottom