Replies: 2 comments 1 reply
-
I think this is an assumption made by docker compose code itself ? I would need to verify that but I have a vague recollection about this. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I am pretty sure this is enforced by the compat API to match docker behavior. You can set compat_api_enforce_docker_hub=false in containers.conf to disable this AFAIK. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Issue Description
When building an image with docker-compose, its name is prefixed with the
docker.io/library
registry name instead oflocalhost
.Steps to reproduce the issue
Steps to reproduce the issue
docker-compose
, so that it is usable bypodman compose
Dockerfile
file with content:FROM scratch
compose.yaml
in the same directory with content:podman compose build
in this directoryDescribe the results you received
A new image was created with name
docker.io/library/test-project-test-service
:Describe the results you expected
The created image should use the name
localhost/test-project-test-service
.podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Docker Compose version v2.30.1
Additional information
Beta Was this translation helpful? Give feedback.
All reactions