-
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
Automatic build of Docker image fails when running with podman #28721
Comments
@gastaldi any chance you can take a look at this one? |
@geoand I using a mac and don't have Fedora in my machine 😞 Let me see if I can reproduce that in a VM |
Oh, I thought you were on Fedora |
I have to pass, I tried but had no luck without requiring payment 😞 |
It makes me think we should be running some of the native tests on M1. That's a different OS, but it's also podman so will flush out some of these issues. Or, alternatively, we could have a matrix job which ran on the normal hardware but forced podman as the container runtime. |
fixed by #41100 |
Thanks for checking! |
Describe the bug
I have an application with
quarkus-resteasy-jackson
andquarkus-container-image-docker
dependecies and with propertyquarkus.container-image.build
set to true. When I runmvn clean package
while using docker as a contanier runtime, everything works as expected. When I run the same command, while using podman socket I get an error.Expected behavior
Result of build command should not depend on used container runtime.
Actual behavior
How to Reproduce?
[email protected]:fedinskiy/reproducer.git -b reproducer/build-podman
a.
sudo dnf install podman podman-docker
b .
systemctl --user enable podman.socket --now
c.
export DOCKER_HOST=unix:///run/user/${UID}/podman/podman.sock && export TESTCONTAINERS_RYUK_DISABLED=true
mvn clean package
If step 2 is ommited, everything works as expected.
For comparison, manual build works flawlessly:
mvn clean package -Dquarkus.container-image.build=false
podman build -f src/main/docker/Dockerfile.jvm -t quarkus/getting-started-jvm .
Output of
uname -a
orver
5.19.11-200.fc36.x86_64
Output of
java -version
11.0.16 temurin
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.13.3.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Additional information
podman version 4.2.1
Docker version 20.10.19, build d85ef84
The text was updated successfully, but these errors were encountered: