Comment 3 for bug 1542438

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.