Hi guys,
Can someone post a full log from a container where this fails? I'm
curious if it has the warning,
+ WARN("using host's /dev/null for container init's std
fds, migraiton won't work");
If so, it seems like the containers rootfs isn't set up correctly and
all is behaving as e
Hi,
It looks like you need the `linux-image-extra` package, you're missing
some of the required modules for checkpoint/restore to work.
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
And once https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580355 is
"Fix released" for Xenial you won't need linux-image-extra any more, but
you do for now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
h
Hi Frank,
On Sun, May 08, 2016 at 09:15:29AM -, Frank Kloeker wrote:
> I have the same issue on a fresh installed Ubuntu-16.04 VM on OpenStack,
> but not in a VM on Citrix XenCenter. Are there some depedencies from the
> hypervisor?
This is not the same issue,
> criu 2.0-2ubuntu3 amd64
> lxd
Strange. Basically it's using the host's /dev/null as described in
7a55c1576e2752e27882c52e34edcb8388120ad1, but I'm not sure why it would
be doing that if you have a valid /dev/null in the container.
If you turn on autodev does it work?
--
You received this bug notification because you are a me
Right. I'm guessing your container doesn't have a proper /dev/null
itself? That will cause this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1569679
Title:
lxc failed to do
Do you have autodev turned off in the container without the container
itself having a /dev/null? I think that will still trigger this bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.n
Can you show the output in the dump.log in the checkpoint directory?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1569679
Title:
lxc failed to do lxc-checkpoint again
Statu
On Thu, Mar 24, 2016 at 06:00:53PM -, Cui Wei wrote:
> Just new I tried the updated CRIU:
>
> >> Linux Image Version: 4.4.0.15.16
> >> CRIU Version: 2.0-2ubuntu2
> >> LXC Version: 2.0.0~rc12-0ubuntu1
>
>
> The checkpoint step became success, but recovery step failed:
>
> + lxc-checkpoint -s
Can you please try the updated CRIU?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1561434
Title:
lxc-checkpoint failed on current newest version
Status in lxc package in Ub
Public bug reported:
This package used to have a useful script called running-in-container.
Indeed, the bash missing binary scripts still think it does:
root@criu:~# cat /etc/issue
Ubuntu Xenial Xerus (development branch) \n \l
root@criu:~# running-in-container
The program 'running-in-container'
Hi,
What version of CRIU are you using? (`dpkg -l | grep criu`) There were
some bugs with ubuntu1, so try 2.0-2ubuntu2.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1561434
T
On Wed, Jan 20, 2016 at 05:48:52PM -, Tom Haddon wrote:
> Public bug reported:
>
> I've followed https://help.ubuntu.com/lts/serverguide/lxc.html#lxc-
> basic-usage but am getting a failure on lxc-start as follows:
>
> lxc-start -n container-test2 -F
> lxc-start: start.c: print_top_failing_di
Hi,
What version of criu do you have installed? What's the host? Can you
show the output of /tmp/checkpont/{dump,restore}.log after the failure?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://b
The lxc in wily-proposed also works for me: inet addr:10.0.4.1
Thanks all.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1509414
Title:
pre-installed lxc in cloud image prod
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1384751
Title:
checkpoint restore fails with /usr/lib/x86_
** Description changed:
+
+ Impact: restoring containers from a checkpoint doesn't work
+ Development fix: LXC uses /usr/lib/x86_64-linux-gnu/lxc as the path to moun
the container's root filesystem in its private mount namespace bef
Sorry about that, turns out I copied and pasted from my terminal to
create the file, which screwed up some whitespace. In any case, here's
an updated debdiff that has been install tested.
** Patch added: "updated.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384751/+attachment/4
Here's a debdiff for the patch.
** Patch added: "lxc.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384751/+attachment/4246695/+files/lxc.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu
19 matches
Mail list logo
