That’s interesting! I’ve converted all my docker run commands to docker compose, as I found that easier to manage. But, I guess you can’t do the dependencies like you have. Also, yours has the advantage it always pulls the latest.
Comment on What is easiest solution to automatically resolve missing mounts due to e.g. a power outage?
avidamoeba@lemmy.ca 4 months agoThis is the answer. You can straight up make things dependent on .mount units that represent stuff in fstab. To add, you can create any number of systemd services that just check if something is “as you want it” and only then “start”. You simply make the Exec line “/bin/bash -c ‘your script here’”. Then you make whatever else you want dependent on it. For example I have such a unit that monitors for Internet connection by checking some public DNS servers. Then I have services that depend on Internet connection dependent on that.
sylverstream@lemmy.nz 4 months ago
key@lemmy.keychat.org 4 months ago
Doesn’t seem mutually exclusive. Replace the docker rm with compose down and the docker run with compose up.
avidamoeba@lemmy.ca 4 months ago
Exactly. In fact I have a few multi-container services with docker-compose that I have to write systems unit files for.
qaz@lemmy.world 4 months ago
Perhaps you could also add the mounts as dependencies to the Docker daemon.
samwwwblack@lemm.ee 4 months ago
You can use
RequiresMountsFor=(egRequiresMountsFor=/media/storage-volume1) instead of manually adding.mounttoAfter/Requires- you can then use.mountfiles or fstab as you’re stipulating the path rather than a potentially changeable systemd unit name.The systemd.mount manpage also strongly recommends using fstab for human added mount points over
.mountfiles.avidamoeba@lemmy.ca 4 months ago
Oh this is nice. I’ll probably start using it.