[lxc-users] Cannot start network: Failed to attach
Hi,
this mailing list seems to be appropriate for beginners questions like
the following. Hope, that's the case.
I am running a CentOS 6.7 VM on VirtualBox with LXC 1.0.8 installed
from the EPEL repository. I am creating an LXC container, but cannot
start it, because some problems with the network (see below). Most
likely, my network configuration is not correct. ifconfig shows three
interfaces to be present ("eth0", "eth1", and "lo").
What might be wrong? Or, what to try next?
Thanks,
Jochen
[jwi@lxc ~]$ sudo cat /etc/lxc/lxc-usernet
jwi eth0 lxcbr0 10
jwi@lxc ~]$ sudo rm -rf /var/lib/lxc/centos6/
[sudo] password for jwi:
[jwi@lxc ~]$ sudo lxc-create -t download -n centos6 -- -d centos -r 6 -a amd64
Using image from local cache
Unpacking the rootfs
---
You just created a CentOS container (release=6, arch=amd64, variant=default)
To enable sshd, run: yum install openssh-server
For security reason, container images ship without user accounts
and without a root password.
Use lxc-attach or chroot directly into the rootfs to set a root password
or create user accounts.
[jwi@lxc ~]$ sudo lxc-start -n centos6
lxc-start: conf.c: instantiate_veth: 3105 failed to attach
'veth47FB4Q' to the bridge 'virbr0': No such device
lxc-start: conf.c: lxc_create_network: 3388 failed to create netdev
lxc-start: start.c: lxc_spawn: 841 failed to create the network
lxc-start: start.c: __lxc_start: 1100 failed to spawn 'centos6'
lxc-start: lxc_start.c: main: 341 The container failed to start.
lxc-start: lxc_start.c: main: 345 Additional information can be
obtained by setting the --logfile and --logpriority options.
--
The next time you hear: "Don't reinvent the wheel!"
http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] LXD Debian/jessie image autostart fail
I just have had disappointment with debian since they started using systemd
and this is what caused the problem.
On Feb 23, 2016 09:39, "Jorge Ventura"
wrote:
> Hi,
> I am trying to autostart the image debian/jessie/amd64 using LXD
> 2.0.0.beta3 under Gentoo but for any reason it doesn't work.
>
> After boot, if I restart the LXD service, it works but it doesn't after
> reboot.
>
> name: rem-devel
> profiles:
> - default
> config:
> boot.autostart: "true"
> volatile.base_image:
> 0d07f11f3f2a0804f501967d278d72a8122b1ec49f01aae4483a41fd9fb546f3
> volatile.eth0.hwaddr: 00:16:3e:0c:fe:0d
> volatile.eth0.name: eth0
> volatile.last_state.idmap:
> '[{"Isuid":true,"Isgid":false,"Hostid":100,"Nsid":0,"Maprange":10},{"Isuid":false,"Isgid":true,"Hostid":100,"Nsid":0,"Maprange":10}]'
> devices:
> root:
> path: /
> type: disk
> ephemeral: false
>
> --
>
> J. Ventura
>
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] Cannot start network: Failed to attach
On Wed, Feb 24, 2016 at 3:09 PM, Jochen Wiedmann
wrote:
> Hi,
>
> this mailing list seems to be appropriate for beginners questions like
> the following. Hope, that's the case.
>
> I am running a CentOS 6.7 VM on VirtualBox with LXC 1.0.8 installed
> from the EPEL repository. I am creating an LXC container, but cannot
You're missing a lot by sticking with c6. Especially if you stick with
the default kernel.
> start it, because some problems with the network (see below). Most
> likely, my network configuration is not correct. ifconfig shows three
> interfaces to be present ("eth0", "eth1", and "lo").
>
> What might be wrong? Or, what to try next?
> [jwi@lxc ~]$ sudo cat /etc/lxc/lxc-usernet
> jwi eth0 lxcbr0 10
That file is irrelevant. It's only used for unprivileged containers,
which won't work on c6 since it needs kernel capabilities that's only
available in newer kernels.
> 'veth47FB4Q' to the bridge 'virbr0': No such device
Does virbr0 exist?
It's usually created by libvirt (which also sets up things like
dnsmasq and iptables rules). You could also create your own bridge
manually (if you know how) and use that for lxc.
--
Fajar
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] Cannot start network: Failed to attach
On Wed, Feb 24, 2016 at 9:49 AM, Fajar A. Nugraha wrote: > You're missing a lot by sticking with c6. Especially if you stick with > the default kernel. What alternative are you suggesting? This is a VM, so I'm flexible. > Does virbr0 exist? > > It's usually created by libvirt (which also sets up things like > dnsmasq and iptables rules). You could also create your own bridge > manually (if you know how) and use that for lxc. Meaning: I've got to install libvirt, right? Thanks, Jochen -- The next time you hear: "Don't reinvent the wheel!" http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] Cannot start network: Failed to attach
On Wed, Feb 24, 2016 at 9:59 AM, Jochen Wiedmann wrote: > On Wed, Feb 24, 2016 at 9:49 AM, Fajar A. Nugraha wrote: >> Does virbr0 exist? >> >> It's usually created by libvirt (which also sets up things like >> dnsmasq and iptables rules). You could also create your own bridge >> manually (if you know how) and use that for lxc. > > Meaning: I've got to install libvirt, right? Thanks! Installing libvirt fixed my problem. Jochen -- The next time you hear: "Don't reinvent the wheel!" http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
[lxc-users] lxd images error
Hello i have a problem with lxd this morning : lxc list images: error: not found However images.linuxcontainers.org is correctly setting lxc remote list +-+-++ | NAME | URL | PUBLIC | +-+-++ | images | https://images.linuxcontainers.org:8443 | YES | | local (default) | unix:// | NO | +-+-++ I'm on ubuntu wily. lxd --version 2.0.0.beta3 ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] Cannot start network: Failed to attach
On Wed, Feb 24, 2016 at 3:59 PM, Jochen Wiedmann wrote: > On Wed, Feb 24, 2016 at 9:49 AM, Fajar A. Nugraha wrote: > >> You're missing a lot by sticking with c6. Especially if you stick with >> the default kernel. > > What alternative are you suggesting? This is a VM, so I'm flexible. Well, https://linuxcontainers.org/ says "Project sponsored by Canonical Ltd". And there's also http://blog.dustinkirkland.com/2016/02/zfs-is-fs-for-containers-in-ubuntu-1604.html Anything with recent-enough kernel should work. I like ubuntu since it's easiest to get lxc working there (obviously), but any distro with recent-enough kernel should be able to support most newer features (e.g. unprivileged containers, additional security using apparmor/seccomp). A c6 host should be able to run sysvinit and upstart-based priviliged containers (i.e. root in container has the same id as root in host), but it won't provide the usual security and restriction that you're used to in VMs (for example, the host might set CPU/memory limit for a container, but a privileged host would be able to reset that limit). And you won't be able to run systemd-based containers either (those need lxcfs) As for the bridge, newer lxc installations (e.g. 1.1.5 or 2 beta) will create lxcbr0 which behaves similar to virbr0. In your case, the easy way out is to install libvirt (which you did). If you had used ubuntu, you'd already have lxcbr0 automagically configured ready to use. -- Fajar ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] Cannot start network: Failed to attach
On Wed, Feb 24, 2016 at 11:59 AM, Fajar A. Nugraha wrote: >> What alternative are you suggesting? This is a VM, so I'm flexible. > > > Well, https://linuxcontainers.org/ says "Project sponsored by > Canonical Ltd". And there's also > http://blog.dustinkirkland.com/2016/02/zfs-is-fs-for-containers-in-ubuntu-1604.html Okay, I'll consider giving Ubuntu a try. Thanks again, Jochen ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
[lxc-users] Antw: Re: Cannot start network: Failed to attach
>>> Jochen Wiedmann schrieb am 2/24/2016 um 10:06 AM in Nachricht : > On Wed, Feb 24, 2016 at 9:59 AM, Jochen Wiedmann > wrote: > > On Wed, Feb 24, 2016 at 9:49 AM, Fajar A. Nugraha wrote: > > >> Does virbr0 exist? > >> > >> It's usually created by libvirt (which also sets up things like > >> dnsmasq and iptables rules). You could also create your own bridge > >> manually (if you know how) and use that for lxc. > > > > Meaning: I've got to install libvirt, right? > > Thanks! Installing libvirt fixed my problem. > > Jochen Hello Jochen, I think next time it should be enough to install bridge-utils und to create the bridge you need (virbr, you can create it via /etc/sysconfig/network-scripts/ifcfg-virbr0). Thomas -- Thomas Belián Fachhochschule Erfurt Fakultät Gebäudetechnik und Informatik Fachrichtung Angewandte Informatik Postfach 45 01 55, 99051 Erfurt Telefon: 0361 6700 - 647 Telefax: 0361 6700 - 643 E-Mail: thomas.bel...@fh-erfurt.de Web: https://ai.fh-erfurt.de ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
[lxc-users] lxd_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb failed to update
Hi! I launched these updates this morning on a test server: lxd_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb lxd-client_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb lxd-client passed but lxd failed. Here are the first error message I got: Do you want to continue? [Y/n] Get:1 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu/ trusty/main lxd amd64 2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1 [3,994 kB] Get:2 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu/ trusty/main lxd-client amd64 2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1 [1,814 kB] Fetched 5,807 kB in 2s (2,003 kB/s) Preconfiguring packages ... (Reading database ... 76200 files and directories currently installed.) Preparing to unpack .../lxd_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb ... lxd stop/waiting postinst called with unknown argument `upgrade' dpkg: error processing archive /var/cache/apt/archives/lxd_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb (--unpack): subprocess new pre-installation script returned error exit status 1 lxd start/running, process 24909 Preparing to unpack .../lxd-client_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb ... Unpacking lxd-client (2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1) over (2.0.0~beta3-0ubuntu4~ubuntu14.04.1~ppa1) ... Processing triggers for man-db (2.6.7.1-1ubuntu1) ... Errors were encountered while processing: /var/cache/apt/archives/lxd_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) So I downloaded the ded package and tried to install it manually. Here's what I got: # dpkg -i lxd_2.0.0~beta4-0ubuntu2_amd64.deb (Reading database ... 76200 files and directories currently installed.) Preparing to unpack lxd_2.0.0~beta4-0ubuntu2_amd64.deb ... lxd stop/waiting Unpacking lxd (2.0.0~beta4-0ubuntu2) over (2.0.0~beta3-0ubuntu4~ubuntu14.04.1~ppa1) ... dpkg: dependency problems prevent configuration of lxd: lxd depends on init-system-helpers (>= 1.18~); however: Version of init-system-helpers on system is 1.14. lxd depends on lsb-base (>= 4.1+Debian11ubuntu7); however: Version of lsb-base on system is 4.1+Debian11ubuntu6. dpkg: error processing package lxd (--install): dependency problems - leaving unconfigured Processing triggers for ureadahead (0.100.0-16) ... Processing triggers for man-db (2.6.7.1-1ubuntu1) ... Errors were encountered while processing: lxd After many many tries with dependancies, I got everything up and running. Luckily for me this happened on a test server. Thanks to all the team for the excellent work you do! Michel = ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
[lxc-users] lxd_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb failed to update
Hi! I launched these updates this morning on a test server: lxd_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb lxd-client_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb lxd-client passed but lxd failed. Here are the first error message I got: Do you want to continue? [Y/n] Get:1 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu/ trusty/main lxd amd64 2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1 [3,994 kB] Get:2 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu/ trusty/main lxd-client amd64 2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1 [1,814 kB] Fetched 5,807 kB in 2s (2,003 kB/s) Preconfiguring packages ... (Reading database ... 76200 files and directories currently installed.) Preparing to unpack .../lxd_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb ... lxd stop/waiting postinst called with unknown argument `upgrade' dpkg: error processing archive /var/cache/apt/archives/lxd_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb (--unpack): subprocess new pre-installation script returned error exit status 1 lxd start/running, process 24909 Preparing to unpack .../lxd-client_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb ... Unpacking lxd-client (2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1) over (2.0.0~beta3-0ubuntu4~ubuntu14.04.1~ppa1) ... Processing triggers for man-db (2.6.7.1-1ubuntu1) ... Errors were encountered while processing: /var/cache/apt/archives/lxd_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) So I downloaded the ded package and tried to install it manually. Here's what I got: # dpkg -i lxd_2.0.0~beta4-0ubuntu2_amd64.deb (Reading database ... 76200 files and directories currently installed.) Preparing to unpack lxd_2.0.0~beta4-0ubuntu2_amd64.deb ... lxd stop/waiting Unpacking lxd (2.0.0~beta4-0ubuntu2) over (2.0.0~beta3-0ubuntu4~ubuntu14.04.1~ppa1) ... dpkg: dependency problems prevent configuration of lxd: lxd depends on init-system-helpers (>= 1.18~); however: Version of init-system-helpers on system is 1.14. lxd depends on lsb-base (>= 4.1+Debian11ubuntu7); however: Version of lsb-base on system is 4.1+Debian11ubuntu6. dpkg: error processing package lxd (--install): dependency problems - leaving unconfigured Processing triggers for ureadahead (0.100.0-16) ... Processing triggers for man-db (2.6.7.1-1ubuntu1) ... Errors were encountered while processing: lxd After many many tries with dependancies, I got everything up and running. Luckily for me this happened on a test server. Thanks to all the team for the excellent work you do! Michel = ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] lxd_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb failed to update
Hi, Sorry about that, I indeed screwed up the preinst for the upgrade case and only tested a clean install (not upgrade)... Anyway, Martin Pitt was kind enough to fix it pretty quickly in the Ubuntu archive which then automatically made its way to all the PPAs. On Wed, Feb 24, 2016 at 07:15:26AM -0500, Michel Dubé wrote: > Hi! > > I launched these updates this morning on a test server: > > lxd_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb > lxd-client_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb > > lxd-client passed but lxd failed. > > Here are the first error message I got: > > Do you want to continue? [Y/n] > Get:1 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu/ trusty/main > lxd amd64 2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1 [3,994 kB] > Get:2 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu/ trusty/main > lxd-client amd64 2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1 [1,814 kB] > Fetched 5,807 kB in 2s (2,003 kB/s) > Preconfiguring packages ... > (Reading database ... 76200 files and directories currently installed.) > Preparing to unpack > .../lxd_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb ... > lxd stop/waiting > postinst called with unknown argument `upgrade' > dpkg: error processing archive > /var/cache/apt/archives/lxd_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb > (--unpack): > subprocess new pre-installation script returned error exit status 1 > lxd start/running, process 24909 > Preparing to unpack > .../lxd-client_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb ... > Unpacking lxd-client (2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1) over > (2.0.0~beta3-0ubuntu4~ubuntu14.04.1~ppa1) ... > Processing triggers for man-db (2.6.7.1-1ubuntu1) ... > Errors were encountered while processing: > /var/cache/apt/archives/lxd_2.0.0~beta4-0ubuntu1~ubuntu14.04.1~ppa1_amd64.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > > So I downloaded the ded package and tried to install it manually. Here's > what I got: > > # dpkg -i lxd_2.0.0~beta4-0ubuntu2_amd64.deb > (Reading database ... 76200 files and directories currently installed.) > Preparing to unpack lxd_2.0.0~beta4-0ubuntu2_amd64.deb ... > lxd stop/waiting > Unpacking lxd (2.0.0~beta4-0ubuntu2) over > (2.0.0~beta3-0ubuntu4~ubuntu14.04.1~ppa1) ... > dpkg: dependency problems prevent configuration of lxd: > lxd depends on init-system-helpers (>= 1.18~); however: > Version of init-system-helpers on system is 1.14. > lxd depends on lsb-base (>= 4.1+Debian11ubuntu7); however: > Version of lsb-base on system is 4.1+Debian11ubuntu6. > > dpkg: error processing package lxd (--install): > dependency problems - leaving unconfigured > Processing triggers for ureadahead (0.100.0-16) ... > Processing triggers for man-db (2.6.7.1-1ubuntu1) ... > Errors were encountered while processing: > lxd > > After many many tries with dependancies, I got everything up and running. > Luckily for me this happened on a test server. > > Thanks to all the team for the excellent work you do! > > Michel > > = > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users -- Stéphane Graber Ubuntu developer http://www.ubuntu.com signature.asc Description: PGP signature ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
[lxc-users] any way to configure lxd as a hypervisor of openstack juno or kilo release in ubuntu 14.04? and how to install and configure LXD for openstack?
Hi^^ I want to configure lxd as a hypervisor of openstack juno or kilo release in ubuntu 14.04. Because http://docs.openstack.org provides only openstack Installation guide for ubuntu 14.04. So I can configure openstack in only ubuntu 14.04. I am afraid that configuration need to be changed when configured in 15.04 or later version anyway... I have found some information below, but this information is not enough kind about configuration lxd-driver in openstack. I should make it. please help me thanks in advance. 1. reference : https://linuxcontainers.org/lxd/getting-started-openstack/ ubuntu 15.10, in openstack compute node, Nova LXD driver install (there is no openstack release vesion metioned) how to : # apt-get install nova-compute-lxd # usermod -G lxd -a nova # service nova-compute restart is that all?? --->* Q1)*no need for setting in /etc/nova/nova-compute.conf like a "virt_type = qemu" or "virt_type = lxc" ??? ---> *Q2)*what minimum release of openstack support LXD driver? lxd can be configured in openstack juno ??? 2. reference : https://insights.ubuntu.com/2015/05/06/introduction-to-nova-compute-lxd/ (there is no ubuntu version, openstack release version metioned) how to : # git clone https://github.com/lxc/nova-compute-lxd After installed source and configure. (there is no explation about "how to installed source and configure", So I don't know how to do) and then, compute_driver=nclxd.nova.virt.lxd.LXDDriver in /etc/nova/nova.conf # service nova-compute restart or in ubuntu 15.04, # apt-get install nova-compute-lxd and configure LXD (there is no explanation about "how to configure")) ---> *Q1*) If not complecated, anyone can let me know lxd source installation and configuration method for openstack and is there minimum ubuntu version for source installation and configuration? 3. I found installation information, In ubuntu 14.04, configuration for standalone LXD. sudo add-apt-repository ppa:ubuntu-lxc/lxd-stable sudo apt-get update sudo apt-get install lxd In ubuntu 14.04, configuration for openstack LXD # add-apt-repository cloud-archive:juno # apt-get update # apt-get install nova-compute-flex ---> *Q1*) So, In my guess, standloane LXD configuration may be right, however I am not sure.for openstack LXD confugration? , how about this way? Is it possible?? ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
[lxc-users] all lxc containers gone after update?
Looks all my lxc containers are gone after some recent update: # lxc-ls -f (no output at all) # lxc-attach -n somecontainer Error: container somecontainer is not defined Is there a way to fix? # dpkg -l|grep lxc ii liblxc1 2.0.0~rc2-0ubuntu2~ubuntu14.04.1~ppa1 amd64Linux Containers userspace tools (library) ii lxc 2.0.0~rc2-0ubuntu2~ubuntu14.04.1~ppa1 all Transitional package for lxc1 ii lxc-common 2.0.0~rc2-0ubuntu2~ubuntu14.04.1~ppa1 amd64Linux Containers userspace tools (common tools) ii lxc-templates 2.0.0~rc2-0ubuntu2~ubuntu14.04.1~ppa1 amd64Linux Containers userspace tools (templates) ii lxc1 2.0.0~rc2-0ubuntu2~ubuntu14.04.1~ppa1 amd64Linux Containers userspace tools ii lxcfs 2.0.0~beta2-0ubuntu1~ubuntu14.04.1~ppa1 amd64FUSE based filesystem for LXC ii python3-lxc 2.0.0~rc2-0ubuntu2~ubuntu14.04.1~ppa1 amd64Linux Containers userspace tools (Python 3.x bindings) Tomasz Chmielewski http://wpkg.org ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] all lxc containers gone after update?
On 2016-02-25 11:15, Tomasz Chmielewski wrote: Looks all my lxc containers are gone after some recent update: # lxc-ls -f (no output at all) # lxc-attach -n somecontainer Error: container somecontainer is not defined FYI, my /var/lib/lxc was a symbolic link to /some/other/mountpoint. Looks like the upgrade removed that symbolic link and created an empty /var/lib/lxc directory. Restoring the symbolic link "fixed" this. Is it expected that /var/lib/lxc is removed when lxc is updated? Tomasz Chmielewski http://wpkg.org ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] all lxc containers gone after update?
On Thu, Feb 25, 2016 at 11:19:28AM +0900, Tomasz Chmielewski wrote: > On 2016-02-25 11:15, Tomasz Chmielewski wrote: > >Looks all my lxc containers are gone after some recent update: > > > ># lxc-ls -f > > > >(no output at all) > > > ># lxc-attach -n somecontainer > >Error: container somecontainer is not defined > > FYI, my /var/lib/lxc was a symbolic link to /some/other/mountpoint. > > Looks like the upgrade removed that symbolic link and created an empty > /var/lib/lxc directory. > > Restoring the symbolic link "fixed" this. > > > Is it expected that /var/lib/lxc is removed when lxc is updated? It's not expected, no. But it most likely happened due to our package split. The owner of /var/lib/lxc changed from the lxc package to the lxc1 package which most likely caused dpkg to reset it to the default permissions (which is a directory set with root:root and 0700 mode). > > > Tomasz Chmielewski > http://wpkg.org -- Stéphane Graber Ubuntu developer http://www.ubuntu.com signature.asc Description: PGP signature ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
[lxc-users] /sbin/init failure
Using latest freshly reinstalled xenial host and containers with 2.0.0~beta4-0ubuntu4 which got the packages installed after removing everything and starting again but I've had this problem for a couple of weeks now... ~ lxc image list ++--++++-+--+ | ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION | ARCH | SIZE | UPLOAD DATE | ++--++++-+--+ | xenial | 0594dbb54ade | no | Ubuntu xenial (amd64) (20160218_03:49) | x86_64 | 64.87MB | Feb 25, 2016 at 1:45am (UTC) | ++--++++-+--+ ~ lxc image copy upstream:/ubuntu/xenial/amd64 local: --alias=xenial ~ lxc launch xenial gc3 Creating gc3 Starting gc3 ~ lx +--+-+--+--++---+ | NAME | STATE | IPV4 | IPV6 |TYPE| SNAPSHOTS | +--+-+--+--++---+ | gc3 | RUNNING | | | PERSISTENT | 0 | +--+-+--+--++---+ ~ lxc exec gc3 bash root@gc3:~# ps aux USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.0 36544 3952 ?Ss 03:27 0:00 /sbin/init root25 0.0 0.0 18220 3160 ?Ss 03:29 0:00 bash root36 0.0 0.0 34412 2804 ?R+ 03:29 0:00 ps aux root@gc3:~# exit And of course I have to use "lxc stop gc3 --force" to get it to stop. Any idea why /sbin/init is not kicking off the rest of the startup procedure? ~ ps auxxww | grep -v grep | grep lx root 9621 0.0 0.0 234760 3744 ?Ssl 11:41 0:00 /usr/bin/lxcfs /var/lib/lxcfs/ root 10264 0.0 0.1 960888 25700 ?Ssl 11:41 0:05 /usr/bin/lxd --group lxd --logfile=/var/log/lxd/lxd.log root 11567 0.0 0.0 7 4552 ?Ss 13:38 0:00 [lxc monitor] /var/lib/lxd/containers gc3 ~ tail /var/log/lxd/lxd.log t=2016-02-25T13:38:42+1000 lvl=info msg=handling method=GET url=/1.0 ip=@ t=2016-02-25T13:38:42+1000 lvl=info msg=handling method=GET url=/1.0/containers/gc3 ip=@ t=2016-02-25T13:38:42+1000 lvl=info msg=handling url=/1.0/containers/gc3/state ip=@ method=GET t=2016-02-25T13:38:42+1000 lvl=info msg=handling url="/1.0/containers/gc3/snapshots?recursion=1" ip=@ method=GET t=2016-02-25T13:38:42+1000 lvl=info msg=handling method=GET url=/1.0/containers/gc3/logs/lxc.log ip=@ t=2016-02-25T13:39:21+1000 lvl=info msg=handling method=GET url=/1.0 ip=@ t=2016-02-25T13:39:21+1000 lvl=info msg=handling ip=@ method=GET url=/1.0/containers/gc3 t=2016-02-25T13:39:21+1000 lvl=info msg=handling method=GET url=/1.0/containers/gc3/state ip=@ t=2016-02-25T13:39:21+1000 lvl=info msg=handling method=GET url="/1.0/containers/gc3/snapshots?recursion=1" ip=@ t=2016-02-25T13:39:21+1000 lvl=info msg=handling method=GET url=/1.0/containers/gc3/logs/lxc.log ip=@ ~ lxc info gc3 --show-log Name: gc3 Architecture: x86_64 Created: 2016/02/25 03:27 UTC Status: Running Type: persistent Profiles: default Pid: 11586 Processes: 1 Ips: lo: inet127.0.0.1 lo: inet6 ::1 Log: lxc 20160225132740.709 INFO lxc_confile - confile.c:config_idmap:1495 - read uid map: type u nsid 0 hostid 231072 range 65536 lxc 20160225132740.709 INFO lxc_confile - confile.c:config_idmap:1495 - read uid map: type g nsid 0 hostid 231072 range 65536 lxc 20160225132740.730 WARN lxc_cgfs - cgfs.c:lxc_cgroup_get_container_info:1113 - Not attaching to cgroup name=systemd unknown to /var/lib/lxd/containers gc3 lxc 20160225132740.730 WARN lxc_cgfs - cgfs.c:lxc_cgroup_get_container_info:1113 - Not attaching to cgroup cpu unknown to /var/lib/lxd/containers gc3 lxc 20160225132740.730 WARN lxc_cgfs - cgfs.c:lxc_cgroup_get_container_info:1113 - Not attaching to cgroup devices unknown to /var/lib/lxd/containers gc3 lxc 20160225132740.730 WARN lxc_cgfs - cgfs.c:lxc_cgroup_get_container_info:1113 - Not attaching to cgroup net_cls unknown to /var/lib/lxd/containers gc3 lxc 20160225132740.730 WARN lxc_cgfs - cgfs.c:lxc_cgroup_get_container_info:1113 - Not attaching to cgroup memory unknown to /var/lib/lxd/containers gc3 lxc 20160225132740.730 WARN lxc_cgfs - cgfs.c:lxc_cgroup_get_container_info:1113 - Not attaching to cgroup hugetlb unknown to /var/lib/lxd/containers gc3 lxc 20160225132740.730 WARN lxc_cgfs - cgfs.c:lxc_cgroup_get_container_info:1113 - Not attaching to cgroup perf_event unknown to /var/lib/lxd/containers gc3 lxc 20160225132740.730 WARN lxc_cgfs - cgfs.c:lxc_cgroup_get_container_info:1113 - Not attaching to cgroup cpuset unknown to /var
Re: [lxc-users] /sbin/init failure
The current xenial kernel is unfortunately a bit broken right now, we have an updated LXC and kernel currently going through testing which should be released at some point tomorrow. Rebooting on the 4.4.0-6-generic kernel should fix things, 4.4.0-7-generic is the broken one and 4.4.0-8-generic is the fixed one. On Thu, Feb 25, 2016 at 01:49:42PM +1000, Mark Constable wrote: > Using latest freshly reinstalled xenial host and containers with > 2.0.0~beta4-0ubuntu4 > which got the packages installed after removing everything and starting again > but I've had this problem for a couple of weeks now... > > ~ lxc image list > ++--++++-+--+ > | ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION | > ARCH | SIZE | UPLOAD DATE | > ++--++++-+--+ > | xenial | 0594dbb54ade | no | Ubuntu xenial (amd64) (20160218_03:49) | > x86_64 | 64.87MB | Feb 25, 2016 at 1:45am (UTC) | > ++--++++-+--+ > > ~ lxc image copy upstream:/ubuntu/xenial/amd64 local: --alias=xenial > > ~ lxc launch xenial gc3 > Creating gc3 > Starting gc3 > > ~ lx > +--+-+--+--++---+ > | NAME | STATE | IPV4 | IPV6 |TYPE| SNAPSHOTS | > +--+-+--+--++---+ > | gc3 | RUNNING | | | PERSISTENT | 0 | > +--+-+--+--++---+ > > ~ lxc exec gc3 bash > root@gc3:~# ps aux > USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND > root 1 0.0 0.0 36544 3952 ?Ss 03:27 0:00 /sbin/init > root25 0.0 0.0 18220 3160 ?Ss 03:29 0:00 bash > root36 0.0 0.0 34412 2804 ?R+ 03:29 0:00 ps aux > root@gc3:~# exit > > And of course I have to use "lxc stop gc3 --force" to get it to stop. > > Any idea why /sbin/init is not kicking off the rest of the startup procedure? > > > > ~ ps auxxww | grep -v grep | grep lx > root 9621 0.0 0.0 234760 3744 ?Ssl 11:41 0:00 > /usr/bin/lxcfs /var/lib/lxcfs/ > root 10264 0.0 0.1 960888 25700 ?Ssl 11:41 0:05 /usr/bin/lxd > --group lxd --logfile=/var/log/lxd/lxd.log > root 11567 0.0 0.0 7 4552 ?Ss 13:38 0:00 [lxc > monitor] /var/lib/lxd/containers gc3 > > ~ tail /var/log/lxd/lxd.log > t=2016-02-25T13:38:42+1000 lvl=info msg=handling method=GET url=/1.0 ip=@ > t=2016-02-25T13:38:42+1000 lvl=info msg=handling method=GET > url=/1.0/containers/gc3 ip=@ > t=2016-02-25T13:38:42+1000 lvl=info msg=handling > url=/1.0/containers/gc3/state ip=@ method=GET > t=2016-02-25T13:38:42+1000 lvl=info msg=handling > url="/1.0/containers/gc3/snapshots?recursion=1" ip=@ method=GET > t=2016-02-25T13:38:42+1000 lvl=info msg=handling method=GET > url=/1.0/containers/gc3/logs/lxc.log ip=@ > t=2016-02-25T13:39:21+1000 lvl=info msg=handling method=GET url=/1.0 ip=@ > t=2016-02-25T13:39:21+1000 lvl=info msg=handling ip=@ method=GET > url=/1.0/containers/gc3 > t=2016-02-25T13:39:21+1000 lvl=info msg=handling method=GET > url=/1.0/containers/gc3/state ip=@ > t=2016-02-25T13:39:21+1000 lvl=info msg=handling method=GET > url="/1.0/containers/gc3/snapshots?recursion=1" ip=@ > t=2016-02-25T13:39:21+1000 lvl=info msg=handling method=GET > url=/1.0/containers/gc3/logs/lxc.log ip=@ > > ~ lxc info gc3 --show-log > Name: gc3 > Architecture: x86_64 > Created: 2016/02/25 03:27 UTC > Status: Running > Type: persistent > Profiles: default > Pid: 11586 > Processes: 1 > Ips: > lo: inet127.0.0.1 > lo: inet6 ::1 > > Log: > > lxc 20160225132740.709 INFO lxc_confile - > confile.c:config_idmap:1495 - read uid map: type u nsid 0 hostid 231072 range > 65536 > lxc 20160225132740.709 INFO lxc_confile - > confile.c:config_idmap:1495 - read uid map: type g nsid 0 hostid 231072 range > 65536 > lxc 20160225132740.730 WARN lxc_cgfs - > cgfs.c:lxc_cgroup_get_container_info:1113 - Not attaching to cgroup > name=systemd unknown to /var/lib/lxd/containers gc3 > lxc 20160225132740.730 WARN lxc_cgfs - > cgfs.c:lxc_cgroup_get_container_info:1113 - Not attaching to cgroup cpu > unknown to /var/lib/lxd/containers gc3 > lxc 20160225132740.730 WARN lxc_cgfs - > cgfs.c:lxc_cgroup_get_container_info:1113 - Not attaching to cgroup devices > unknown to /var/lib/lxd/containers gc3 > lxc 20160225132740.730 WARN lxc_cgfs - > cgfs.c:lxc_cgroup_get_container_info:1113 - Not attaching to cgroup net_cls > unknown to /var/lib/lxd/containers gc3 > lxc 20160225132740.730 WARN lxc_cgfs - > cgfs.c:lxc_cgroup_get_c
Re: [lxc-users] What is the status of "stable" LXC PPA?
Bump. Also, is the stable-1.1 PPA actually stable or not? -Cam On Sat, Feb 13, 2016 at 4:33 AM, Andrey Repin wrote: > Greetings, All! > > What is the status of > https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/stable ? > Is it supposed to contain beta builds? > > > -- > With best regards, > Andrey Repin > Saturday, February 13, 2016 15:32:21 > > Sorry for my terrible english... > > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
