agentleFS
Sign inStart free
TeddyAlbinaTeddyAlbina/skills/podman/SKILL.md

podman

Skill2 starsChanged 28 days agoMITView on GitHub

Podman is a daemonless, rootless OCI container engine for managing containers, images, volumes, and pods. It is fully compatible with Docker CLI commands and the Docker API while offering superior security (no root daemon) and flexibility.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No background daemon → improved security and lower idle resource usage.

    line 12
  2. Distinctive:

    Rootless: No special flags needed in most modern installs

    line 105
  3. Very specific:

    Quadlet: Place .container files in ~/.config/containers/systemd/ or /etc/containers/systemd/

    line 107
  4. Very specific:

    Manpage Syntax Reminder: Follow exact formatting from MANPAGE_SYNTAX.md (OPTIONS in alphabetical order, bold defaults, tables for complex …

    line 110
  5. Distinctive:

    Use pods for multi-container apps.

    line 114
  6. Distinctive:

    Use Netavark + CNI plugins for complex networking.

    line 116
  7. Very specific:

    Use podman farm for distributed builds.

    line 118
  8. Very specific:

    Always check podman version and podman info for configuration.

    line 122
  9. Very specific:

    Always reference podman --help + specific man page.

    line 133

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

1. What is Podman?

  • Runs on Linux natively; supports macOS and Windows via podman machine (VM-based remote client).
  • Built on the libpod library.
  • Supports OCI and Docker image formats.
  • Full lifecycle management: build, run, checkpoint/restore (CRIU), network, pods, etc.
  • No background daemon → improved security and lower idle resource usage.
  • REST API with Docker-compatible + enhanced endpoints.
  • Excellent Docker compatibility (drop-in replacement for most docker commands).

Official Project Links (always cross-reference):

2. Key Features & Advantages (vs Docker)

  • Rootless by default (no sudo required for most operations).
  • Daemonless architecture.
  • Pods (groups of containers sharing network/IPC namespaces, inspired by Kubernetes).
  • Native Kubernetes YAML support (podman kube play/generate).
  • Quadlet (systemd-native container management via .container/.pod/.image/.volume unit files).
  • Netavark (modern networking stack).
  • Image signing & trust policies.
  • Machine management for remote clients (macOS/Windows).
  • Farm (multi-host build farms).
  • Artifact commands (new in recent versions for handling OCI artifacts).
  • Full compatibility with Docker CLI + API.
  • Built-in remote client support.

3. Documentation References (MANDATORY – Always Link These)

Core Documentation Tree (GitHub)

Command Documentation (Markdown Source – All Man Pages)

https://github.com/containers/podman/tree/main/docs/source/markdown

categorized List of Command Markdown Files:

Artifact Commands

Container Commands

Image Commands

System, Machine, Farm & Misc Commands

  • podman-machine.*, podman-farm.*, podman-info, podman-events, podman-logs, podman-exec, podman-create, podman-run, podman-start/stop/rm, podman-ps, podman-inspect, podman-kill, podman-logs, podman-cp, podman-diff, podman-export/import, podman-load/save, podman-login/logout, podman-auto-update, podman-completion, podman-generate-*, podman-healthcheck, podman-history, podman-init, podman-mount/unmount, etc.
  • Full directory (ALL files): https://github.com/containers/podman/tree/main/docs/source/markdown

Shared Options (included via @@option in man pages):
https://github.com/containers/podman/tree/main/docs/source/markdown/options (e.g., env.md, volume.md, network.md, cap-add.md, etc.)

Aliases/Links: https://github.com/containers/podman/tree/main/docs/source/markdown/links

Tutorials & Advanced Guides

Tutorials Directory: https://github.com/containers/podman/tree/main/docs/tutorials

  • podman_tutorial.md, rootless_tutorial.md, basic_networking.md, image_signing.md, remote_client.md, mac_client.md, podman-for-windows.md, performance.md, socket_activation.md, qemu-remote-tutorial.md, podman-derivative-api.md, etc.

CNCF Self-Assessment: https://github.com/containers/podman/tree/main/docs/cncf/self-assessment.md

Build & Rendering: See docs/README.md for make docs, make html, Sphinx, Pandoc, etc.

4. Core Workflows & Common Commands (Agent Must Master)

Always prefer official man pages for exact syntax/flags.

  • Build: podman build -t image:tag . (or podman buildx compatibility)
  • Run: podman run -d --name mycont -p 8080:80 image
  • Pods: podman pod create, podman pod run
  • Kube: podman kube play deployment.yaml, podman kube generate
  • Rootless: No special flags needed in most modern installs
  • Machine (macOS/Windows): podman machine init/start/ssh
  • Quadlet: Place .container files in ~/.config/containers/systemd/ or /etc/containers/systemd/
  • Remote: podman --remote or set CONTAINER_HOST

Manpage Syntax Reminder: Follow exact formatting from MANPAGE_SYNTAX.md (OPTIONS in alphabetical order, bold defaults, tables for complex args, no pronouns, etc.).

5. Best Practices & Advanced Topics (Agent Guidance)

  • Prefer rootless mode.
  • Use pods for multi-container apps.
  • Leverage Quadlet for systemd integration, use SKILL podman-quadlet when you need to deal with quadlet.
  • Use Netavark + CNI plugins for complex networking.
  • Enable image signing with podman image trust.
  • Use podman farm for distributed builds.
  • Monitor with podman events, podman system df, podman info.
  • Security: Use --security-opt, capabilities, seccomp, apparmor/selinux.
  • Volumes: Named volumes preferred over bind mounts for portability.
  • Always check podman version and podman info for configuration.

6. Docker Compatibility & Migration

  • Most docker commands work with podman (alias docker=podman).
  • Differences: No daemon, rootless by default, pod concept, different storage/network drivers.
  • See official migration guides in rendered docs.

7. Troubleshooting & Common Issues

  • Rootless networking/permission issues → check containers.conf.
  • Remote connection → podman system connection.
  • Build cache → podman builder prune.
  • Always reference podman --help + specific man page.

8. Agent Usage Instructions

  • Always cite the exact GitHub Markdown file or rendered ReadTheDocs page when answering.
  • Provide complete command examples with common options (e.g., --rm, -v, --name, --network, --env).
  • For complex tasks, combine commands (e.g., podman build && podman run or Quadlet units).
  • Recommend reading the full man page for any command.
  • Stay up-to-date: Check the main branch of https://github.com/containers/podman/tree/main/docs/source/markdown for latest command docs.

Associated SKILLs:

  • podman-quadlet

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free