Convert CT from OpenVZ to LXC manually?

[ramses]

Hi everybody,

I have upgraded from PROXMOX 3.4 to 4.2 and then I have viewed that I have not backup of some CT OpenVZ to migrate to LXC.

I have the CT in /vz/private/200/ with all files inside.

Is there any way to migrate from OpenVZ (/vz/private/200) to LXC if I have not a backup of CT 200?

I know that in KVM, if I create a VM and then I overwrite the 'file-disk.raw' with the file of another VM KVM, it works well.

Is there something similar to this to convert manually from OpenVZ to LXC if I have not a backup of CT?


Best regards,

Ramses

 

[LnxBil]

Have you already looked at this page?

https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC

It describes the necessary steps.

 

[ramses]

Have you already looked at this page?

https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC

It describes the necessary steps.

LnxBil, yes, but in this procedure I need to have a backup of CT OpenVZ created with vzdump previously, but I have some CT that I have not done the backup.

Know anybody a procedure to do the convert if I have not done the backup of a container OpenVZ?


Best regards,

Ramses

 

[LnxBil]

Two options:

• You can create a container with the same OS and rsync the OpenVZ data into the LXC. Afterwards do the same steps that are on the previously mentioned page
• Install the older version with OpenVZ on another machine (e.g. inside your current Proxmox) and copy the OpenVZ folder and config in, do the backup and import in your new Proxmox.

 

[ramses]

Two options:

• You can create a container with the same OS and rsync the OpenVZ data into the LXC. Afterwards do the same steps that are on the previously mentioned page
• Install the older version with OpenVZ on another machine (e.g. inside your current Proxmox) and copy the OpenVZ folder and config in, do the backup and import in your new Proxmox.

LnxBil, very thanks by the answer.

I have done this:

- Create a LXC Container with the same OS that had the old OpenVZ Container.

- Access to the new LXC Container (1600).

- Install rsync package.

- Execute rsynk with this line in the new LXC Container:

rsync -vaz --delete -e 'ssh -p 1111' root@<source-PROXMOX-server>:/vz/private/600 / --exclude '/proc/*' --exclude '/dev/*' --exclude '/sys/*' --exclude '/tmp/*'

** Note: I put (-e 'ssh -p 1111') in the previous line because I have the SSH Service in the 1111 port of the PROXMOX Server.

- Remove the Network Interface of LXC Container from PROXMOX.

- Add the new Network Interface of LXC Container form PROXMOX Console with this line:

pct set 1600 -net0 name=eth0,bridge=vmbr0,ip=192.168.20.90/24,gw=192.168.20.10


Best regards,

Ramses

 

[LnxBil]

You did this from inside your container? It's better to do it from outside and in non-started mode. Then you do not have to exclude the runtime directories. I'd also suggest to use '-x' and '--numeric-ids'.

But glad it worked.

 

[ramses]

You did this from inside your container? It's better to do it from outside and in non-started mode. Then you do not have to exclude the runtime directories. I'd also suggest to use '-x' and '--numeric-ids'.

But glad it worked.

LnxBil, can you tell me where are the content of LXC Containers when they are stopped?
Can you explain me how to do that?
I don't understand, I am very clumsy or newbie with PROXMOX.

Best regards,
Ramses

 

[fabian]

you can just do a "pct mount CTID" to mount a container's volumes to /var/lib/lxc/CTID/rootfs/

 

[LnxBil]

That depends on the used storage backend. If you choose a file-based storage backend (e.g. directory, ZFS) it is mounted, e.g. for ZFS you'll have "real" mount points:

Filesystem                               Size  Used Avail Use% Mounted on
...
zpool/proxmox/subvol-100-disk-1          121G   52G   70G  43% /zpool/proxmox/subvol-100-disk-1
zpool/proxmox/subvol-1003-disk-1         8.0G  1.5G  6.6G  19% /zpool/proxmox/subvol-1003-disk-1
zpool/proxmox/subvol-1004-disk-1         8.0G  1.4G  6.7G  17% /zpool/proxmox/subvol-1004-disk-1
zpool/proxmox/subvol-1005-disk-1         4.0G  1.1G  3.0G  27% /zpool/proxmox/subvol-1005-disk-1
zpool/proxmox/subvol-1006-disk-1         8.0G  346M  7.7G   5% /zpool/proxmox/subvol-1006-disk-1
zpool/proxmox/subvol-1007-disk-1         4.0G  315M  3.7G   8% /zpool/proxmox/subvol-1007-disk-1
zpool/proxmox/subvol-1008-disk-1         4.0G  703M  3.4G  18% /zpool/proxmox/subvol-1008-disk-1

For directory-based containers, you'll have subfolders inside your specified directory sub-folders.

If you have block storage device like LVM, Ceph you have to mount it yourself. Then you'll have to mount it manually.

 

[fabian]

or you can just use "pct mount", which will follow the exact same mounting procedure used when starting the container, but does not "hide" the mountpoints in a different name space.