Cloud & Storage 4
DevOps & Automation 8
Media & Home 9
Monitoring 6
Network & Proxy 8
Productivity 8
Security 5
Tools 3
Web & Communication 4
Community 1
Network
Advanced
systemd service
.kube unit of the Kube YAML tab.Build a Podman pod and get it running
Add containers from the sidebarMenu, load one of the ready-made stacks, or Import a docker-compose file, a docker run command or Pod YAML.
You get the pod as Kube YAML, Quadlet, Compose or shell script, with step-by-step setup for Debian, Fedora, Arch and Alpine, rootless or rootful.
Fill in variables
Import Pod YAML
Paste an existing podman play kube YAML (kind: Pod) — containers, volumes, ports and environment variables will be loaded into the builder.
Import docker-compose.yml
Paste your docker-compose.yml below or drop a file onto the text area. Services will be converted to pod containers.
Rate-limited: 1 import per 2 minutes. Named volumes and env vars are preserved. Secrets/build sections are ignored.
Variables found in the compose file. Pre-filled defaults can be adjusted before import. Empty fields have no default.
Import docker run command
Paste a docker run or podman run command. Backslash line continuations and sudo prefix are handled automatically.
Rate-limited: 1 import per 2 minutes.
Paste .env file
Paste your .env file content. Missing variables will be added to the affected containers. Existing vars won't be overwritten.
Review passwords
These password/secret fields were imported from your compose file. Generate secure random values or enter your own.
Use host path
Enter a base directory on your host. Each volume will be mounted as a subdirectory.
Directories must exist and be accessible to the container user. In rootless Podman, chown to the mapped UID may be required.
Review environment variables
Warnings before generating
Select database
Database type:
Hostname or IP of the database server:
