You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The docker client can connect to a remote daemon using TLS, which is often easier to setup than ssh. It would be great if this was supported by lazydocker.
To Reproduce
Steps to reproduce the behavior:
Create a docker context using TLS:
docker context create my-context --docker "host=tcp://<host>:2376,ca=<path>,cert=<path>,key=<path>
docker use my-context
Launch lazydocker
We get the error Docker event stream returned error: Error response from daemon: Client sent an HTTP request to an HTTPS.
Expected behaviour
Lazydocker should connect to the daemon and work normally.
Workaround
Use socat to map the TLS socket to a local UNIX socket:
Describe the bug
The docker client can connect to a remote daemon using TLS, which is often easier to setup than ssh. It would be great if this was supported by lazydocker.
To Reproduce
Steps to reproduce the behavior:
Docker event stream returned error: Error response from daemon: Client sent an HTTP request to an HTTPS
.Expected behaviour
Lazydocker should connect to the daemon and work normally.
Workaround
Use
socat
to map the TLS socket to a local UNIX socket:Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: