Comment 1 for bug 1580612

After quite a bit of investigation, I found that there is already a python3-pylxd API in development by the maintainers of LXD. Instead of rolling our own API and duplicate work, we should use that instead.

However, one of the most important pieces is missing form pylxd- the actual executing of commands inside the LXD container. There is a very minimal exec function, but offers no process control nor any access to stdin, stdout, and stderr. There is a comment in that part of the pylxd code that says it needs to be expanded in the future.

I think we should wait on pylxd to mature some more before moving forward with this.