Re: [lxc-users] problem after migrating zfs pool to new disk

I cloned the github repository and found docs/database.md There's a patch.global.sql that did the trick :-) On Sat, Nov 21, 2020 at 8:30 PM Norberto Bensa wrote: > Hello, > > $ snap list > lxd 4.818324 latest/stable canonical✓ - > > I moved my zfs

[lxc-users] problem after migrating zfs pool to new disk

Hello, $ snap list lxd 4.818324 latest/stable canonical✓ - I moved my zfs pool to a new disk and then renamed the pool. Old name was zroot, new name: rz1-venkman-nvme. The pool was migrated using zfs send|zfs receive. While doing the migration, both pools were on the same machine.

[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] lxc-destroy: "container has snapshots" but it doesn't

Hello, I haven't read the code, but it seems lxc-destroy checks if there's a 'snaps' directory and if it exists the code asumes there's at least one snapshot. nbensa@tecno04:~$ sudo lxc-destroy -n eleva [sudo] password for nbensa: Destroying eleva failed: eleva has snapshots. nbensa@tecno04:~$

Re: [lxc-users] Resolve .lxc domain with Ubuntu 17.04

auth-zone=lxd > dns-loop-detect > name: lxdbr0 > type: bridge > > No more 100% cpu usage any more! > > The workaround I was using until I figured it out was... > https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1571967/comments/13 -- > but that only works for ssh, no

Re: [lxc-users] Resolve .lxc domain with Ubuntu 17.04

ss to DNS resolvers made me > able to resolve *.lxd domains from the host machine. > -- > Matlink > > Le 17 avril 2017 13:42:36 GMT+02:00, Simos Xenitellis > <simos.li...@googlemail.com> a écrit : >> >> On Thu, Apr 13, 2017 at 10:49 PM, Norberto Bensa >> <

Re: [lxc-users] Resolve .lxc domain with Ubuntu 17.04

-04-17 8:42 GMT-03:00 Simos Xenitellis <simos.li...@googlemail.com>: > On Thu, Apr 13, 2017 at 10:49 PM, Norberto Bensa > <nbensa+lxcus...@gmail.com> wrote: >> Hello Simos, >> >> 2017-04-13 10:44 GMT-03:00 Simos Xenitellis <simos.li...@googlemail.com>: >&

Re: [lxc-users] Resolve .lxc domain with Ubuntu 17.04

Hello Simos, 2017-04-13 10:44 GMT-03:00 Simos Xenitellis : > I got stuck with this issue (Ubuntu Desktop with NetworkManager) and > wrote about it at > https://www.mail-archive.com/lxc-users@lists.linuxcontainers.org/msg07060.html For me, that doesn't work anymore

Re: [lxc-users] Resolve .lxc domain with Ubuntu 17.04

he desktop version, systemd-resolved and dnsmasq eat my cpu. Maybe a network-manager bug? 2017-03-29 1:25 GMT-03:00 Serge E. Hallyn <se...@hallyn.com>: > On Wed, Mar 29, 2017 at 12:59:15AM -0300, Norberto Bensa wrote: >> 2017-03-29 0:29 GMT-03:00 Serge E. Hallyn <se...@hallyn.com

Re: [lxc-users] Resolve .lxc domain with Ubuntu 17.04

2017-03-29 0:29 GMT-03:00 Serge E. Hallyn <se...@hallyn.com>: > On Wed, Mar 29, 2017 at 12:16:29AM -0300, Norberto Bensa wrote: >> Hello list! >> >> In previous versions of Ubuntu I had lxc domain name resolution >> working, but it's broken for me in 17.04

[lxc-users] Resolve .lxc domain with Ubuntu 17.04

Hello list! In previous versions of Ubuntu I had lxc domain name resolution working, but it's broken for me in 17.04. Name resolution inside the containers work: ubuntu@consulta:~⟫ ping fox PING fox.lxc (10.0.1.114) 56(84) bytes of data. 64 bytes from fox.lxc (10.0.1.114): icmp_seq=1 ttl=64

Re: [lxc-users] Ownership changes after container move

Hi, what prodecure did you use to move the container? I usually use tar: cd /var/lib/lxc/ ; tar --numeric-owner -zcpf containter.tar container/, then, tar -zxpf container.tar in the target host. HTH, Norberto 2015-11-10 6:10 GMT-03:00 Jamie Brown : > Hi, > > I’ve

Re: [lxc-users] re lxcbr0 doesn't exist after upgrade to 15.10

Hello. This problem fixed by itself. Today I re-enabled systemd and after a reboot lxcbr0 is up and running again. Maybe this update has something to do with it: Start-Date: 2015-10-26 20:37:19 Commandline: apt-get dist-upgrade Upgrade: lxc:amd64 (1.1.4-0ubuntu1, 1.1.4-0ubuntu1.1),

