-
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.container-image.push is ignored with buildpacks #23844
Comments
@lordofthejars: Using the exact same commands the image was pushed successfully (using quarkus 2.7.1.Final). One issue I see is that no log message appears, so the user can't tell what is going on until the registry is checked. |
Well I checked quay.io and I didn't see it, maybe there was some refresh issue and since no log was present I just thought that no push happened. I'll try again. |
Hi @geoand may I ask why closing it, I have not been able to make it work. I've shared the project too |
ah ok :D |
@iocanel can you take another look at this one? |
Yeah, looking at it right now! |
Thanks 🙏 |
The provided reproducer works for me, howver I still can't see the added log message. |
I wonder if the push problem has been solved. Neither can I push to Docker Hub nor quay.io though I can push the image manually via docker and podman or create it w/o problems with Jib and S2I. @lordofthejars - were you finally able to push the image to quay.io? |
Describe the bug
I just created a simple project with buildpacks extension registered then I set the buildpack image, I run the following command:
./mvnw clean package -DskipTests -Dquarkus.container-image.push=true
But no push was done.
Expected behavior
Image created and pushed
Actual behavior
The container is created but not pushed:
How to Reproduce?
Create a project with buildpacks extension and run
./mvnw clean package -DskipTests -Dquarkus.container-image.push=true
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.7.1
Build tool (ie. output of
mvnw --version
orgradlew --version
)mvnw
Additional information
No response
The text was updated successfully, but these errors were encountered: