2020 Jun 12, 04:18 PM
(This post was last modified: 2020 Jun 12, 05:59 PM by astrogerard.)
Hi Michael,
Restarting SIP within a container doesn't seem logical to me. Once SIP stops (or dies) the container should be killed.
Usually you should configure the entire application and its environment in the dockerfile. If you update a container from within the container your dockerfile will be out of date.
Ideally you should keep the specific settings etc. outside the container. In this case I would create a git repository with all specific commands and settings. In the dockerfile then just before starting SIP you can do a git clone and if necessary fire up some stuff to get prepared.
Hope this make a little sense,
--Gerard
Restarting SIP within a container doesn't seem logical to me. Once SIP stops (or dies) the container should be killed.
Usually you should configure the entire application and its environment in the dockerfile. If you update a container from within the container your dockerfile will be out of date.
Ideally you should keep the specific settings etc. outside the container. In this case I would create a git repository with all specific commands and settings. In the dockerfile then just before starting SIP you can do a git clone and if necessary fire up some stuff to get prepared.
Hope this make a little sense,
--Gerard