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
I'm using docker-maven-plugin with podman, which was working fine so far.
After I added the configuration for a specific build platform (linux/amd64), the builds fails with
[INFO] DOCKER> [my/project:latest]: Created docker-build.tar in 1 second
[WARNING] DOCKER> Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
[WARNING] DOCKER> time="2024-10-16T18:53:27+02:00" level=warning msg="The --config flag is ignored by Podman. Exists for Docker compatibility"
[WARNING] DOCKER> Error: unrecognized command `podman buildx ls`
[WARNING] DOCKER> Try 'podman buildx --help' for more information
[INFO] DOCKER> docker --config /var/lib/jenkins/workspace/dummy_develop/blafasel/target/drum-dev/.docker.build/my/project/latest/docker buildx create --driver docker-container --name maven
[INFO] DOCKER> Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
[INFO] DOCKER> Error: unknown flag: --driver
[INFO] DOCKER> See 'podman buildx --help'
[ERROR] DOCKER> Error status (125) while creating builder maven
The section added to the docker-maven-plugin config (in "configuration.images.image.build") was:
This looks a bit strange. We use docker CLI for doing buildx based builds. Do you know if podman has complete support for buildx? Or maybe command name is different in case of podman?
Description
I'm using docker-maven-plugin with podman, which was working fine so far.
After I added the configuration for a specific build platform (linux/amd64), the builds fails with
The section added to the docker-maven-plugin config (in "configuration.images.image.build") was:
With
docker.platforms = linux/amd64
.NOTE:
linux/amd64
is the native platform architecture. An alternate profile shall also perform builds forlinux/arm64
.Info
mvn -v
) :DockerPodman version : 4.9.4-rhelIt should probably sufficient to add the above buildx config to trigger the error.
The text was updated successfully, but these errors were encountered: