The problem is that docker is not ready until the file start.sh is fully executed! Because of that, docker-compose fails with message:
Couldn't connect to Docker daemon at http+docker://localunixsocket - is it running? If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.
Any idea? Is there an option to auto-run some scripts at the time user docker is ready? For obvious reason I don’t want to run the app as system service.
Also, if I use docker-compose manually, I can see the logs of the whole application using docker-compose -p myapp logs, which I am not sure would be possible if I bootstrap my app using the cloud config. Or is it?
But unfortunately, you cannot login and use the same cloud-config to launch services using those credentials. I’ve created an enhancement request for it.