You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When we need to take down the server hosting LME for maintenance purposes, what is the best way to stop the LME docker stack without completely destroying the existing containers?
We want to be able to re-run docker stack after the downtime and still have access to all the data that was present beforehand.
Describe the solution you'd like
Please add a section under the "Maintenance" section of https://github.com/cisagov/LME, where you provide guidance on how to properly stop LME in a manner that preserves state.
Describe alternatives you've considered
Tried to run "docker stop <lme_container_ids>" but the containers come right back up automatically.
docker remove commands are not a good alternative, because that would theoretically destroy all the data inside the containers.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When we need to take down the server hosting LME for maintenance purposes, what is the best way to stop the LME docker stack without completely destroying the existing containers?
We want to be able to re-run docker stack after the downtime and still have access to all the data that was present beforehand.
Describe the solution you'd like
Please add a section under the "Maintenance" section of https://github.com/cisagov/LME, where you provide guidance on how to properly stop LME in a manner that preserves state.
Describe alternatives you've considered
Tried to run "docker stop <lme_container_ids>" but the containers come right back up automatically.
docker remove commands are not a good alternative, because that would theoretically destroy all the data inside the containers.
Additional context
N/A
The text was updated successfully, but these errors were encountered: