You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Quarkus team. Nowadays I am taking a look at Quarkus and trying to implement a small app. First of all, thanks a lot for this great work! Developer experience is really king with this framework.
When I checked the Dockerfiles in Quarkus projects, I saw that Dockerfiles are not self-contained. We need to run mvn/gradle to create runnable JAR files or native binaries at first and then we can run docker build commands. Also, maven runs docker run to create native binaries from runnable jar files.
I think this is not a good way. Here are my arguments.
It is not elegant. It doesn't fit the philosophy "Developer experience is king."
It may a problem in modern CI/CD tools. Many CI/CD tools let you run some commands inside docker containers. You can run mvn inside a docker container but you are not allowed to run another container via a process in the container.
Implementation ideas
If Quarkus is a modern, cloud-native framework, I believe it should use multi-stage builds and isolate build processes from host machines.
Description
Hi Quarkus team. Nowadays I am taking a look at Quarkus and trying to implement a small app. First of all, thanks a lot for this great work! Developer experience is really king with this framework.
When I checked the Dockerfiles in Quarkus projects, I saw that Dockerfiles are not self-contained. We need to run mvn/gradle to create runnable JAR files or native binaries at first and then we can run
docker build
commands. Also, maven runsdocker run
to create native binaries from runnable jar files.I think this is not a good way. Here are my arguments.
mvn
inside a docker container but you are not allowed to run another container via a process in the container.Implementation ideas
If Quarkus is a modern, cloud-native framework, I believe it should use multi-stage builds and isolate build processes from host machines.
I have prepared an example here: https://github.com/erkanerol/quarkus-multistage-docker-build
The text was updated successfully, but these errors were encountered: