envsto load the environment variables.
@durango the error is a bit more complicated than I was expecting. Did some testing here with the image.
You are right, the error is not in the image but on provision steps implementation. In my tests they get fail sometimes (mainly to get code from bitbucket) until complete all steps.
A workaround for this (at least until we dont have an "advanced provision") is running all provision commands manually:
$ azk shell gambit # executar os comandos do provision
So let us know if you are getting get a minimally viable environment.
We know this is not the best way, after all the
provision is there to facilitate this, but it's our chance to debug it better to an environment where we have not done extensive testing in the case of the golang.
/etc/resolv.confwhen it starts the container. The correct way to do that is to pass the DNS config to
docker runas an argument, but
azkdoesn't implement that feature yet. We will update our backlog with this isssue.
azk start(depois do init, que identificou tudo direito)
azk startnovamente, mas dessa vez ele não subiu porque a máquina do postgresql estava, aparentemente, corrompida.
azk start --reprovision, mas não sei se é o certo e nem resolveu...