Create Environment fails using Docker Toolbox 1.12 #30
Comments
|
Hi @teamschwarz, could you please provide more details, about how exactly (step-by-step) you have created ADOP stack, hard to say without details. OS and Docker version also would be useful. Thank you. |
|
Windows 10. I've been using ADOP heavily on Docker Toolbox 1.11.x for months. The problem started after upgrading to 1.12. I run quickstart (git clone of adop-docker-compose a few days ago) to bring up the environment. i create a workspace/project and then load the Java cartridge (or use the one inside the Example workspace). Create environment always fails with the text above. Also, i think part of the same problem is trying to run the Chef Cartridge. the second step of the Chef pipeline: Sanity_Test -- error is: |
|
I can confirm this issue, the same for me on Docker Version 1.12.0-a (build: 11213) @teamschwarz could you please check this workaround, In this case it should work, add sleep here https://github.com/Accenture/adop-docker-compose/blob/master/cmd/compose#L230 And in root folder of docker-compose repository, please run this command: The output should be something like: If so, you can re-run "Create_Environment" job or any other, your stack should work just as expected. @nickdgriffin @SachinKSingh28: |
|
i tried what you suggested but it did not work.
|
new output running docker 1.12 on a windows 10 box, using docker quickstart running as administrator:$ ./adop compose gen-certs //root/.docker |
|
Does "/c/Users/richard.a.schwarz/.docker/machine/certs/ca.pem" actually exist (both on the filesystem and from the perspective of the shell)? What version of Docker Machine is in use as well please? |
|
docker 1.12. i worked with Anton on the phone, and the error message above was where were left off-temporarily stuck. i did check that the file was there, and had the correct contents. my docker terminal was launched as Admin. on a separate note: I accidentally closed the issue, so had to reopen it. |
|
Docker 1.12 is the version of the Engine/Toolbox not Machine, but I'm going to install Docker Toolbox 1.12.1 on my Windows 10 PC at home and see if I can reproduce for a local machine (as it's not clear from the above what actual quickstart comand was run). I think this issue relates to Docker Machine though, as that's what creates the keys in question. So, this is what I've done:
Versions:
Output from docker info: Output from quickstart: After I tested the above, I also manually re-ran gen-certs as well: So as far as I can see everything is fine, which makes me think either:
|
|
Hi, is this still an issue? If not, we could close it. |
Error: Message is below. Running
eval $(docker-machine env default)doesn't help::::::::::::::::::::
TLS configuration is invalid - make sure your DOCKER_TLS_VERIFY and DOCKER_CERT_PATH are set correctly.
You might need to run eval "$(docker-machine env default)"
Build step 'Execute shell' marked build as failure
[ssh-agent] Stopped.
Finished: FAILURE
The text was updated successfully, but these errors were encountered: