SenorLoco Posted October 6, 2018 Share Posted October 6, 2018 I was previously using a plugin to delay the start of my home-assistant docker until my mqtt vm was loaded, but since the plugin was depreciated with the release of 6.6.0 I've tried using the new 'wait' option, but noticed an issue. I had home-assistance wait set to 60 seconds, but it didn't actually wait...and then I noticed this is the system log. Oct 4 14:20:37 Tower rc.docker: home-assistant: started succesfully! Oct 4 14:20:37 Tower rc.docker: home-assistant: wait 60 seconds A little further down the next container started successfully, but 60 seconds after home-assistant. Am I misinterpreting the wait function? Is it not how long to wait before starting that container or is it how long to wait after it is started before the next is started (and if that is the case, are containers loaded in the order they show in the GUI) Quote Link to comment
hernandito Posted October 11, 2018 Share Posted October 11, 2018 Not sure if this is what you are looking for. Quote Link to comment
bonienl Posted October 12, 2018 Share Posted October 12, 2018 On 10/6/2018 at 5:50 AM, SenorLoco said: is it how long to wait after it is started before the next is started (and if that is the case, are containers loaded in the order they show in the GUI) yes Quote Link to comment
Recommended Posts
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.