Podman Playground
A Linux server with Podman, a daemonless Docker alternative, pre-installed.

About This Playground
Want to try a Podman command, build a Containerfile, or see how a daemonless container engine compares with Docker—without installing anything on your laptop?
iximiuz Labs' Podman playground gives you a fresh Linux server with Podman pre-installed and ready to use. It starts in seconds, opens in your browser, and behaves like a regular remote machine: you get a shell, root access, a real Linux kernel, and enough freedom to install additional tools or reconfigure the system as needed.
This is not a limited container-in-container shell. The playground is a lightweight but fully fledged VM running on iximiuz Labs' bare-metal infrastructure. Podman runs directly on Linux and manages OCI containers without requiring an always-running central daemon.
Podman's command-line interface will feel familiar if you've used Docker, but its architecture opens up a few interesting additional scenarios. Run containers as root or as a regular user, explore rootless networking and storage, group containers into pods, build images from Dockerfiles or Containerfiles, push them to registries, and manage long-running workloads with systemd and Quadlet.
Use the Podman playground for learning containers, comparing Podman and Docker workflows, testing existing images and build files, experimenting with rootless containers, and running short-lived development or demo environments. Because the machine is disposable, you can freely change container storage, break networking, test unfamiliar projects, or fill the image cache with experiments—then start over with a clean server.
iximiuz Labs playgrounds are not intended for production workloads or services that must stay online indefinitely. Playground sessions have a time limit, public URLs should not be treated as production endpoints, and disposable environments are the wrong home for secrets, sensitive data, or anything irreplaceable.
For everything else, start the VM and get your hands dirty. The fastest way to understand what makes Podman different is to run containers, inspect the processes and namespaces underneath, and compare what you find with the Docker model you may already know.
Happy hacking!
A real VM, not a container
Get root on a VM with its own kernel, so Docker, Kubernetes, and systemd just work.
Read the docs →
SSH from browser or CLI
Use the built-in web terminal, or connect with labctl ssh, plain ssh, scp, or rsync.
Read the docs →
Drive it with AI
Let Claude, Codex, or any MCP client start this playground and run commands in it.
Read the docs →
Expose HTTP(S) ports
Give any web app running inside the VM a public URL - for yourself or to share with others.
Read the docs →
Share terminals
Invite others into your terminal session, or open it yourself from another device.
Read the docs →
Customize with init scripts
Add shell scripts that run at boot to install packages, clone repos, or seed test data.
Read the docs →
Private networking
VMs reach the internet via NAT with no public IP; several VMs share bridge networks.
Read the docs →
Ephemeral or persistent
By default, VMs are destroyed when the session ends; enable persistence to keep the disks for next time.
Read the docs →
Built-in container registry
A private registry.iximiuz.com for every playground to share images across services and VMs.
Read the docs →