Hi - Please let us know if that does not suffice, and we need to do the
fallback when lxc detects -c is not a device. I'll remove the lxc task
in the meantime.
** No longer affects: lxc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subsc
Tested on a precise lxc container I have:
it seems we could try with -L (or even better --console-log) and fall
back to -c (or --console) if that fails with exit code 1 (we could even
check the output for "invalid option".
ubuntu@clean-precise:~$ lxc-start -n foo -L omg
lxc-start: invalid o
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/13483
