-
Notifications
You must be signed in to change notification settings - Fork 41.1k
Invalid reference format error when tagging images using Podman #35358
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
Comments
I have something in this branch, what do you think @scottfrederick ? |
mhalbritter
added a commit
that referenced
this issue
May 11, 2023
mhalbritter
added a commit
that referenced
this issue
May 11, 2023
That was fast! Thanks @mhalbritter ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
The
bootBuildImage
task encounters an error configuring tags when using Podman instead of Docker.Example config:
Error:
Diagnosis
DockerApi::tag
uses a single query parameter (repo
) for the target reference:spring-boot/spring-boot-project/spring-boot-tools/spring-boot-buildpack-platform/src/main/java/org/springframework/boot/buildpack/platform/docker/DockerApi.java
Line 349 in 21406e7
The Docker Engine API accepts both
repo
andtag
parameters, but it parsesrepo
iftag
is not specified. Podman does not currently support this behavior.API reference: https://docs.podman.io/en/v3.2.3/_static/api.html#tag/images/operation/ImageTagLibpod
Example request (current behavior)
This fails with podman 4.5.0:
curl --unix-socket /var/run/docker.sock -v -X POST \ "http://localhost/v1.24/images/example.org/example-service:1.0.0/tag?repo=example.org%2Fexample-service%3Alatest"
Podman returns the following:
Updated request (desired behavior)
This request includes separate
repo
andtag
parameters and works with podman 4.5.0:curl --unix-socket /var/run/docker.sock -v -X POST \ "http://localhost/v1.24/images/example.org/example-service:1.0.0/tag?repo=example.org%2Fexample-service&tag=latest"
Workaround
The text was updated successfully, but these errors were encountered: