systemd-docker | Wrapper for `` docker run '' to handle systemd quirks | Continuous Deployment library

systemd-docker is a Go library typically used in Devops, Continuous Deployment, Docker applications. systemd-docker has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

In short, it’s best to always have --name %n --rm in your unit file’s ExecStart. The best way I’ve found to run containers under systemd is to always assign the container a name. Even better is to put --name %n in your unit file and then the name of the container will match the name of the service unit. If you don’t name your container, you will essentially be creating a new container on every start that will get orphaned. You’re probably clever and thinking you can just add --rm and that will take care of the orphans. The problem with this is that --rm is not super reliable. By naming your container, systemd-docker will take extra care to keep the systemd unit and the container in sync. For example, if you do --name %n --rm, systemd-docker will ensure that the container is really deleted each time. The issue with --rm is that the remove is done from the client side. If the client dies, the container is not deleted. If you do --name %n --rm, systemd-docker on start will look for the named container. If it exists and is stopped, it will be deleted. This is really important if you ever change your unit file. If you change your ExecStart command, and it is a named container, the old values will be saved in the stopped container. By ensuring the container is always deleted, you ensure the args in ExecStart are always in sync.