Docker Restart Policy within containers

    • OMV 4.x
    • Resolved

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Docker Restart Policy within containers

      Can I get more info on the Docker Restart Policy from the OMV console? I'll attach a screenshot for what I'm referring to. I see the 4 options (no, always, unless-stopped, on-failure) but want to know if it's something I need to set in case the server is rebooted or loses power and starts back up.
      • 2018-07-30_16-17-16.jpg

        75.73 kB, 657×705, viewed 149 times
    • (After testing the container to insure it's stable and something you want to keep.)

      If you want the container to run all the time, no matter what, set it to "always". That will cover a few scenarios.

      - Server Reboots
      - Container crashes (A Docker container is a type of Linux VM. While I've never see it with my containers, a crash is possible. )
      If the container is not corrupt, "Always" will restart it.

      If you need to stop the container, to do an update or for testing a replacement, manually stopping it in the Docker plugin will still work.

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.13, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk

      The post was edited 2 times, last by flmaxey: edit ().