[SOLVED] Unable to start LXC container after moving storage

Virt

Active Member
Oct 3, 2014
25
0
41
I have an LXC container (Ubuntu 16.04) that refuses to start after moving it using the GUI.

Log from lxc-start:
Code:
lxc-start 103 20180820144828.681 ERROR    lxc_conf - conf.c:run_buffer:347 - Script exited with status 255
lxc-start 103 20180820144828.681 ERROR    lxc_start - start.c:lxc_init:815 - Failed to run lxc.hook.pre-start for container "103"
lxc-start 103 20180820144828.681 ERROR    lxc_start - start.c:__lxc_start:1849 - Failed to initialize container "103"
lxc-start 103 20180820145033.822 ERROR    lxc_conf - conf.c:run_buffer:347 - Script exited with status 255
lxc-start 103 20180820145033.822 ERROR    lxc_start - start.c:lxc_init:815 - Failed to run lxc.hook.pre-start for container "103"
lxc-start 103 20180820145033.822 ERROR    lxc_start - start.c:__lxc_start:1849 - Failed to initialize container "103"
lxc-start 103 20180820145750.699 INFO     lxc_lsm - lsm/lsm.c:lsm_init:46 - LSM security driver AppArmor
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:parse_config_v2:585 - processing: .reject_force_umount  # comment this to allow umount -f;  not recommended
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:parse_config_v2:761 - Adding native rule for reject_force_umount  # comment this to allow umount -f;  not recommended action 0(kill)
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:411 - Setting Seccomp rule to reject force umounts
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:parse_config_v2:765 - Adding compat rule for reject_force_umount action 0(kill)
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:411 - Setting Seccomp rule to reject force umounts
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:411 - Setting Seccomp rule to reject force umounts
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:parse_config_v2:585 - processing: .[all]
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:parse_config_v2:585 - processing: .kexec_load errno 1
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:parse_config_v2:761 - Adding native rule for kexec_load errno 1 action 327681(errno)
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:parse_config_v2:765 - Adding compat rule for kexec_load action 327681(errno)
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:parse_config_v2:585 - processing: .open_by_handle_at errno 1
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:parse_config_v2:761 - Adding native rule for open_by_handle_at errno 1 action 327681(errno)
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:parse_config_v2:765 - Adding compat rule for open_by_handle_at action 327681(errno)
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:parse_config_v2:585 - processing: .init_module errno 1
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:parse_config_v2:761 - Adding native rule for init_module errno 1 action 327681(errno)
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:parse_config_v2:765 - Adding compat rule for init_module action 327681(errno)
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:parse_config_v2:585 - processing: .finit_module errno 1
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:parse_config_v2:761 - Adding native rule for finit_module errno 1 action 327681(errno)
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:parse_config_v2:765 - Adding compat rule for finit_module action 327681(errno)
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:parse_config_v2:585 - processing: .delete_module errno 1
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:parse_config_v2:761 - Adding native rule for delete_module errno 1 action 327681(errno)
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:parse_config_v2:765 - Adding compat rule for delete_module action 327681(errno)
lxc-start 103 20180820145750.699 INFO     lxc_seccomp - seccomp.c:parse_config_v2:775 - Merging in the compat Seccomp ctx into the main one
lxc-start 103 20180820145750.699 INFO     lxc_conf - conf.c:run_script_argv:368 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "103", config section "lxc"
lxc-start 103 20180820145751.553 DEBUG    lxc_conf - conf.c:run_buffer:338 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 103 lxc pre-start with output: got unknown DISTRIB_ID

lxc-start 103 20180820145751.566 ERROR    lxc_conf - conf.c:run_buffer:347 - Script exited with status 255
lxc-start 103 20180820145751.566 ERROR    lxc_start - start.c:lxc_init:815 - Failed to run lxc.hook.pre-start for container "103"
lxc-start 103 20180820145751.566 ERROR    lxc_start - start.c:__lxc_start:1849 - Failed to initialize container "103"

I have other containers on the same datastore that have no issues. For whatever reason, it's only this one container.
 
lxc-start 103 20180820145751.553 DEBUG lxc_conf - conf.c:run_buffer:338 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 103 lxc pre-start with output: got unknown DISTRIB_ID
what is the content of the file /etc/lsb-release of the container? (you can temporarily mount the fs of the ct with 'pct mount' and then unmount with pct unmount)
 
what is the content of the file /etc/lsb-release of the container? (you can temporarily mount the fs of the ct with 'pct mount' and then unmount with pct unmount)
Looks like it's binary, cat produces gibberish. Perhaps I need to replace it with a copy from the other image?
 
I was able to get it up and running by manually recreating the container using the previous image.
The previous transfer had corrupted the image and I was able to move it the second try.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!