jesseduffield / jesseduffield/lazydocker

Lazydocker could do automatic docker host discovery on startup

Open
#455 2 comments 3 reactions 0 assignees View on GitHub
discussion
Dominant language
Go
Stars
52.8k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

Follow up on this 2 issues:
https://github.com/jesseduffield/lazydocker/issues/422
https://github.com/jesseduffield/lazydocker/issues/311

This is to start a discussion on whether lazydocker should support automatic docker host discovery.

The main pro for me is that when I run colima and then `docker ps` it works fine without extra tuning. But when I start lazydocker right after it fails. This can be confusing for people new to docker or unix systems in general. They picked lazydocker as an alternative to raw commands in console but face situation when raw commands are actually friendly (speaking solely of this case) because they can identify under the hood which docker host is used, but lazydocker cant.

So the proposal is to think about adding automatic docker host discovery on start up or add at least more info in the project docs or troubleshooting page.

PS: As colima gains its popularity this is going to become a common issue or stumbling stone on the very first run, which is not good for the project.

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.