Ivan Wong Ivan Wong - 1 year ago 104
Bash Question

spring-boot cannot start in docker

I've a little problem with run my spring boot application in docker.

stack: maven 3+, spring boot(jpa/rest/jetty) - mysql - deploy in docker

So, i've have in my pom file

<relativePath/> <!-- lookup parent from repository -->


<!-- add for exlude tomcat -->
<!-- Jetty (tomcat replacement) -->
<!-- mysql connector -->
<!-- optional dependency javax.el -->
<!-- google http client -->
<!-- google http jackson -->

Ubuntu 16.04 x64
The problem:
Locally: I try to run my app with follow command in terminal

user$ java -Xmx768m -jar /mnf-backend.jar --spring.datasource.url=jdbc:mysql://$MYSQL_PORT_3306_TCP_ADDR/app_1?autoReconnect=true&useSSL=false
user$ #<--- LOOK AT THIS jvm has return of control with 1 status (or same status but not negative)
:: Spring Boot :: (v1.4.0.M3) # <--- spring boot starts by itself. HOW????

it's not good by i can tolerate it. But not docker.
When commands above will be run in docker then docker stop container (because -> app exit with status 1)

ENTRYPOINT ["java", "-Xmx768m", "-jar", "/mnf-backend.jar", "--spring.datasource.url=jdbc:mysql://$MYSQL_PORT_3306_TCP_ADDR/app_1?autoReconnect=true&useSSL=false"]

Docker will start container 1 second and immediately stop container because java return control.
I look for method which allow me to configure spring app for predictable behavior or any ideas how to improve my docker instructions.
my dockerfile content:

FROM frolvlad/alpine-oraclejdk8:slim

ENV MNFB_ENV production

ADD ./builds/mnf-latest.jar mnf-backend.jar


ENTRYPOINT ["java", "-Xmx768m", "-jar", "/mnf-backend.jar", "--spring.datasource.url=jdbc:mysql://$MYSQL_PORT_3306_TCP_ADDR/minifinance?autoReconnect=true&useSSL=false"]

docker logs of a container
enter image description here

For example: when i've start nodejs app control not return until application not finished

user$ node ./server.js
[...here program output and stdout strings]
[... it may be stopped by ctrl+c for example]


I think the problem is the ampersand (&) in your command line:


Try to escape it:


The ampersand denotes the shell to start your process in the background. That's exactly what's happening on your local machine. If you start your jar, the process should start in foreground... and the prompt shouldn't return directly.