*** This bug is a duplicate of bug 1181136 ***
https://bugs.launchpad.net/bugs/1181136
sorry, no I meant that it's failing to get logs the content from stderr
or stdout (and so, we don't see the logs if something failed), as per
the duplicate :)
--
You received this bug notification because
*** This bug is a duplicate of bug 1181136 ***
https://bugs.launchpad.net/bugs/1181136
** This bug has been marked a duplicate of bug 1181136
Empty log file when a container is started with the API
--
You received this bug notification because you are a member of Ubuntu
Server Team,
*** This bug is a duplicate of bug 1181136 ***
https://bugs.launchpad.net/bugs/1181136
did you try with the python bindings (hence why I duplicated it to the
other bug report)?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
*** This bug is a duplicate of bug 1181136 ***
https://bugs.launchpad.net/bugs/1181136
Do you mean c-start(c) in python bindings, with
lxc.loglevel = debug
lxc.logfile = /tmp/foo
in container config, fails? If so that's very interesting. If not,
then it matches my current expectation.
