I am wondering what is the best practice for this. What happens if for x,y,z reason I need to restart the hardware host where a rancher-agent is running. When we add a custom host to an environemnt the generated bash command does not include a “–restart always” flag.
I am wondering what is the right thing to do. Right now what I’ve done is search through the history and find the generated bash command and re-run it, but I am sure that is not the proper way to do it.
Could someone share what is the correct procedure for this?
The command that is shown creates a data volume, starts the actual agent, and then exits. If you look at the container that is actually running afterwards it has the equivalent of --restart=always.