Resources

Headless Container Management

Podman, Docker, and Distrobox without the Desktop Bloat.

The Strategy

In most operating systems, running containers requires a "Desktop App" (Docker Desktop, Podman Desktop). These apps are Electron-based, use massive amounts of RAM, and add an unnecessary layer of complexity between you and the engine. In Tebian, we use the Headless CLI engines directly.

This guide explains how to manage your development environments and services using raw, high-performance container engines.

1. The Podman Advantage

Podman is the "Docker alternative" with a key difference: it is Daemonless. Unlike Docker, it doesn't run a background process as root. It's just a tool that starts containers.

  • Rootless: Run containers as your normal user for better security.
  • Docker Alias: Simply alias docker=podman. Same commands, better engine.
  • Zero-Overhead: No background daemons consuming RAM.

2. Distrobox (The AUR Bridge)

This is Tebian's "Secret Weapon." Distrobox lets you run any Linux distribution (Arch, Alpine, Fedora) inside a container, but it integrates them into your host desktop. You can run Arch AUR apps as if they were native to Tebian.

  • Arch on Debian: Get the latest AUR packages without the fragility of an Arch host.
  • Isolation: Keep your main OS clean while you test messy dependencies.
  • Performance: It's a container, not a VM. There is zero performance penalty.

3. Docker-Compose for Services

For complex, multi-container stacks (like a database + web server), Tebian's "Container Mode" includes a pre-configured docker-compose setup that talks directly to the Docker.io engine.

  • Systemd Integration: Auto-start your containers on boot.
  • Networking: Pre-configured bridges for container-to-host communication.
  • Volumes: Secure, local storage for your database data.

4. The "No GUI" Policy

Why avoid the GUI? Because GUIs lie to you. They hide the configuration files and the error logs. When a container fails in a GUI, you get a generic "Error." When you use the CLI, you get the raw STDOUT. In Tebian, we teach you how to be the root of your containers.

  • CLI Tools: ctop for container monitoring, lazydocker for terminal TUI management.
  • Direct Logs: podman logs -f [container]. See the truth in real-time.
  • Pure Performance: No GUI means more RAM for your containers.

Why Containers on Tebian?

Tebian's stability (Debian base) makes it the perfect host for containers. Your host never changes, but your containers can be anything. It's the ultimate "Dev/Ops" balance: a rock-solid foundation with the freedom to run any software in a sandbox.