Ok.
I know.
This is very weird and very likely to have nothing to do with lxc/lxd at all.
I am asking here exactly because it is very strange and insight from knowledgeable people could make the difference.
I am trying to write a python script to automatize container handling.
It generally works quite well but there’s ONE command that hangs completely if/when used under PyCharm (it works perfectly fine if run from the command line).
this minimal example:
import subprocess
image = 'images:ubuntu/bionic'
name = 'name'
r = subprocess.run(['lxc', 'launch', image, name])
print(r)
never prints anything (if and only if run under PyCharm!) and the container is not created at all.
What kind of PyCharm bug could justify such a behavior?
Other commands (e.g.: lxc list, lxc exec ..., lxc stop ... and even lxc delete ...) seem to work without problems; What’s so special in lxc launch ...??
Can confirm what you are saying. Spent an hour trying to fix this but go nowhere!
Interestingly the command never makes it to the point where it hits the API (you can run lxc monitor --debug --pretty in another shell to confirm this).