Re: [lxc-users] TTY issue

Thanks for the solution. It works indeed. Just out of curiosity, how did you find this out? I googled it far and wide and there was nothing available. On Sat, Nov 18, 2017 at 9:13 AM, Marat Khalili wrote: > On 18/11/17 17:10, Saint Michael wrote: > > Yes, of course. It works but

Re: [lxc-users] TTY issue

On 21/11/17 15:07, Saint Michael wrote: Thanks for the solution. It works indeed. Just out of curiosity, how did you find this out? I googled it far and wide and there was nothing available. The autodev part, I needed it in order to make qemu networking work in a container via /dev/net/tun

[lxc-users] Working configuration for live migration

Dear all, could you please suggest the exact versions of LXD, CRIU and Linux kernel on top of which you managed to successfully migrate a container statefully? Any other specific configuration? We are working with Linux kernel 4.13.0-17, LXD 2.20 and CRIU 3.4 and it always gives the same error:

[lxc-users] lxd.migrate doesn't work with Ubuntu based distro

$ snap install lxd 2017-11-21T10:36:27-03:00 INFO Waiting for restart... lxd 2.20 from 'canonical' installed $ lxd.migrate error: This tool must be run as root. $ sudo lxd.migrate error: Data migration is only supported on Ubuntu at this time. $ lsb_release -a No LSB modules are available.

[lxc-users] Using a mounted drive to handle storage pool

I've currently migrated LXD from canonical PPA to Snap. I have 2 RAIDS: * /dev/sda - ext4 (this is root device) * /dev/sdb - brtfs (where I want my pool to be with the containers and snapshots) How/where should I mount my btrfs device? What's the best practice in having the pool

Re: [lxc-users] Using a mounted drive to handle storage pool

Perhaps you should use “bind” mount instead of symbolic links here? mount -o bind /storage/lxd /var/snap/lxd You probably also need to make sure survives a reboot. -Ron > On Nov 21, 2017, at 5:47 PM, Lai Wei-Hwa wrote: > > In the following scenario, I: > > $ sudo

Re: [lxc-users] Snap 2.20 - Default Text Editor

sudo update-alternatives --config editor http://vim.wikia.com/wiki/Set_Vim_as_your_default_editor_for_Unix > On Nov 21, 2017, at 7:49 PM, Lai Wei-Hwa wrote: > > Thanks, but that's the problem, it's still opening in VI > > Thanks! > Lai > > - Original Message - >

Re: [lxc-users] Using a mounted drive to handle storage pool

On Wed, Nov 22, 2017 at 1:37 AM, Lai Wei-Hwa wrote: > I've currently migrated LXD from canonical PPA to Snap. > > I have 2 RAIDS: > >- /dev/sda - ext4 (this is root device) >- /dev/sdb - brtfs (where I want my pool to be with the containers and >snapshots) > >

[lxc-users] Bonding inside container? Or any other ideas?

Greetings, All! Some time ago I've managed to install a second network card into one of my servers, and have been experimenting with bonding on host. The field is: a host with two cards in one bond0 interface. A number of containers sitting as macvlans on top of bond0. Some success was achieved

Re: [lxc-users] Using a mounted drive to handle storage pool

In the following scenario, I: $ sudo mount /dev/sdb /storage Then, when I do: $ sudo ln -s /storage/lxd lxd $ snap install lxd $ sudo lxd init error: Unable to talk to LXD: Get http://unix.socket/1.0: dial unix /var/snap/lxd/common/lxd/unix.socket: connect: no such file or directory

Re: [lxc-users] Bonding inside container? Or any other ideas?

I'm not sure I follow. I have multiple servers running Bond Mode 4 (for LACP/802.3ad). I then created a bridge, br0 which becomes the main (only) interface. I'm using flat networking with no NATS between containers and edited the profiles to use br0. Everything works for me. I can't speak to

Re: [lxc-users] Using a mounted drive to handle storage pool

That seems to work! I still get the message: error: Unable to talk to LXD: Get http://unix.socket/1.0: dial unix /var/snap/lxd/common/lxd/unix.socket: connect: no such file or directory But if I run it again, it inits. Thanks, Ron. Thanks! Lai - Original Message - From: "Ron Kelley"

Re: [lxc-users] Snap 2.20 - Default Text Editor

Hi, > $ lxc profile edit default > Opens in VI even though my editor is nano (save the flaming) > > How can we edit the default editor? $ EDITOR=nano $ export EDITOR Cheers, Björn ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org

Re: [lxc-users] Snap 2.20 - Default Text Editor

Thanks, but that's the problem, it's still opening in VI Thanks! Lai - Original Message - From: "Björn Fischer" To: "lxc-users" Sent: Tuesday, November 21, 2017 7:46:58 PM Subject: Re: [lxc-users] Snap 2.20 - Default

[lxc-users] Snap 2.20 - Default Text Editor

$ lxc profile edit default Opens in VI even though my editor is nano (save the flaming) How can we edit the default editor? Best Regards, Lai Wei-Hwa ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org