Re: [lxc-users] Error installing lxcfs > rc8

Quoting Antonio Tovar (anto...@gmail.com): > Hello, > > I have problems upgrading from lxcfs RC8 to RC9 or v2. > > When upgrading, the installer shows the message: > > Setting up lxcfs (...~ppa1) ... > > and then every filesystem is mounted and the installer freezes. > > I have three fs's

Re: [lxc-users] lxc file push garbling existing file

Up until very recently they were needed to provide the lxcbr0 bridge. However as of two days ago, you can now safely remove those packages as only the LXC library and some common files are now needed (liblxc1 and lxc-common). On Wed, Apr 06, 2016 at 03:57:54PM -0500, Craig Tataryn wrote: > Thank

Re: [lxc-users] lxc progress and a few questions

Greetings - I'be not yet been able to reproduce that one shining moment from Mar 29 when live migration of privileged containers was working, under kernel 4.4.0-15 To recap. live container migration broke with 4.4.0-16, and is still broken in 4.4.0-17 - but now, instead of producing an error

Re: [lxc-users] lxc file push garbling existing file

Thank you! So assuming I'm not using the lxc-* commands, is it even necessary to install them? Is it safe for me to remove the legacy lxc package all together? Craig. On Wed, Apr 6, 2016 at 3:54 PM, Stéphane Graber wrote: > On Wed, Apr 06, 2016 at 03:51:12PM -0500, Craig

Re: [lxc-users] lxc file push garbling existing file

On Wed, Apr 06, 2016 at 03:51:12PM -0500, Craig Tataryn wrote: > Really sorry to be a pain but I am confused... > > I ran: > > sudo apt-get install lxd > sudo apt-get install lxc That's because you forgot to update lxd-client which is the package providing the "lxc" command. > > When I run an

Re: [lxc-users] lxc file push garbling existing file

Really sorry to be a pain but I am confused... I ran: sudo apt-get install lxd sudo apt-get install lxc When I run an `apt-cache policy` they both seem to be running the latest and greatest respective 2.0 rc versions. However, when I run `sudo lxc --version` I still see 0.19, even though `sudo

Re: [lxc-users] lxc file push garbling existing file

Nope, no need to stop the containers. Old package versions may shut them all down before doing the upgrade but that's not necessary at all and newer packages no longer do that. On Wed, Apr 06, 2016 at 03:22:34PM -0500, Craig Tataryn wrote: > I forgot to ask. When upgrading LXD is there any need

Re: [lxc-users] lxc file push garbling existing file

I forgot to ask. When upgrading LXD is there any need to stop the containers before doing so? Craig. On Wed, Apr 6, 2016 at 3:18 PM, Craig Tataryn wrote: > Thanks for the background. My vote is to rename the LXD command-line tools > project to: LXE ;) > > Craig. > > On

Re: [lxc-users] lxc file push garbling existing file

Thanks for the background. My vote is to rename the LXD command-line tools project to: LXE ;) Craig. On Wed, Apr 6, 2016 at 2:28 PM, Stéphane Graber wrote: > The lxc and lxd binaries come from LXD which is currently at rc8. > > The lxc-* binaries are for the "old" user

Re: [lxc-users] lxc file push garbling existing file

The lxc and lxd binaries come from LXD which is currently at rc8. The lxc-* binaries are for the "old" user experience which is LXC itself, that's what we just released as 2.0 earlier today. LXD changelog: https://linuxcontainers.org/lxd/news/ LXC changelog:

Re: [lxc-users] lxc file push garbling existing file

I just saw that 2.0 was released! Congrats! You guys have quick release cycles, I don't consider 6 months that long ago! Q1. Just out of curiosity how does the version displayed using the '--version' switch coincide with the releases on the news page? [1] Also, I find this very interesting...

Re: [lxc-users] Can't ssh my lxc instances and no instance console on Horizon

Thanks. That solved the ssh issue but I still can't access the console from dashboard and it says "console is currently unavailable. Please try again later". Any ideas? On Wed, Apr 6, 2016 at 8:38 PM, Chuck Short wrote: > Hi, > > Are you using devstack? > > If so

[lxc-users] LXC 2.0 has been released!

Hello everyone, It's with great pleasure that the LXC development team is announcing the release of LXC 2.0! This is the result of over a year of work from upstream LXC and was made of over 700 commits by over 90 contributors! It also joins LXCFS which got its own 2.0 release last week and will

Re: [lxc-users] sysvinit with cgroup namespace

Quoting KATOH Yasufumi (ka...@jazz.email.ne.jp): > Sorry, I ran old version (2.0.0.rc7). > > > My desktop is used sysvinit as init. > > > I try using the "cgroup namespace", then a lxc container does not > > start. > > > Now, If we have '/proc/self/ns/cgroup', then cgfsng is used as cgroup > >

Re: [lxc-users] sysvinit with cgroup namespace

Quoting KATOH Yasufumi (ka...@jazz.email.ne.jp): > Hi, > > My desktop is used sysvinit as init. > > I try using the "cgroup namespace", then a lxc container does not > start. > > Now, If we have '/proc/self/ns/cgroup', then cgfsng is used as cgroup > driver (in cgfsng_opt_init function). But in

Re: [lxc-users] lxc file push garbling existing file

On Wed, Apr 06, 2016 at 09:55:08AM -0500, Craig Tataryn wrote: > I've setup an automated deploy script that does the following: > > * Uploads (via scp) a file to a host > * Executes (via ssh) the `lxc file push` command to a container on that host > > Every once in a while the file that is

Re: [lxc-users] sysvinit with cgroup namespace

Sorry, I ran old version (2.0.0.rc7). > My desktop is used sysvinit as init. > I try using the "cgroup namespace", then a lxc container does not > start. > Now, If we have '/proc/self/ns/cgroup', then cgfsng is used as cgroup > driver (in cgfsng_opt_init function). But in all_controllers_found

[lxc-users] sysvinit with cgroup namespace

Hi, My desktop is used sysvinit as init. I try using the "cgroup namespace", then a lxc container does not start. Now, If we have '/proc/self/ns/cgroup', then cgfsng is used as cgroup driver (in cgfsng_opt_init function). But in all_controllers_found function (in cgfsng.c), systemd cgroup

Re: [lxc-users] Can't ssh my lxc instances and no instance console on Horizon

Hi, > I'm unable to ssh into any instance except the CirrOS. For ssh, did you try to set pam_loginuid.so to "optional" in /etc/pam.d/sshd in your containers? Regards, Xavier ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org