It is impossible to migrate container if it has bind mount configured for it.
Migration fails with the following error:
[root@pcs ~]# pmigrate c 100500 c --ssh="-p 22" firstname.lastname@example.org<br> Connection to destination node (18.104.22.168) is successfully established<br> Moving/copying CT#100500 -> CT#100500, ,  ...<br> vzctl2_env_get_param(QUOTAUGIDLIMIT) return 12000000<br> Checking external bind mounts<br> /mnt/100500/wincoa:/mnt/wincoa<br> config ve contains ext bindmount: /mnt/100500/wincoa:/mnt/wincoa<br> Can't move/copy CT#100500 -> CT#100500, ,  : config ve contains ext bindmount:<br> /mnt/100500/wincoa:/mnt/wincoa
This limitation is intentional, it is a product design which prevents actions that could be harmful.
There are two general cases for this situation:
If your destination server has the necessary bind-mount already configured you can ignore the warning and use
--nodepsoption for migration:
# pmigrate <CTID> <IP.AD.DR.ES> --nodeps=bindmount
Note!: you can use the same option for
If destination doesn't have the bind-mount point configured, and you do not intend to use it, you can remove the mount point using following command:
# vzctl set <CTID> --bindmount_del <BIND_MOUNT> --save
Once bind-mount is removed you can retry the migration.