When I try to run
npm start from inside the docker shell, I get this error:
# A fatal error has been detected by the Java Runtime Environment: # # Internal Error (safepoint.cpp:310), pid=31, tid=0x00000040381de700 # guarantee(PageArmed == 0) failed: invariant # # JRE version: OpenJDK Runtime Environment (8.0_242-b08) (build 1.8.0_242-b08) # Java VM: OpenJDK 64-Bit Server VM (25.242-b08 mixed mode linux-amd64 compressed oops) # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /opt/hs_err_pid31.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # qemu: uncaught target signal 6 (Aborted) - core dumped Aborted npm ERR! code ELIFECYCLE npm ERR! errno 134 npm ERR! @ start: `npm run grunt-concat && grunt watch & sbt -Dsbt.ivy.home='.ivy2' -Dsbt.global.base='.sbt' -Dsbt.repository.config='.sbt/repositories' compile "~ run" shell` npm ERR! Exit status 134 npm ERR! npm ERR! Failed at the @ start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2021-10-12T05_40_24_364Z-debug.log [email protected]:/opt# Error response from daemon: dial unix docker.raw.sock: connect: connection refused make: *** [docker-run] Error 1
It consistently errors out to this every time I try to run it. I’ve tried to run
export LD_BIND_NOW=1 based on a different post but still get this error.
Source: Docker Questions