3 ms·
This is really neat. I have been using `podman generate systemd` for a large number of deployments. This just makes it so much simpler. For anyone wondering, t
by asabil 4y ago
This is really neat. I have been using `podman generate systemd` for a large number of deployments. This just makes it so much simpler.
For anyone wondering, the main difference between this and docker/docker-compose is that podman can run in a daemonless mode such as containers are running directly under systemd which makes them integrate into the existing systemd infrastructure and appear as any other normal service.
- bravetraveler 4y agoFor those curious why you may want this: consider your service relies on /somelocation Make that a mount unit in systemd (free from lines in /etc/fstab) and now you can accurately lay out your service's requirement/dependency on this filesystem. I know systemd gets flack for overreach 'as an init system', but there's a reason - initialization doesn't happen in a vacuum. Services need filesystems, networks, etc to matter.