3 ms·
Its documented. If you just type `podman-compose` in the command line you get... usage: podman-compose [-h] [-v] [--in-pod in_pod] [--pod-args pod_args]
by ape4 3y ago
Its documented. If you just type `podman-compose` in the command line you get...
usage: podman-compose [-h] [-v] [--in-pod in_pod] [--pod-args pod_args]
[--env-file env_file] [-f file] [-p PROJECT_NAME]
[--podman-path PODMAN_PATH] [--podman-args args]
[--podman-pull-args args] [--podman-push-args args]
[--podman-build-args args] [--podman-inspect-args args]
[--podman-run-args args] [--podman-start-args args]
[--podman-stop-args args] [--podman-rm-args args]
[--podman-volume-args args] [--no-ansi] [--no-cleanup]
[--dry-run]
{help,version,wait,systemd,pull,push,build,up,down,ps,run,exec,start,stop,restart,logs,config,port,pause,unpause,kill}
...
command:
{help,version,wait,systemd,pull,push,build,up,down,ps,run,exec,start,stop,restart,logs,config,port,pause,unpause,kill}
...
systemd create systemd unit file and register its compose stacks
When first installed type `sudo podman-compose systemd -a create-unit`
later you can add a compose stack by running `podman-compose systemd -a register`
then you can start/stop your stack with `systemctl --user start podman-compose@<PROJ>`
- lolinder 3y agoYeah, I eventually found that, but only after I finally stumbled upon someone referencing the feature in a GitHub issue. The --help is fine documentation for the people who have already installed the tool, but it doesn't help people like OP who just want a simple way to run multiple containers as a systemd unit and don't yet know that podman-compose has a solution. That's why I said "poorly documented" instead of "undocumented". It's there once you know where to look.
- tw04 3y agoThat’s… not documentation. That’s a CLI helpfile. It’s better than nothing but also what is completely broken with the “move fast and break things” mindset.
- notatoad 3y agoit's documentation enough to not call it an undocumented feature. the concern with truly undocumented functionality is that it's not included intentionally: either it's a bug or an experimental feature that could be removed or changed with no notice. a poorly-documented feature, on the other hand, will probably at least get a deprecation notice before it disappears
- lolinder 3y ago> it's documentation enough to not call it an undocumented feature. Which is why I didn't call it that, I called it poorly documented.
- scrozart 3y agoSure looks like documentation to me, but I don't need pretty webpages. 'man' is more than sufficient for tools like these.
- ClumsyPilot 3y agoHow would I ever read this documentation without installing postman? Am I suppose to download and install every tool just to read about how it works?