-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
using DOCKER_HOST: ssh tunneled socket never became available #591
Comments
Does e.g. |
Yes |
yes it does |
Having same issue in 0.24.1 of lazydocker and Docker version 27.3.1 |
Having the same issue in 0.24.1 of lazydocker and Docker version 27.5.1. Lazydocker only works when the docker context isn't ssh |
any update on this ? |
Same issue here. Local Docker works, ssh context not :( |
works again on version 0.24.1 |
@tan-wei-xin-alez not for me sadly |
Nope, does not work in 0.24.1 under macos for me. The issue still persists. |
Describe the bug
THE BUG :
$ lazydocker
2024/11/16 03:10:19 tunnel ssh docker host: ssh tunneled socket never became available: context deadline exceeded
I'm using DOCKER_HOST="ssh://something"
To Reproduce
Create a debian server with docker running
Create a debian client with docker client (install docker then systemctl stop docker)
Server: systemctl start docker
Client: ssh-copy-id to server
Client: export DOCKER_HOST="ssh://target"
Client: lazydocker
Expected behaviour
Start the lazydocker program.
Screenshots
Desktop (please complete the following information):
Client: Linux i3 6.1.0-27-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.115-1 (2024-11-01) x86_64 GNU/Linux
Server: Linux nas 5.10.0-33-amd64 #1 SMP Debian 5.10.226-1 (2024-10-03) x86_64 GNU/Linux
Client is "debian12.8 X11 i3wm alacritty tmux docker27.3.1"
Server is "debian11.11 no-gui docker27.3.1"
lazydocker is
Version: 0.23.3
Date: 2024-05-26T04:20:34Z
BuildSource: binaryRelease
Commit: 152b365
OS: linux
Arch: amd64
The text was updated successfully, but these errors were encountered: