Docker and Podman

Docker and Podman

Noob mode

The Wizard can create a container setup:

binman wizard

Or manage an existing BinMan app:

binman docker up MyApp
binman docker logs MyApp
binman docker shell MyApp
binman docker down MyApp

Pro mode

The complete action family is:

binman docker up|down|restart|logs|follow|shell|edit|build|remove|nuke|purge APP
binman docker run APP -- COMMAND [ARGS...]
binman docker prune
binman docker orphans

BinMan detects Docker or Podman unless --engine docker|podman selects one. Metadata lives under ~/.local/share/binman/docker, or under the directory specified by BINMAN_DOCKER_DIR.

up creates or starts a managed service. build builds from the app metadata root. edit changes ports, environment, mounts, network, and restart policy. run performs a one-shot execution. remove removes a managed container; nuke removes the managed container and image; purge removes BinMan's metadata. prune cleans managed images and orphans finds metadata whose container no longer exists.

Wizard container modes

The Wizard offers none, oneshot, or service:

1. It creates a language-appropriate Dockerfile and .dockerignore.
2. It asks for host/container ports, environment values, network, and mounts.
3. Service mode additionally asks for restart policy and defaults to mounts under ~/.config, ~/.local/share, and ~/.cache for the app.
4. It writes metadata so the Docker screen can manage the result.

Container generation is scaffolding, not a guarantee that an image will build. Review the generated entry command and Dockerfile. remove, nuke, and prune affect real containers, images, and disk space; the robot is powerful, but it is not legally responsible for your abandoned image collection.