Software
We've compiled a list of 7 free and paid alternatives to Lazydocker. The primary competitors include Rancher, Kubernetes. In addition to these, users also draw comparisons between Lazydocker and Nanobox, Portainer, Cockpit Project. Also you can look at other similar options here: About.
We've compiled a list of 7 free and paid alternatives to Lazydocker. The primary competitors include Rancher, Kubernetes. In addition to these, users also draw comparisons between Lazydocker and Nanobox, Portainer, Cockpit Project. Also you can look at other similar options here: About.
52
Rancher is a complete platform for running Docker applications in production.
50
39
Automate complex infrastructure tasks so you can get back to what really matters
38
Lightweight, open-source management UI for docker hosts or swam clusters.
22
20
14
5
A simple terminal UI for docker and docker-compose, written in Go with the gocui library.
A simple terminal UI for docker and docker-compose, written in Go with the gocui library.
Windows
Linux
Mac
Minor rant incoming: Something's not working? Maybe a service is down. docker-compose ps. Yep, it's that microservice that's still buggy. No issue, I'll just restart it: docker-compose restart. Okay now let's try again. Oh wait the issue is still there. Hmm. docker-compose ps. Right so the service must have just stopped immediately after starting. I probably would have known that if I was reading the log stream, but there is a lot of clutter in there from other services. I could get the logs for just that one service with docker compose logs --follow myservice but that dies everytime the service dies so I'd need to run that command every time I restart the service. I could alternatively run docker-compose up myservice and in that terminal window if the service is down I could just up it again, but now I've got one service hogging a terminal window even after I no longer care about its logs. I guess when I want to reclaim the terminal realestate I can do ctrl+P,Q, but... wait, that's not working for some reason. Should I use ctrl+C instead? I can't remember if that closes the foreground process or kills the actual service.
What a headache!
Memorising docker commands is hard. Memorising aliases is slightly less hard. Keeping track of your containers across multiple terminal windows is near impossible. What if you had all the information you needed in one terminal window with every common command living one keypress away (and the ability to add custom commands as well). Lazydocker's goal is to make that dream a reality.
Support for Docker
Graphical User Interface
Share your opinion about the software, leave a review and help make it even better!
Suggest Changes
Your Feedback
Your vote has been counted.
Do you have experience using this software?
