Closed PatrickRWright closed 1 year ago
For now I suspect something like has been described here:
https://stackoverflow.com/questions/72841549/container-fails-to-start-insufficient-memory-for-the-java-runtime-environment-t
My server actually runs a rather old version of Docker (19.03.8, build afacb8b7f0
), which I will try and update ASAP in the hope that this fixes the problem.
With Docker version 24.0.5, build ced0996
its working.
I've tried to transition from shinyproxy 3.0.1 to the more recent 3.0.2. The only change I knowingly made is this. i.e. Dockerfile used to start with
FROM openanalytics/shinyproxy:3.0.1
and now hasFROM openanalytics/shinyproxy:3.0.2
.My 3.0.1 based setup works like a charm but the setup using 3.0.2 keeps showing the
STATUS
Restarting
when callingdocker ps
.Looking at the
docker logs
I see messages like these:There is insufficient memory for the Java Runtime Environment to continue.
Out of Memory Error (workerManager.hpp:70), pid=1, tid=1
However, the machine I am running this on has 16 GB of RAM and 13 GB of those are free.
I hope this is the right place for this question.