-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
quarkus/jib: Native build fails if docker isn't installed #24231
Comments
/cc @geoand |
What you are seeing is the expected behavior.
I assume you mean with this that building the native binary is done with podman without you having to configure anything? |
@geoand Correct - like
|
@metacosm FYI |
Gotcha, thanks . I'll bring it in line with what we do for the native build |
The detection uses the same method Quarkus already used when building the native binary using a container build Fixes: quarkusio#24231
Detect container runtime when using Jib
Thank you for your quick fix ! |
The detection uses the same method Quarkus already used when building the native binary using a container build Fixes: quarkusio#24231 (cherry picked from commit a6745e0)
@jesperpedersen 2.7.5.Final has been released. |
Already? Damn, I barely had time to release the extension with 2.7.4! 😁 |
Describe the bug
mvn clean package -Pnative
Fails with
since
docker
isn't installed. The build up to this point have usedpodman
successfully.Expected behavior
To be able to use
podman
for the entire buildActual behavior
docker
is required - e.g.podman
isn't detectedHow to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
JDK14
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.7.3.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)Maven 3.8.4
Additional information
Workaround: Using
and the build is successful.
Code: extensions/container-image/container-image-jib/deployment/src/main/java/io/quarkus/container/image/jib/deployment/JibProcessor.java
The text was updated successfully, but these errors were encountered: