On Wed, Aug 08, 2018 at 09:06:40PM +0200, Tomasz Chmielewski wrote:
> I've tried to migrate from deb to snap on Ubuntu 18.04.
>
> Unfortunately, lxd.migrate failed with "error: LXD still not running after 5
> minutes":
>
> root@b1 ~ # lxd.migrate
> => Connecting to source server
> => Connecting
On Wed, Aug 08, 2018 at 11:26:10PM +0200, Tomasz Chmielewski wrote:
> On 2018-08-08 22:26, Stéphane Graber wrote:
>
> > > Not sure how to recover now? The containers seem intact in
> > > /var/lib/lxd/
> >
> > What do you get if you do "journalctl -u snap.lxd.daemon -n 300" and
>
> -- Logs begin
wrote:
Has anybody invented a procedure, a script, etc., to convert a running
machine to a LXC container? I was thinking to create a container of the
same OS, and then use rsync, excluding /proc /tmp/ /sys etc. Any ideas?
Use the fabulous lxd-p2c script.
On Wed, Aug 08, 2018 at 07:04:31PM -0400, Saint Michael wrote:
> Has anybody invented a procedure, a script, etc., to convert a running
> machine to a LXC container? I was thinking to create a container of the
> same OS, and then use rsync, excluding /proc /tmp/ /sys etc. Any ideas?
We have that
Has anybody invented a procedure, a script, etc., to convert a running
machine to a LXC container? I was thinking to create a container of the
same OS, and then use rsync, excluding /proc /tmp/ /sys etc. Any ideas?
___
lxc-users mailing list
I've converted (manually) some lxc containers to lxd and back in the past.
IIRC the biggest difference was that lxd does not need to output anything
to console, while lxc needs it (e.g. for lxc-attach). Depending on what
container distro and version you use, it might not matter (e.g. it should
Sorry, my mistake. I meant "lxc-console". And I just rechecked, apparently
there's the equivalent "lxc console" command as well.
Ignore my comment about "lxc-attach" earlier. You should be able to use lxd
rootfs for lxc as long as:
- you have the correct uid mapping (it's simpler if you just use
The question is how can I use that for plan LXC.
I can install a box with LXD, bring the computer in, but then I want a
plain LXC container.
Is it doable?
On Wed, Aug 8, 2018 at 7:17 PM David Favor wrote:
> wrote:
> > Has anybody invented a procedure, a script, etc., to convert a running
> >
LXD does not support lxc-attach?
I thought that LXD was a superset of LXC, that added on top of it.
Maybe somebody care to explain how LXC and LXD compare.
On Wed, Aug 8, 2018 at 11:21 PM Fajar A. Nugraha wrote:
> I've converted (manually) some lxc containers to lxd and back in the past.
>
Greetings, Goran!
> # cat /proc/self/uid
> cat: /proc/self/uid: No such file or directory
> I do not log into the container but attach to it.
How do you attach?
--
With best regards,
Andrey Repin
Wednesday, August 8, 2018 14:28:13
Sorry for my terrible english...
I log into Arch Linux OS. Form there I attach to the container
# lxc-attach -n monitor
The container itself is hosting Arch Linux too.
2018-08-08 13:28 GMT+02:00 Andrey Repin :
> Greetings, Goran!
>
>> # cat /proc/self/uid
>> cat: /proc/self/uid: No such file or directory
>
>> I do not log into
I've tried to migrate from deb to snap on Ubuntu 18.04.
Unfortunately, lxd.migrate failed with "error: LXD still not running
after 5 minutes":
root@b1 ~ # lxd.migrate
=> Connecting to source server
=> Connecting to destination server
=> Running sanity checks
=== Source server
LXD version:
On 2018-08-08 21:06, Tomasz Chmielewski wrote:
I've tried to migrate from deb to snap on Ubuntu 18.04.
Unfortunately, lxd.migrate failed with "error: LXD still not running
after 5 minutes":
(...)
Not sure how to recover now? The containers seem intact in
/var/lib/lxd/
It seems it's
13 matches
Mail list logo
