java virtual machine launcher error unable to access jarfile minecraft

I've tried specifying the absolute path to the jarfile in the CMD of the Dockerfile, but that doesn't help when running from Docker Compose.ĭoes anyone know what might be causing this? I'm on a Windows 10 host. $ /usr/src/core # java $JAVA_OPTIONS -jar $JARFILEīut if I run a container from the same image as part of docker-compose up -d the container fails with the error that Java couldn't access the jarfile. If I run an individual container from the core_image image, and set the same environment vars that I defined in the docker-compose file, I can launch the Spring Boot app successfully, like so: $ docker run -it -p 8080:8080 -name mycontainer core_image sh myproject/target/myjar.jar /usr/src/core The Dockerfile for the core service, which is the one running the Spring Boot app, is this: FROM openjdk:8-jdk-alpineĪDD. My docker-compose file is: version: '3.3' Mycontainer | Error: unable to access jarfile myjar.jar Running docker-compose logs core shows that the error message is:

For purposes of this post I'm using generic names like 'mycontainer' and 'myfile'. Como SOLUCIONAR o ARREGLAR el problema java virtual machine launcher error MINECRAFT Die 427 subscribers Subscribe 1.6K 83K views 2 years ago ARGENTINA En esta ocasin les vengo a dejar un.

I'm trying to run a Spring Boot app as one of the services in a Docker Compose setup, but whenever I run docker-compose up -d the container running the Spring Boot app fails and exits immediately.

Java virtual machine launcher error unable to access jarfile minecraft