Update Dockerfile.jvm #939
Conversation
…nache-quickstart It doesn't need to use the maven-docker-plugin anymore (cherry picked from commit 58de52d)
(cherry picked from commit 7a3a16b)
(cherry picked from commit 167379b)
(cherry picked from commit 6c80fcc)
(cherry picked from commit 168ebbd)
(cherry picked from commit f130948)
(cherry picked from commit 1dda1b5)
(cherry picked from commit 2e1b010)
(cherry picked from commit 14218b3)
(cherry picked from commit 807d196)
The Dockerfile didn't run with Kaniko with gitlab-ci. The separated chown did solve the problem
|
What's the error displayed by Kaniko? |
|
error building image: error building stage: failed to get files used from context: failed to get fileinfo for /builds/playground108/logproducer/target/quarkus-app/lib: lstat /builds/playground108/logproducer/target/quarkus-app/lib: no such file or directory As far as I understood, the --chown flag was introduced with docker-ce version 17.09 (see: https://stackoverflow.com/questions/44766665/how-do-i-docker-copy-as-non-root). It might be the case, that some builder like kaniko or moby does not support it. Might is connected to |
|
Looking at the issue, it seems to be a kaniko limitation. Hopefully, it will be fixed soon. |
|
The PR does not target the right branch, please update to use the |
|
switch to #943 |
The Dockerfile didn't run with Kaniko on gitlab-ci. The separated chown did solve the problem.
I think Quarkus should be as compatible as possible and not only work with docker an builder.
Check list:
Your pull request:
developmentbranch999-SNAPSHOTversion of Quarkusmvn clean test)mvn clean package -Pnative)mvn clean verify -Pnative)README.mdfile (with build and run instructions)pom.xmlandREADME.md