Set the image, map your ports and volumes, pick a restart policy, then copy a docker run command ready for your terminal or a compose file conversion.
docker run -d nginx:latestUse -d for services that should keep running in the background (web servers, databases). Use -it --rm for one-off interactive work like debugging shells, and drop both if you are wiring the container into a script that reads its stdout. -d and -it together rarely make sense.
This docker run generator assembles the flags that self-hosters and developers reach for daily: port publishing, bind mounts and named volumes, environment variables, restart policies for surviving reboots, and network attachment. The output works unchanged with Podman, alias docker=podman and everything here still applies.
Bind mounts (/host/path:/container/path) expose an existing host directory into the container. Named volumes (name:/container/path) are managed by Docker under /var/lib/docker/volumes and are the better default for data you do not need to browse on the host.
Check that the port is published on 0.0.0.0 (the default) rather than 127.0.0.1, and that the host firewall allows the port. Note that Docker inserts its own iptables rules which bypass ufw by default.
unless-stopped is the usual choice: the container restarts after crashes and reboots, but stays down if you deliberately stopped it. always will resurrect containers you stopped manually once the daemon restarts.
Yes. Podman implements the same CLI, so the generated command works with podman run directly. For rootless Podman, publishing ports below 1024 needs extra configuration.