Firstly you will need to decide whether you want to use lxc, or lxd.
There is no such thing as "lxd/lxc" as the two tools are completely
separate, pretty different in behavior, and the interface for
interacting with them is completely different.

However, in the general case of any arbitrary Linux-based OS in an
OpenVZ container, there's a fairly high chance that some random
service or another will fail (for a multitude of reasons) if you try
to boot its disk image under lxc or lxd; indeed, it may not even boot.

It depends on what your container's OS is, though. An OpenVZ image of,
say, Ubuntu 16.04, *might* be a better fit for direct copying into an
lxc or lxd container, though you would still have to at least adjust
things like networking, user and group IDs, and things like that.

There is no general-purpose "command structure" that will work with
*all* OpenVZ containers across *all* OpenVZ versions and allow
successful, problem-free importing into any arbitrary version of lxc
or lxd, though. You can try copying the raw files of the image into an
lxd or lxc container you've created from scratch and then see if it
boots, and fix it where it fails; or you can take the (IMO) easier
path, and create a new container and then copy over the files you need
via the host.


On Mon, Sep 12, 2016 at 1:33 PM, Steven Spencer <[email protected]> wrote:
> Greetings,
>
> Is there a command structure that will allow for an import of an openvz
> container into lxd/lxc or is the best method to use a new container and
> rsync any content needed?
>
> Thanks,
> Steven G. Spencer
>
> _______________________________________________
> lxc-users mailing list
> [email protected]
> http://lists.linuxcontainers.org/listinfo/lxc-users
_______________________________________________
lxc-users mailing list
[email protected]
http://lists.linuxcontainers.org/listinfo/lxc-users

Reply via email to