Force start containers on reboot?


Recommended Posts

So I'm out of town and last night I connected to my server through my OpenVPN docker to check on things.  I started fooling around with another container and absentmindedly clicked 'shut down all containers'... which naturally shutdown OpenVPN along with everything else... 

 

My server is plugged into a Wemo outlet (and UPS) to let me force shutdown if absolutely necessary, but upon restarting my containers didn't come up back up as I hoped they would have (the auto-restart button is on).  I did get an email notification saying it came back on, so it's definitely running though.  Anyways, now I have to wait until someone gets home in a few days so I can teamviewer into her computer, turn my containers back on, etc...  

 

Tldr: Idiotically booted myself out of OpenVPN and the container didn't start on server restart.

 

Is there anything I can add in place once I'm back up to ensure this doesn't happen again?  I was thinking perhaps a user script set to run on startup to ensure OpenVPN always starts?  But maybe there's a better way?  

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.