LaunchDaemon starts too soon — how to work around?
I have a LaunchDaemon that starts Docker, but the files Docker needs to run are on a filesystem that takes another 15–20 seconds to mount.
Consequently, I have to quit the stalled Docker instance and restart it manually.
I’m trying to figure out a better way to have Docker start after the file system mounts. I have two main thoughts.
- Have Docker’s LaunchDaemon wait for 30 seconds or so before starting.
- Stop the LaunchDaemon from running at load and have a separate daemon count to 30 before invoking Docker’s LaunchDaemon
Any thoughts or suggestions would be fantastic!
Posted May 5, 2025, 2:10 AM UTC
22