I am running Fedora Server with Docker installed, and it has a folder that connects to my NAS via SMB. I will have all of my Docker files (and Compose configs) stored on my NAS, since it has a lot more storage. I am worried that Docker will glitch out and cause a mess, since my NAS starts ~2 minutes later than my server from a reboot. Is there something that I can do to make sure Docker is able to connect to the SMB share safely?

  • Max-P@lemmy.max-p.me
    1·
    5 months ago

    Make Docker depend on the mount. You can simply use systemctl edit docker.service and then

    [Unit]
Requires=path-to-your-smb.mount
After=path-to-your-smb.mount

    Then it will guarantee it’s mounted by the time Docker starts.

    • Mountain_Mike_420@lemmy.ml
      0·
      11 days ago

      This is the answer. I’m not sure you need both. I tried the Requires= but that didn’t solve my problem till I did After= Thanks for the heads up!

      • Max-P@lemmy.max-p.me
        2·
        11 days ago

        It does need both. Requires= alone will only pull the unit as a dependency and will activate it, but doesn’t define a hard dependency. You need the After= to also declare that the unit must be started after its dependencies are finished loading, not merely being activated. Otherwise they will start in parallel, it just guarantees that both units will be activated. There’s an even stronger directive, BindsTo=, that will tie them such that if its dependency is stopped, this unit will be deactivated too. If SMB is a hard dependency that might be preferable. Requires+After still allows the mount to fail, but ensures if it’s mountable it’ll be mounted before Docker, whereas with BindsTo+After, failing the SMB mount would also shut down Docker.