lxc-attach stopped working for docker containers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Saucy |
Fix Released
|
High
|
Unassigned |
Bug Description
I think https:/
The main blocker is that docker containers are hitted by https:/
Thanks !
=======
1. impact: containers starte with a custom configuration file cannot be controlled the same way as normal containers. Instead a custom lxcpath, formed by appending "_anon" to the real lxcpath, must be apssed to lxc-console, lxc-stop, lxc-attach, etc.
2. development fix: don't specify a custom lxcpath
3. stable fix: same as dev fix
4. test case:
sudo lxc-create -t ubuntu -n u1
sudo lxc-start -n u1 -f /var/lib/
sudo lxc-info -n u1
# shows not running
5. regression potential: this is cherrypicked from upstream and should have no regressions.
=======
Related branches
description: | updated |
Thanks - I assume that the docker containers are started with 'lxc-start <...> -f cofnigfile'. That is the trigger for the use of the anon lxcpath, which also caused autostart to fail. The git commit you cite is indeed the fix for this. I"ll fix this in trusty and SRU to saucy.