Re: [lxc-users] lxd images error

2016-02-25 Thread laurent ducos
sorry for the first post. The error is lxc image list images: error: json: cannot unmarshal string into Go value of type int64 Same error when i want to launch a image. Le mer. 24 févr. 2016 à 10:23, laurent ducos a écrit : > Hello i have a problem with lxd this morning : > > lxc list images: er

Re: [lxc-users] What is the status of "stable" LXC PPA?

2016-02-25 Thread Timotheus Pokorra
I just checked the history: https://lists.linuxcontainers.org/pipermail/lxc-users/2015-April/008881.html describes what ppas are available. https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxc-lts seems to be fixed on lxc 1.0.x Timotheus > Bump. Also, is the stable-1.1 PPA actually stable or no

Re: [lxc-users] Antw: Re: Cannot start network: Failed to attach

2016-02-25 Thread Fajar A. Nugraha
On Wed, Feb 24, 2016 at 7:51 PM, Thomas Belián wrote: Jochen Wiedmann schrieb am 2/24/2016 um > 10:06 AM in > Nachricht >> 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

Re: [lxc-users] What is the status of "stable" LXC PPA?

2016-02-25 Thread Cam Cope
Ok, that clarification is helpful. The ppa's statuses are inconsistent with those descriptions though: - 'stable' currently contains release candidate builds of lxc - https://launchpad.net/~ubuntu-lxc states that the stable-1.0 and stable-1.1 ppa's contain "development builds" - https://launchpa

[lxc-users] setcap does not work in unprivileged container

2016-02-25 Thread Tamas Papp
hi All, # /sbin/setcap 'cap_net_bind_service=+ep' /usr/bin/nodejs Failed to set capabilities on file `/usr/bin/nodejs' (Invalid argument) The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file Can we somehow make it work? 10x tamas

Re: [lxc-users] setcap does not work in unprivileged container

2016-02-25 Thread Mark Constable
On 25/02/16 20:16, Tamas Papp wrote: # /sbin/setcap 'cap_net_bind_service=+ep' /usr/bin/nodejs Failed to set capabilities on file `/usr/bin/nodejs' (Invalid argument) The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file Can we somehow

Re: [lxc-users] setcap does not work in unprivileged container

2016-02-25 Thread Tamas Papp
On 02/25/2016 11:49 AM, Mark Constable wrote: On 25/02/16 20:16, Tamas Papp wrote: # /sbin/setcap 'cap_net_bind_service=+ep' /usr/bin/nodejs Failed to set capabilities on file `/usr/bin/nodejs' (Invalid argument) The value of the capability argument is not permitted for a file. Or the file is

Re: [lxc-users] Antw: Re: Cannot start network: Failed to attach

2016-02-25 Thread Thomas Belián
>>> "Fajar A. Nugraha" schrieb am 2/25/2016 um 10:44 AM in Nachricht : > On Wed, Feb 24, 2016 at 7:51 PM, Thomas Belián > wrote: > Jochen Wiedmann schrieb am 2/24/2016 um > > 10:06 AM in > > Nachricht > >> Thanks! Installing libvirt fixed my problem. > >> > >> Jochen > > > > Hello Jochen, >

Re: [lxc-users] Antw: Re: Cannot start network: Failed to attach

2016-02-25 Thread Fajar A. Nugraha
On Thu, Feb 25, 2016 at 6:52 PM, Thomas Belián wrote: >> > 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). >> >> With THAT alone, you'd get something similar to v

Re: [lxc-users] lxd images error

2016-02-25 Thread laurent ducos
ok i have upgraded lxd and all is ok now. Sorry for the noise Le jeu. 25 févr. 2016 à 09:08, laurent ducos a écrit : > sorry for the first post. > The error is > lxc image list images: error: json: cannot unmarshal string into Go value > of type int64 > Same error when i want to launch a image.

Re: [lxc-users] setcap does not work in unprivileged container

2016-02-25 Thread Serge Hallyn
Quoting Tamas Papp (tom...@martos.bme.hu): > hi All, > > > # /sbin/setcap 'cap_net_bind_service=+ep' /usr/bin/nodejs > Failed to set capabilities on file `/usr/bin/nodejs' (Invalid argument) > The value of the capability argument is not permitted for a file. Or > the file is not a regular (non-sy

