Thanks, if it turns out there is more that lxc could do please do reply here or open a github issue.
Doing more in the C api woudl be tough, as we'd presumably need to allocate memory for the error msg which the caller would need to free. Returning more in the python API could be doable if it could control the lxc.logfile and present the output after a failure, but since the caller may want to set those himself it's not so simple. Not sure what to do with the status of this bug. If we re-title it general failure logging improvements then it definately could be Confirmed. Otherwise it may be Invalid, not sure. Either way, marking Wishlist for now. ** Changed in: lxc (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1542438 Title: Python LXC api needs to be much better at error reporting Status in lxc package in Ubuntu: New Bug description: I use the Python API extensively on the lp:libertine project. However, when there is an error somewhere in the LXC layer, the only thing that is returned is False which is not very useful when trying to figure out what has gone wrong. For example, I try to use the Container.create() method and it is failing However, when I try using the lxc-create CLI tool using the same exact parameters, it works. Since the Python API does not have an error output, I'm having a very difficult time figuring out why the Python create is failing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1542438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