Re: [lxc-users] lxcbr0 doesn't exist after upgrade to 15.10

2015-10-27 1:31 GMT-03:00 Fajar A. Nugraha <l...@fajar.net>: > On Tue, Oct 27, 2015 at 6:20 AM, Norberto Bensa <nbensa+lxcus...@gmail.com> > wrote: >> >> This problem is related to network-manager (NM) or systemd. >> >> I tried to disable NM but I

Re: [lxc-users] lxcbr0 doesn't exist after upgrade to 15.10

19:28 GMT-03:00 Norberto Bensa <nbensa+lxcus...@gmail.com>: > zoolook@venkman:~$ LC_ALL=C ifconfig lxcbr0 > lxcbr0: error fetching interface information: Device not found > > zoolook@venkman:~$ LC_ALL=C sudo service lxc-net start > > zoolook@venkman:~$ LC_ALL=C ifconfi

[lxc-users] lxcbr0 doesn't exist after upgrade to 15.10

zoolook@venkman:~$ LC_ALL=C ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found zoolook@venkman:~$ LC_ALL=C sudo service lxc-net start zoolook@venkman:~$ LC_ALL=C ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found zoolook@venkman:~$

[lxc-users] #1390223 Apparmor related regression on access to unix sockets (was: ubuntu utopic (14.10) permission problems?)

2015-03-11 23:01 GMT-03:00 Norberto Bensa nbensa+lxcus...@gmail.com: And of course it's a bug and is reported. https://bugs.launchpad.net/ubuntu/utopic/+source/linux/+bug/1390223 Hello. Is anyone working on this? It says Fix Released for and old Vivid kernel (3.18) but I still have

Re: [lxc-users] #1390223 Apparmor related regression on access to unix sockets (was: ubuntu utopic (14.10) permission problems?)

2015-04-21 11:01 GMT-03:00 Fajar A. Nugraha l...@fajar.net: On Tue, Apr 21, 2015 at 7:06 PM, Norberto Bensa nbensa+lxcus...@gmail.com wrote: 2015-03-11 23:01 GMT-03:00 Norberto Bensa nbensa+lxcus...@gmail.com: And of course it's a bug and is reported. https://bugs.launchpad.net/ubuntu

Re: [lxc-users] container stuck until lxcfs restart

2015-03-25 2:53 GMT-03:00 Fajar A. Nugraha l...@fajar.net: On Tue, Mar 24, 2015 at 2:10 PM, Fajar A. Nugraha l...@fajar.net wrote: On Tue, Mar 24, 2015 at 5:52 AM, Norberto Bensa nbensa+lxcus...@gmail.com wrote: Hello, from time to tome, I think once per day, my containers get stuck. I

[lxc-users] container stuck until lxcfs restart

Hello, from time to tome, I think once per day, my containers get stuck. I found that `service lxcfs restart` restores functionality. Is this a know bug? ii liblxc1 1.1.0-0ubuntu1 amd64Linux Containers userspace

Re: [lxc-users] ubuntu utopic (14.10) permission problems?

Mail; done # for i in {1..1000}; do mailq 21 |grep Mail; done Mail queue is empty Does this ring any bell? I'm using postfix as an example but I think this is related to my kerberos/ldap/pam problem. Postfix is just easier to set up :-) Thanks! 2015-03-11 0:42 GMT-03:00 Norberto Bensa nbensa

Re: [lxc-users] more ubuntu utopic problems (network)

...@ubuntu.com: Quoting Norberto Bensa (nbensa+lxcus...@gmail.com): Hello Tycho, 2015-03-11 20:10 GMT-03:00 Tycho Andersen tycho.ander...@canonical.com : On Wed, Mar 11, 2015 at 07:57:50PM -0300, Norberto Bensa wrote: Hello, new containers (created with lxc-create) have either

Re: [lxc-users] ubuntu utopic (14.10) permission problems?

And of course it's a bug and is reported. https://bugs.launchpad.net/ubuntu/utopic/+source/linux/+bug/1390223 2015-03-11 22:58 GMT-03:00 Norberto Bensa nbensa+lxcus...@gmail.com: This one is a kernel issue. Going back to trusty's kernel solves these issues with mailq and pam/kerberos/ldap

[lxc-users] ubuntu utopic (14.10) permission problems?

Hello, I upgraded my main box to ubuntu 14.10 and now my containers are failing with weird permission problems. A simple test is this: $ sudo lxc-create -t ubuntu -n testing -- -r trusty In the containter install postfix (sudo apt-get install postfix). After a basic postfix configuration, run