lxc script non-root errors can be confusing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
A trivial thing, but at least a couple of people have been confused by something like this, just being forgetful:
$ lxc-start -n lp
lxc-start: failed to cap_get_flag: Invalid argument
lxc-start: failed to create veth5HNAcN-
lxc-start: failed to create netdev
lxc-start: failed to create the network
lxc-start: failed to spawn 'lp'
lxc-start: No such file or directory - failed to remove cgroup '/sys/fs/
The fix is to simply use sudo. The error message does not communicate this clearly.
I'd suggest that the lxc scripts that need to be run as root (is that all of them except lxc-list?) have a "this script must be run as root" error message, or similar. It's a small thing, but I think it would be appreciated by users.
This seems related, but not identical, to bug 918327