Podman Desktop Companion
Full project documentation lives in docs/:
- Architecture
- Guides
- Project
- Podman offers an official cross-platform desktop UI available at Podman Desktop, give it a try.
- The container UI space is much more rich today, minimalist solutions exist, such as Pods, Podman TUI or feature rich ones such as Rancher Desktop
- Podman Desktop Companion is considered complete, it started by offering a familiar experience, but it strives to offer its own identity.
- It will not be shut-down or archived unless required, it was the first cross-platform container UI before any other existing solution.
- There is great pride in this(mom is proud), no other benefits were obtained, no donations on patreon or ko-fi since inception.
- It was my first experience with the open source world as a creator and the one that made me never do it again, at least not on my own.
- Thank you to The Podman Team and to all the great persons I've met!
A familiar desktop graphical interface to the free and open container manager, podman!
Main goals
- Cross-platform desktop integrated application with consistent UI
- Learning tool for the powerful
podmancommand line interface
- Linux - Install podman - note that distributions usually have older versions of podman, see Aalvistack for the most recent repositories.
Additional packages besides podman may be required, such as
aardvark-dnsandpasstfor networking (https://passt.top/passt/about/). If one wants to add support for docker container engine, the easiest is to install rootless docker as documented here https://linuxhandbook.com/rootless-docker/ - Windows - Install podman or provision your favorite WSL distribution with latest podman by following the instructions above for Linux. On your custom WSL distribution, a lightweight stdio relay bridges the engine's unix socket back to the Windows native context (named pipe ↔
wsl.exestdio — no TCP listener or SSH server inside the distribution). - MacOS - Install podman or lima
NOTE - To access and monitor remote ssh installations, properly set-up the connections in your
$HOME/.ssh/configor$env:USERPROFILE/.ssh/configjust like you do for Visual Studio Code remote extensions https://code.visualstudio.com/docs/remote/ssh - remote SSH connections use the nativesshclient with host-key verification (StrictHostKeyChecking=accept-newagainstknown_hosts) and forward the engine's unix socket to a local socket only.
- See docs/usage.md



