jesseduffield / jesseduffield/lazydocker

using DOCKER_HOST: ssh tunneled socket never became available

Open
#591 11 comments 8 reactions 0 assignees View on GitHub
bug
Dominant language
Go
Stars
52.8k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

**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**
```
$ lazydocker
2024/11/16 03:10:19 tunnel ssh docker host: ssh tunneled socket never became available: context deadline exceeded
```

**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: 152b36577137fd95f288e12cee5fd6d857a2d101
OS: linux
Arch: amd64

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.