LXC containers - how to restore them?

[Big_boss]

@anon50890781

Guys about LXC running with your old LXC instance

Linux Containers - LXC - Manpages - lxc-update-config.1

lxc-update-config detects any legacy configuration keys in the given config file and will replace them with the appropriate new configuration keys.

lxc-update-config will first create a backup of the old config file in the same directory and name it config.backup and then update the original config file in place. In case the update fails to apply or leads to an invalid config file that cannot be used to start a container users can either compare config with config.backup and try to manually repair any the invalid configuration keys or simply rollback to the legacy configuration file by copying config.backup to config.

The problem is, there is no lxc-update-config package as far as i could search.

opkg find lxc

root@K-Router:~# opkg find lxc
lxc - 2.1.1-2.0 - LXC is the userspace control package for Linux Containers, a lightweight
 virtual system mechanism sometimes described as "chroot on steroids".
root@K-Router:~# opkg find lxc*
lxc - 2.1.1-2.0 - LXC is the userspace control package for Linux Containers, a lightweight
 virtual system mechanism sometimes described as "chroot on steroids".
lxc-attach - 2.1.1-2.1 - Utility lxc-attach from the LXC userspace tools
lxc-auto - 2.1.1-2.0 - LXC is the userspace control package for Linux Containers, a lightweight
 virtual system mechanism sometimes described as "chroot on steroids".
 This package adds and initscript for starting and stopping the containers
 on boot and shutdown.
lxc-autostart - 2.1.1-2.1 - Utility lxc-autostart from the LXC userspace tools
lxc-cgroup - 2.1.1-2.1 - Utility lxc-cgroup from the LXC userspace tools
lxc-checkconfig - 2.1.1-2.0 - Utility lxc-checkconfig from the LXC userspace tools
lxc-common - 2.1.1-2.0 - LXC common files
lxc-config - 2.1.1-2.1 - Utility lxc-config from the LXC userspace tools
lxc-configs - 2.1.1-2.0 - LXC virtual machine common config files
lxc-console - 2.1.1-2.1 - Utility lxc-console from the LXC userspace tools
lxc-copy - 2.1.1-2.1 - Utility lxc-copy from the LXC userspace tools
lxc-create - 2.1.1-2.1 - Utility lxc-create from the LXC userspace tools
lxc-destroy - 2.1.1-2.1 - Utility lxc-destroy from the LXC userspace tools
lxc-device - 2.1.1-2.1 - Utility lxc-device from the LXC userspace tools
lxc-execute - 2.1.1-2.1 - Utility lxc-execute from the LXC userspace tools
lxc-freeze - 2.1.1-2.1 - Utility lxc-freeze from the LXC userspace tools
lxc-hooks - 2.1.1-2.0 - LXC virtual machine hooks
lxc-info - 2.1.1-2.1 - Utility lxc-info from the LXC userspace tools
lxc-init - 2.1.1-2.1 - LXC Lua bindings
lxc-ls - 2.1.1-2.1 - Utility lxc-ls from the LXC userspace tools
lxc-lua - 2.1.1-2.1 - LXC Lua bindings
lxc-monitor - 2.1.1-2.1 - Utility lxc-monitor from the LXC userspace tools
lxc-monitord - 2.1.1-2.1 - Utility lxc-monitord from the LXC userspace tools
lxc-snapshot - 2.1.1-2.1 - Utility lxc-snapshot from the LXC userspace tools
lxc-start - 2.1.1-2.1 - Utility lxc-start from the LXC userspace tools
lxc-stop - 2.1.1-2.1 - Utility lxc-stop from the LXC userspace tools
lxc-templates - 2.1.1-2.0 - LXC virtual machine templates
lxc-top - 2.1.1-2.1 - Utility lxc-top from the LXC userspace tools
lxc-unfreeze - 2.1.1-2.1 - Utility lxc-unfreeze from the LXC userspace tools
lxc-unprivileged - 2.1.1-2.0 - Support for unprivileged containers requires newuidmap and newguidmap.
 This package makes sure they are available & have correct permissions.
lxc-unshare - 2.1.1-2.1 - Utility lxc-unshare from the LXC userspace tools
lxc-user-nic - 2.1.1-2.1 - Utility lxc-user-nic from the LXC userspace tools
lxc-usernsexec - 2.1.1-2.1 - Utility lxc-usernsexec from the LXC userspace tools
lxc-wait - 2.1.1-2.1 - Utility lxc-wait from the LXC userspace tools

@anon50890781

Big_boss:

Although solved the first problem, now i am being stopped by another error.

You could, as suggested, run the container in foreground mode (perhaps also add --logfile) and see if additional information is displayed.

From the above bits is seems like a privilege issue in the namespace.

The foreground mode is just putting the output that i could read in the log file. Sadky it is the same output as i posted earlier.