Skip to content
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

ssh context timed out (workaround: ControlPersist) #315

Closed
AkihiroSuda opened this issue Jun 23, 2020 · 3 comments
Closed

ssh context timed out (workaround: ControlPersist) #315

AkihiroSuda opened this issue Jun 23, 2020 · 3 comments
Labels
kind/bug Something isn't working

Comments

@AkihiroSuda
Copy link
Collaborator

AkihiroSuda commented Jun 23, 2020

$ docker context create my-arm-instance --docker host=ssh://me@my-arm-instance
$ docker buildx ls
NAME/NODE         DRIVER/ENDPOINT  STATUS PLATFORMS
my-arm-instance   docker                  
  my-arm-instance my-arm-instance  listing workers: failed to list workers: rpc error: code = DeadlineExceeded desc = context deadline exceeded
...

A workaround is to set ControlPersist in ~/.ssh/config:

ControlMaster auto
ControlPath ~/.ssh/control-%C
ControlPersist yes

This workaroud is not needed for docker --context=my-arm-instance info|version|run.

BuildX version: v0.4.1

@AkihiroSuda AkihiroSuda added the kind/bug Something isn't working label Jun 23, 2020
@tonistiigi
Copy link
Member

Is it just that making a new connection takes longer than the timeout or something else? One way to try would be to make the timeout configurable.

@tonistiigi
Copy link
Member

Is this duplicate of #358 ?

@AkihiroSuda
Copy link
Collaborator Author

Probably yes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants