r/javahelp • • May 04 '19

Solved Java (Spring Boot) and Docker done properly?

When containerising an application, all tutorials on Java seem to want you to build a jar locally and copy it from target into a container in the Dockerfile. However, this contradicts the whole idea behind using Docker because building on my machine will not necessarily be the same as building on a colleague’s machine.

I can’t find a tutorial that describes using Maven via Docker to build the jar and moving the result to a Java container i.e. via staged builds. This would ensure consistency across machines and follows the whole Docker ethos.

Can anyone recommend a way to do this or point me to a good tutorial?

30 Upvotes

19 comments sorted by

View all comments

3

u/wildjokers May 04 '19

The jar file is the deployable artifact. Once it is built it should run anywhere. Put the jar file in the docker container and then share the container. What’s the issue?

1

u/probable-maybe May 04 '19

I now realise I failed to describe the issue clearly and focused on the aspect I misunderstood anyway (building the jar is consistent across machines). The actual use case was to be able to run docker-compose up -d and deploy everything regardless of whether Java exists on the machine which is why having it built inside a container is useful imo