/tools/docker-run-to-compose takes the docker run ... command a README gives you and writes the equivalent compose.yaml. It handles the flags we see most in project READMEs: -p ports, -v volumes and bind mounts, -e and --env-file, --name, --restart, --network, --add-host, -d (dropped, compose is detached anyway), --gpus, and a trailing command.
Why bother: the docker run line is fine for trying something once, but the second service you add (a database, a reverse proxy) you want compose, and converting by hand is where the typo in the volume path happens. The tool runs in the page; nothing is sent to a server.
Known limits: it does not know what the image expects, so it will not invent a healthcheck or a depends_on for you, and exotic flags are passed through as a comment rather than guessed. If a flag you use comes out wrong, paste the line here and we will fix the parser.