You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, up to now it worked well for me to use the plugin with Podman using podman system service. However, I encountered the following problem today when using docker:push latest (formatted the output for better readability):
DOCKER> Unable to inspect image [sha256:e9685] :
{
"cause": "normalizing name for compat API: sha256:e9685: invalid format: no 64-byte hexadecimal value",
"message": "normalizing image: normalizing name for compat API: sha256:e9685: invalid format: no 64-byte hexadecimal value",
"response": 500
}
(Internal Server Error: 500)]
The reason seems to be that the plugin uses 5-byte hex shortcuts while the podman-docker-service requires the full 64-byte hex value.
Info
docker-maven-plugin version : 0.40.3
podman version: 4.3.1
Maven version (mvn -v) : 3.8.6
If it's a bug, how to reproduce : simply start the docker system service and use the docker:tag feature.
Description
Hi, up to now it worked well for me to use the plugin with Podman using
podman system service
. However, I encountered the following problem today when usingdocker:push latest
(formatted the output for better readability):The reason seems to be that the plugin uses 5-byte hex shortcuts while the podman-docker-service requires the full 64-byte hex value.
Info
mvn -v
) : 3.8.6docker system service
and use thedocker:tag
feature.Relates to #1330
The text was updated successfully, but these errors were encountered: