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 pool
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.
$ 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.
Distr
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:~$ s
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, not for http and other
me
> able to resolve *.lxd domains from the host machine.
> --
> Matlink
>
> Le 17 avril 2017 13:42:36 GMT+02:00, Simos Xenitellis
> a écrit :
>>
>> On Thu, Apr 13, 2017 at 10:49 PM, Norberto Bensa
>> wrote:
>>>
>>> Hello Simos,
>>>
>&
2017-04-17 8:42 GMT-03:00 Simos Xenitellis :
> On Thu, Apr 13, 2017 at 10:49 PM, Norberto Bensa
> wrote:
>> Hello Simos,
>>
>> 2017-04-13 10:44 GMT-03:00 Simos Xenitellis :
>>> I got stuck with this issue (Ubuntu Desktop with NetworkManager) and
>>> wro
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 with 17.04
I tried a lot of con
in the 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 :
> On Wed, Mar 29, 2017 at 12:59:15AM -0300, Norberto Bensa wrote:
>> 2017-03-29 0:29 GMT-03:00 Serge E. Hallyn :
>> > On Wed, Mar 29, 2017 at
2017-03-29 0:29 GMT-03:00 Serge E. Hallyn :
> 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.
>
> https://help.u
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 time
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 discovered that some file own
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),
python3-lxc:
2015-10-27 1:31 GMT-03:00 Fajar A. Nugraha :
> On Tue, Oct 27, 2015 at 6:20 AM, Norberto Bensa
> wrote:
>>
>> This problem is related to network-manager (NM) or systemd.
>>
>> I tried to disable NM but I couldn't. NM started with every boot (does
>> syst
10-26 19:28 GMT-03:00 Norberto Bensa :
> 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 fetc
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:~$ LC_ALL=C
2015-04-21 11:01 GMT-03:00 Fajar A. Nugraha :
> On Tue, Apr 21, 2015 at 7:06 PM, Norberto Bensa
> wrote:
> > 2015-03-11 23:01 GMT-03:00 Norberto Bensa :
> >>
> >> And of course it's a bug and is reported.
> >>
> >> https://bugs.l
2015-03-11 23:01 GMT-03:00 Norberto Bensa :
> 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
2015-03-25 2:53 GMT-03:00 Fajar A. Nugraha :
> On Tue, Mar 24, 2015 at 2:10 PM, Fajar A. Nugraha wrote:
> > On Tue, Mar 24, 2015 at 5:52 AM, Norberto Bensa
> > wrote:
> >> Hello,
> >>
> >> from time to tome, I think once per day, my containers get
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 too
Quoting Norberto Bensa (nbensa+lxcus...@gmail.com):
> > Hello Tycho,
> >
> > 2015-03-11 20:10 GMT-03:00 Tycho Andersen >:
> >
> > > On Wed, Mar 11, 2015 at 07:57:50PM -0300, Norberto Bensa wrote:
> > > > Hello,
> > > >
> > >
container.
Maybe the package maintainer would want to remove that line from
/etc/lxc/default.conf.
Thanks for reading.
Norberto
2015-03-11 19:57 GMT-03:00 Norberto Bensa :
> Hello,
>
> new containers (created with lxc-create) have either no network or the ip
> address is not prese
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 :
> This one is a kernel issue. Going back to trusty's kernel solves these
> issues with mailq and pam/kerberos/ldap.
>
&g
Bad:
ii linux-image-3.16.0-31-generic 3.16.0-31.43
amd64Linux kernel image for version 3.16.0
on 64 bit x86 SMP
2015-03-11 22:14 GMT-03:00 Norberto Bensa :
> Update.
>
> # mailq
> Mail queue is empty
> # mailq
> po
lq 2>&1 |grep Mail; done
# for i in {1..1000}; do mailq 2>&1 |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:4
Hello Tycho,
2015-03-11 20:10 GMT-03:00 Tycho Andersen :
> On Wed, Mar 11, 2015 at 07:57:50PM -0300, Norberto Bensa wrote:
> > Hello,
> >
> > new containers (created with lxc-create) have either no network or the ip
> > address is not preserved between container
Hello,
new containers (created with lxc-create) have either no network or the ip
address is not preserved between container reboots.
Containers without network lack all lxc.network.* entries in the confg file.
Containers with random ip address have lxc.network.hwaddr =
00:16:3e:xx:xx:xx
Is this
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 ma
28 matches
Mail list logo
