Comment 0 for bug 1656985

I'm seeing "Error calling external process" when mojo attempts to start the container using a non-existent config file:

CalledProcessError: Command '['sudo', 'lxc-start', '-d', '-n', 'mojo-my-project.xenial', '-f', '/var/lib/lxc/mojo-my-project.xenial/config.nonet']' returned non-zero exit status 1

$ sudo lxc-start -d -n mojo-u1-software-center-agent.xenial -f /var/lib/lxc/mojo-my-project.xenial/config.nonet
lxc-start: tools/lxc_start.c: main: 258 Failed to load rcfile

$ ls -al /var/lib/lxc/mojo-my-project.xenial/
total 16
drwxrwxr-x 3 root root 4096 Jan 16 23:32 .
drwxr-xr-x 3 root mojo 4096 Jan 16 23:31 ..
-rw-r--r-- 1 root root 797 Jan 16 23:32 config
drwxr-xr-x 2 root root 4096 Jan 16 23:31 rootfs

I suspect LXCContainer.is_setup should be checking that the required config is written before it decides to return True (so that LXCContainer.setup() is not called - but not 100%). Full traceback at [1]

[1] https://pastebin.canonical.com/176092/ (sorry for the internal link)