Note: With the latest 1.23.0 release, the Anbox Cloud documentation is moved to https://documentation.ubuntu.com/anbox-cloud/en/latest/. Hence, the information in this discourse post may be obsolete. The documentation posts on discourse will be unlisted and archived shortly.
Discourse will still be used for user engagement and release announcements.
When an instance is either initialised with the amc init (see Create an instance) command or stopped with the amc stop command (See Stop an instance), you must start it explicitly with the amc start command:
amc start <instance_id>
<instance_id> is the ID of the instance that you want to start.
Do not use the lxc command to manage an instance. Always use the amc command instead. In Anbox Cloud, instances have their own life cycle and using the lxc command to manage an instance can cause the instance to be out of sync.
By default, the amc start command waits 5 minutes for an instance to run before the operation times out. When starting an instance, you can specify a custom wait time with the --timeout option.
amc start <instance_id> --timeout 10m
When the --no-wait option is specified, the amc start command exits immediately after the instance starts and will not wait till it is running.
amc start <instance_id> --no-wait
Starting an instance that has stopped with an error status is is not allowed. Doing so would cause the amc start command to fail.