jesseduffield/lazydocker

Feature request: show container names

Open

#40 opened on Jul 1, 2019

View on GitHub
 (17 comments) (6 reactions) (0 assignees)Go (51,040 stars) (1,612 forks)batch import
good first issue

Description

Hi, i'v tested out lazydocker today and i love it! A feature to have is to have names on the containers where the Services window is.

I have a docker-compose.yml file:

version: '3.7'

services:
  mongodb:
    image: mongo
    container_name: "db_app"
    ports:
      - "27017:27017"

  frontend:
    image: quizgame/webclient
    container_name: "web_app"
    build:
      context: .
      dockerfile: Dockerfile
    ports:
      - "8080:3000"
    environment:
      - NODE_ENV=docker
    depends_on:
      - mongodb

In Services window, there is to running containers.

running frontend 0.00%
running mongodb 0.35%

It should be:

running frontend (web_app) 0.00%
running mongodb (db_app) 0.35%

Love this tool!

Contributor guide

Tech stack
godocker
Domain
clidevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programmingDocker basicslazydocker architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Start by examining the code that renders the Services window in lazydocker. It likely constructs a list of containers with their names and CPU/memory usage. Look for where the display string like 'running frontend 0.00%' is generated. The issue suggests appending the container name in parentheses. Check the comments on this issue for any discussion on implementation. Also review the docker compose parsing logic to see if the container name field is already available. Relevant files may be in the docker or gui directories.