Closed nekerd closed 8 months ago
Container is stopped when apply new memory usage settings
By default, when CrashPlan quits, the container also terminates. If you prefer CrashPlan to be automatically restarted instead, set KEEP_APP_RUNNING=1
environment variable. See https://github.com/jlesage/docker-crashplan-pro#environment-variables
and new configuration is not applied after restarting container
If CRASHPLAN_SRV_MAX_MEM
variable is set, it will take precedence. It's usually better to use this variable to set the memory limit.
Hi Jocelyn, thanks for all your help. Your work is amazing!
Current Behavior
Container is stopped when apply new memory usage settings, and new configuration is not applied after restarting container
Expected Behavior
Container do not stop. Crashplan restart inside the active container and new setting are applied
Steps To Reproduce
Ctrl+Shift+C > Popup terminal from application appears > instruction provided: "java mx 4096, restart" container stopped
Environment
Container creation
/init
Container log
Container inspect
No response
Anything else?
No response