-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to connect to docker Provider over ssh (works outside of Pulumi) #1293
Comments
From the looks of things, Pulumi is lying to me. The first time that I am invoking this function, waiting for the node to install Docker, and create the network I am looking up:
As far as I can tell, there is no other way to do this without a retry loop. But if Pulumi isn't going to bother invoking I am attempting to connect once every 5 seconds for 3 minutes. The remote host begins responding ~1 minute after launch, but by that time Pulumi stops trying to invoke ssh... I can see that |
@cowwoc your provider's SSH setup looks correct, but I suspect only the build path is currently handling SSH correctly. The If you're trying to use the remote to build images, it might be simpler to configure a remote builder and use that with the docker-build provider. Edit: I wasn't able to reproduce this in #1297. That modifies our remote SSH test to also query the network and it seems to work... |
Describe what happened
I've been pulling my hair out trying to figure out why Pulumi is unable to connect to a remote docker engine using ssh (the connection gets refused) but when I take the exact same command-line and run it from cmd.exe it works just fine.
Sample program
Log output
Pulumi output:
Output when running
ssh -vvv -i C:/Users/Gili/.ssh/licensed-pulumi.pem -o StrictHostKeyChecking=no -o UserKnownHostsFile=\\.\NUL -o ConnectTimeout=30 -l root -p 22 -- 134.209.213.246 docker system dial-stdio
fromcmd.exe
:I diffed the two outputs and as far as I can tell, they start out the same except that Pulumi gets a "connection refused" error while cmd.exe is able to connect without any problems.
Affected Resource(s)
No response
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: