We can now configure whether rancher should wait for container to be running or stopped.
Basically, async tasks are done by celery, and tasks that are directly run by rancher are potentially synchronous, but as they take a while, the api did not wait for their completion, not even for their succesfull launch. (Making them async might be a solution on the long run).
For the moment, this code lets the user switch on that the endpoint waits for either the container to be running or the container to be finished. Useful for debugging or first time installation.
(It took me a while to understand why I got success responses, but no containers were created.)
We can now configure whether rancher should wait for container to be running or stopped. Basically, async tasks are done by celery, and tasks that are directly run by rancher are potentially synchronous, but as they take a while, the api did not wait for their completion, not even for their succesfull launch. (Making them async might be a solution on the long run).
For the moment, this code lets the user switch on that the endpoint waits for either the container to be running or the container to be finished. Useful for debugging or first time installation.
(It took me a while to understand why I got success responses, but no containers were created.)