I can give you the issue I filed with lxc/lxc as an example :
https://github.com/lxc/lxc/issues/819
If you try to create a container using the following command:
lxc-create -t download -n lxc10009 -f lxc10009.conf -- -d ubuntu -r
xenial -a amd64
And the config file contain a “lxc.roofs
I agree with your comments and the fact that the team is busy working lxc
v2, but I wanted to get a sense of whether it was a problem everyone is
facing and that the lxc team are aware of. I didn't look into the codebase
for logging yet and I'm not a C programmer (anymore), but I would like to
give
Dear Akshay,
I do agree with you and find this behaviour a bit annoying, yet I believe
"patches welcome" response will follow shortly :)
On a more serious note:
As I skimmed over LXC code a while ago, it seems LXC bails out on first
error that occurs. This means that implementing your suggestion
I agree that lxc-start need better error logging, not only for lxc-start, but
for most lxc-* tools. But on the other hand, dev properly are too busy
straighten out other issue for lxc v2.
Regarding your issue, you can try following:
lxc-start-ephemeral -n e1 -l 9 -o test -d
The “-l 9”
Hello lxc users,
After having used lxc for a while now, I've realized that when the
container fails to start, it fails with a very generic message as follows:
$ lxc-start -n test
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 346 To get more details
