Lazydocker - Simplify Container Management with One Terminal Window

TechOps Examples

Hey — It's Govardhana MK 👋

AN IMPORTANT UPDATE - On readers' demand, we are starting the remote jobs section from this edition as an experiment.

Share your feedback in the poll at the end of this edition!

👋 Before we begin... a big thank you to today's sponsor Notops

If your team finds Kubernetes and cloud-native technology overwhelming, Notops.io enables you to leverage its full potential without deep technical knowledge of AWS, Kubernetes, or complex cloud ecosystems.

Notops.io empowers teams to build scalable, secure Kubernetes platforms with industry-best practices and observability from the start—so you can focus on innovation, not infrastructure.

See why organizations are experiencing faster, measurable impact with Notops.io from day one.

IN TODAY'S EDITION

🧠 Use Case

• Lazydocker - Simplify Container Management with One Terminal Window

🚀 Top News

• Prometheus 3.0 Announced: What's New?

  • New UI with PromLens-style tree view.

  • Remote Write 2.0 adds native histograms.

  • OTLP ingestion supports UTF-8 metrics.

  • More details here.

👀 Remote Jobs

• Staple is hiring a DevOps Engineer

  Hires remotely in: India, Singapore

• Proxify is hiring a Senior DevOps Engineer (Azure / AWS)

  Hires remotely: Anywhere

• Supabase is hiring a Cloud Platform / Site Reliability Engineer

  Hires remotely: Anywhere

📚️ Resources

• Ultimate DevSecOps library

• Build container images in OpenShift using Podman as a GitLab runner

• DevSecOps Pipeline Project: Deploy Netflix Clone on Kubernetes with Monitoring

👇️Join me to not miss daily updates  

X (twitter) |  Instagram 

🛠️ TOOL OF THE DAY

cloud custodian - A rules engine for cloud security, cost optimization, and governance..

• Used to manage AWS, Azure, and GCP environments.

• DSL in yaml for policies to query, filter, and take actions on resources.

🧠 USE CASE

Lazydocker - Simplify Container Management with One Terminal Window

Managing Docker containers often feels like a juggling act.

We often check docker-compose ps, restart a service, and follow logs with docker-compose logs --follow.

But every time the service crashes, the logs stop, and we have to restart the process.

Using docker-compose up helps, but it locks a terminal, and detaching feels awkward.

Before long, we’re stuck wondering which command to use without accidentally killing the service.

In this context, I started using Lazydocker a while ago during some client projects that couldn’t afford expensive alters.

At first, I was skeptical about how much a terminal UI could help, but after using it, I was hooked.

Here's what I loved:

• Let me monitor all services in one clear terminal interface.

• Allowed viewing isolated logs without wading through irrelevant clutter.

• Made restarting or rebuilding containers as simple as a keypress.

• Freed up terminal space without the fear of killing anything.

• Simplified Docker management so the client’s could focus on crucial things, not commands.

Lazydocker installation is standard and straight forward using:

Brew (Linux or MacOs):

brew install lazydocker

Scoop (Windows):

scoop install lazydocker

 Chocolatey (Windows)

choco install lazydocker

How to access the terminal UI ?

Just run ‘lazydocker’ in the terminal - simple.

The best part - it is easily customizable.

You can fine-tune what you want to see by updating the Lazydocker config file.

You can even add custom commands like:

To explore all config options, click here.

Hope this helps, and I suggest giving Lazydocker a try for your containerized projects.

Looking to promote your company, product, service, or event to 20,000+ TechOps Professionals? Let's work together.