Re: [lxc-users] setcap does not work in unprivileged container

2016-02-25 Thread Tamas Papp
On 02/25/2016 05:51 PM, Serge Hallyn wrote: Quoting Tamas Papp (tom...@martos.bme.hu): hi All, # /sbin/setcap 'cap_net_bind_service=+ep' /usr/bin/nodejs Failed to set capabilities on file `/usr/bin/nodejs' (Invalid argument) The value of the capability argument is not permitted for a file. O

[lxc-users] [urgent] help! nc-lxd(nova-compute-lxd) support current status

2016-02-25 Thread 디케이
nc-lxd supports openstack? I mean that NC-LXD(nova-compute-lxd) can be configured and work with openstack now? or not though LXD is still beta version, I thought basic LXD implementation with openstack is work. because I found information about openstack support of LXD through openstack summit vid

Re: [lxc-users] setcap does not work in unprivileged container

2016-02-25 Thread Serge Hallyn
Quoting Tamas Papp (tom...@martos.bme.hu): > > > On 02/25/2016 05:51 PM, Serge Hallyn wrote: > >Quoting Tamas Papp (tom...@martos.bme.hu): > >>hi All, > >> > >> > >># /sbin/setcap 'cap_net_bind_service=+ep' /usr/bin/nodejs > >>Failed to set capabilities on file `/usr/bin/nodejs' (Invalid argument

Re: [lxc-users] [urgent] help! nc-lxd(nova-compute-lxd) support current status

2016-02-25 Thread Serge Hallyn
Quoting 디케이 (zunt...@gmail.com): > nc-lxd supports openstack? > I mean that NC-LXD(nova-compute-lxd) can be configured and work with > openstack now? or not > > though LXD is still beta version, > I thought basic LXD implementation with openstack is work. > because I found information about openst

Re: [lxc-users] setcap does not work in unprivileged container

2016-02-25 Thread Mark Constable
On 26/02/16 05:56, Serge Hallyn wrote: Hopefully in the next month or two I'll get time to get that working in the kernel. Which means a few more months before it'd be really available. Can we expect it to be backported to Xenial? No, but the HWE and such kernels will have it. They are just

[lxc-users] no lxc nor lxd containers start after recent update

2016-02-25 Thread Tomasz Chmielewski
None of my lxc nor lxd container start after the most recent lxc/lxd update. Any clues? # lxc-start -n td-backupslave lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start: lxc_sta

Re: [lxc-users] no lxc nor lxd containers start after recent update

2016-02-25 Thread Tomasz Chmielewski
Doing the following seems to help: # service lxcfs stop # service lxcfs start Then, I'm able to manually start lxc and lxd containers. Tomasz On 2016-02-26 09:04, Tomasz Chmielewski wrote: None of my lxc nor lxd container start after the most recent lxc/lxd update. Any clues? # lxc-sta

Re: [lxc-users] no lxc nor lxd containers start after recent update

2016-02-25 Thread Tomasz Chmielewski
Also, with the "service lxcfs stop/start fix", console in lxd containers (in lxc, all fine) looks botched - after pressing enter, getting as below. I guess it wasn't the best of updates, at least for me. # lxc exec z-testing-a19ea622182c63ddc19bb22cde982b82-2016-02-24-19-20-55 /bin/bash roo

Re: [lxc-users] no lxc nor lxd containers start after recent update

2016-02-25 Thread Serge Hallyn
Yes, fixes for all of these should now be in git and on their way to the ppas and archive. Been quite a week. ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] setcap does not work in unprivileged container

2016-02-25 Thread Tamas Papp
On 02/25/2016 08:56 PM, Serge Hallyn wrote: Quoting Tamas Papp (tom...@martos.bme.hu): On 02/25/2016 05:51 PM, Serge Hallyn wrote: Quoting Tamas Papp (tom...@martos.bme.hu): hi All, # /sbin/setcap 'cap_net_bind_service=+ep' /usr/bin/nodejs Failed to set capabilities on file `/usr/bin/node