Closed TomaszGasior closed 1 year ago
which docker-compose is this?
which docker-compose is this?
Sorry but I don't understand. Could you please explain? :)
Are you using the python docker-compose or the go-based docker compose.
It's already specified in issue description: I provided RPM package version. That's Python-based implementation with -
in the name.
can you strace the docker-compose command? i think i remember that docker compose python actually also calls the docker binary for a couple of things?
Using simple technique with overriding docker binary by script which logs all arguments I found that docker-compose actually does something simple:
docker build --tag SOME_NAME --iidfile SOME_TMP_FILE PATH_TO_DIRECTORY_CONTAINING_DOCKERFILE
The thing is docker build
with DOCKER_HOST set to Podman just does not work, completely. Just bare docker build DIRECTORY
does not work causing the following error while podman build DIRECTORY
works properly.
request returned Bad Request for API route and version http://%2Frun%2Fuser%2F1000%2Fpodman%2Fpodman.sock/v1.41/build?buildargs=%7B%7D&cachefrom=%5B%5D&cgroupparent=&cpuperiod=0&cpuquota=0&cpusetcpus=&cpusetmems=&cpushares=0&dockerfile=Dockerfile&labels=%7B%7D&memory=0&memswap=0&networkmode=default&rm=1&shmsize=0&target=&ulimits=null&version=1, check if the server supports the requested API version
For example you can try podman build container/http/
vs docker build container/http/
with CWD in linked repository.
docker-compose up
running through strace: strace.txt
docker binary version:
[tomasz@fedora RadioLista-v3]$ docker --version
Docker version 20.10.21, build baeda1f
[tomasz@fedora RadioLista-v3]$ rpm -q moby-engine
moby-engine-20.10.21-1.fc37.x86_64
I am pretty sure this was fixed in https://github.com/containers/podman/pull/16380, this should be fixed in podman v4.4, the cachefrom param is causing this. Duplicate of #15928
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
The problem is similar to https://github.com/containers/podman/issues/12206 but error message is different so I decided to create new issue for that.
I have user-wide podman service enabled (
systemctl enable --now --user podman.socket
) and I haveDOCKER_HOST=unix://$XDG_RUNTIME_DIR/podman/podman.sock
in my environment. I have both dockerd, docker binary and podman installed in my OS (Fedora 37 in clean VM). docker-compose invokes docker binary and that binary cannot communicate with podman-provided API.I want to have podman working with docker-compose without need to uninstall docker from my OS.
Steps to reproduce the issue:
Environment:
When I want to just work on my project:
Describe the results you received:
(Error occurs when images are not built yet only.)
I have to remove docker from my OS and install docker binary from podman-docker to make it working:
Then
docker-compose up
works.Describe the results you expected:
I don't have to install fake docker binary pointing to podman to make podman working with docker-compose. I don't have to use wrapping script like in the previous issue https://github.com/containers/podman/issues/12206.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info
:Package info (e.g. output of
rpm -q podman
orapt list podman
orbrew info podman
):also
Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
Fedora 37 clean VM