Unable to create machines since authentication update

[khast3x]

Error message:

[~] user:$ export PWD_URL= `URL after auth`
[~] user:$ docker-machine create -d pwd  pwd1
Running pre-create checks...
Creating machine...
Error creating machine: Error in driver during machine creation: Could not create instance <nil> &{404 Not Found 404 HTTP/1.1 1 1 map[X-Content-Type-Options:[nosniff] Date:[Fri, 10 Nov 2017 00:04:39 GMT] Content-Length:[19] Content-Type:[text/plain; charset=utf-8]] 0xc420108980 19 [] false false map[] 0xc42000b500 <nil>}

[marcosnils]

Right. this doesn't work for the moment. We'll fix it eventually

[matthiasnoback]

It would be very cool if this could be fixed! (also: thanks for this awesome tool)

[lima1909]

Hi, is this problem fixed? (this is really a great tool!)

[marcosnils]

Not yet

[andrevtg]

I know this is not the same thing but some workarounds to improve PWD user experience exist:

• Current PWD has a SSH button that copies into the clipboard a SSH command that works nicely. Run this command in a terminal and you'll working in the PW instance without the browser. Example:

ssh ip172-18-0-19-heregoesthesessionidshowninpwd@direct.labs.play-with-docker.com

• If this SSH interface is unstable (sometimes it is, maybe due to slow connections), you can use the DOCKER_HOST variable to instruct your Docker client to talk directly to the PWD engine. Use the same SSH URL generated in the SSH button, but modify it like below (added "tcp://" and replaced the "@" by "."):

export DOCKER_HOST=tcp://ip172-18-0-19-heregoesthesessionidshowninpwd.direct.labs.play-with-docker.com

Done! Your "docker" commands will talk to your PWD instance instead of your local Docker engine.

[marcosnils]

hey @andrevtg, thx for helping out and adding some alternatives. Just wanted to mention that it's not necessary to run a container with socat in the PWD instances in order to access the daemon.

You can just set the DOCKER_HOST variable like this: tcp://ip172-18-0-19-<session_id>.direct.labs.play-with-docker.com and it'll work without running anything in the instance.

[andrevtg]

That was a facepalm moment I didn't have in years. Editing my post to fix it...

I noticed that this "dashed" IP is no longer the IP shown in the PWD user interface, but instead the one present in the SSH URL.

[zgfh]

try to fix this: #13

[sqlaz]

Hi Marcos - Wondering if you had an update on this? Looks like the driver is still looking for the http and not https, and comes up with the 404 error. Even setting the PWD_SSL_PORT does not help. Please advise. Thanks!

[Hlavi71]

Hi, is this problem fixed? Because it does not work my machine.

[gohmc]

hey @andrevtg, thx for helping out and adding some alternatives. Just wanted to mention that it's not necessary to run a container with socat in the PWD instances in order to access the daemon.

You can just set the DOCKER_HOST variable like this: tcp://ip172-18-0-19-<session_id>.direct.labs.play-with-docker.com and it'll work without running anything in the instance.

Extend the ssh command copied from the session page with -i ~/.docker/machine/certs/key.pem do the trick as well.