Show HN: Container Desktop – Podman Desktop Companion

Original Article ↗ Hacker News Discussion ↗

Project goals and scope

  • Container Desktop is presented as a lightweight, MIT-licensed GUI “companion” for Podman (and Docker), not a full “batteries included” stack like Docker Desktop.
  • Focus is on minimal resource usage, clear UI/UX, and exposing what happens “behind the scenes” via a developer console to help users learn and eventually script things themselves.
  • Kubernetes integration is explicitly “planned” and requested by some users, but not available yet.

Comparisons with Docker Desktop and other alternatives

  • Many comments discuss the broader ecosystem: Colima, Rancher Desktop, OrbStack, Podman Desktop, kind, k3s/k0s, minikube.
  • Docker Desktop is praised for stability and features (including VS Code Devcontainers support and local Kubernetes), but criticized for:
    • Licensing (paid for companies over a certain size).
    • High memory/CPU usage.
  • Alternatives:
    • Rancher Desktop considered solid; large teams have migrated successfully, especially for k3s.
    • OrbStack is frequently praised for speed, low resource usage, fast Kubernetes startup, and quality-of-life features, but it requires a paid license and subscription model.
    • Colima is appreciated for simplicity and x86-on-Apple-Silicon support, though some report stability issues.
    • Podman Desktop is mentioned as a strong FOSS option; compose support relies on various shims (podman-compose, docker-compose via Podman’s socket, podman compose).

User experience and quality

  • Some users report Container Desktop as “not fully baked”: bugs, confusing UX, weak error messages, extra setup needed, and inability to browse image tags.
  • Others see it as a promising, non-commercial passion project, encouraging bug reports instead of complaints.
  • On macOS, users hit startup errors and signature issues on Apple Silicon; unsigned builds trigger “damaged” warnings, with workarounds documented but no paid signing due to cost.

GUI vs CLI debate

  • One camp questions the need for Docker/Podman GUIs when CLI commands are relatively simple.
  • Others argue GUIs:
    • Reduce cognitive load across many tools.
    • Help infrequent users (e.g., frontend devs, interns) and large teams by standardizing workflows (“install X, run Y”).
    • Excel for exploration, visualization, and occasional tasks.