Fix ssh context not working

[peauc]

Fix issue as described in #559

[peauc]

It seems that I was missing the code of the PR #511 that was merged early June.
I still have the issue using my now fresh copy of master.

The code of this branch is a bit cleaner and now works for me

[peauc]

I'll get to the tests in a few days.

[jesseduffield]

See comments :)

[jesseduffield]

Could you explain the rationale behind these changes? I'm not clear on the reasoning

[peauc]

I just wired it correctly for the SSH connection to work.
I'll rework it so its clearer and doesn't rely on a modified docker host env variable.

[peauc]

Hey @jesseduffield took over 6 months to get some free time but now that I'm in vacation... :D

The rationale is that ATM ssh tunneling with docker context over lazydocker is broken. There are a few issues regarding this see this link
In my opinion those issues are due to an edge case in the current implementation of the ssh tunneling & docker host parsing.
I've rewritten a few parts to both make it simpler and more robust, tell me what you think :)

[bill-mccormick-dg]

Anyway this get's merged soon @jesseduffield? I'd love to have it.

[wpcarro]

What's the latest here?

[peauc]

@wpcarro waiting for merge on this repo. Works on my fork.

[bill-mccormick-dg]

Sorry haven't tried this. I'm on a work break and not sure I'll have a chance to look at it until next week. BTW...my use case is from WSL.

…

On Fri, Nov 21, 2025, 6:16 PM PÉAU Clément ***@***.***> wrote: *peauc* left a comment (jesseduffield/lazydocker#577) <#577 (comment)> @wpcarro <https://github.com/wpcarro> waiting for merge on this repo. Works on my fork. — Reply to this email directly, view it on GitHub <#577 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALAW2DFQPDC5JKT4Z3ORLD356TNNAVCNFSM6AAAAABNQ3LW7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNRVGA3DSOBWGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[peauc]

If anyone is interested in this thread. I've released lazydocker-ng with a bunch of fixes that where never merged.

[francoiscabrol]

I am facing the same issue. Thank you, @peauc, for providing a solution. Would it be possible to review it again, @jesseduffield? I have checked with the fork, and the issue is gone. It would be awesome to have it merge in the main project!

[francoiscabrol]

I have an update: maybe my issue was a bit different. My issue was about getting ssh tunneled socket never became available: context deadline exceeded (like #591) running DOCKER_HOST=ssh://user@domain:2222 ~/go/bin/lazydocker
With the fork lazydocker-ng, this command works without error.

But I realize that I can actually connect through ssh with the main project if I omit the port in the command DOCKER_HOST=ssh://user@domain ~/go/bin/lazydocker

[peauc]

@francoiscabrol, yeah there is an issue with the way the docker host is consumed.
Your workaround is a good one if you have the default ssh port.

[vlanx]

I have an update: maybe my issue was a bit different. My issue was about getting ssh tunneled socket never became available: context deadline exceeded (like #591) running DOCKER_HOST=ssh://user@domain:2222 ~/go/bin/lazydocker With the fork lazydocker-ng, this command works without error.

But I realize that I can actually connect through ssh with the main project if I omit the port in the command DOCKER_HOST=ssh://user@domain ~/go/bin/lazydocker

This did not work for me either, port or no port.
What did though, was creating an entry in my ssh config file like so:

Host remote-context
  Hostname 10.16.10.1
  User ubuntu

Then, the DOCKER_HOST url can be DOCKER_HOST=ssh://remote-context lazydocker which makes it work for me.
I've wrapped into a zsh helper function and autocompletes with ssh aliases too.

lzd() {
  local host_alias="$1"

  if [ -z "$host_alias" ]; then
    echo "usage: lzd <ssh-host-alias>"
    return 1
  fi

  DOCKER_HOST="ssh://$host_alias" lazydocker
}

compdef lzd=ssh