Compose does not work with a rootless podman machine on windows

[odockal]

Bug description

I am trying to use a compose installed through a Podman Desktop to spin up flask compose example 1. I am also having a default podman machine installed on laptop via podman desktop. This machine is rootless. On a cli, I run docker-compose.exe up -d in a flask folder and get: Error response from daemon: crun: creating cgroup directory /sys/fs/cgroup/misc/docker/buildx/libpod-e8e918dd83ea5605e3b70e5c37ccd65262eb0534377fb56d8ca29d02058f3dd9: No such file or directory: OCI runtime attempted to invoke a command that was not found

Operating system

Windows 10

Installation Method

Installer from website/GitHub releases

Version

next (development version)

Steps to reproduce

1. Checkout awesome-compose repo
2. Install podman desktop (1.3.0-next), install podman 4.6.1.
3. Initialize and start podman machine (podman-machine-default - gonna be rootless)
4. Install compose via download button (2.20.3)
5. Set it to be installed system wide
6. Open Cli and check availability of docker-compose.exe on a PATH
7. checkout to a folder with flask sample
8. Run DOCKER_HOST=npipe:////./pipe/podman-machine-default docker-compose.exe up -d
9. Assert: flask container are spin up correctly.
   Actual result:

Error response from daemon: crun: creating cgroup directory `/sys/fs/cgroup/misc/docker/buildx/libpod-e8e918dd83ea5605e3b70e5c37ccd65262eb0534377fb56d8ca29d02058f3dd9`: No such file or directory: OCI runtime attempted to invoke a command that was not found

Relevant log output

$ DOCKER_HOST=npipe:////./pipe/podman-machine-default docker-compose.exe up -d
#0 building with "default" instance using docker-container driver

#1 [web internal] booting buildkit
#1 starting container buildx_buildkit_default
#1 starting container buildx_buildkit_default 0.6s done
#1 ERROR: Error response from daemon: crun: creating cgroup directory `/sys/fs/cgroup/misc/docker/buildx/libpod-e8e918dd83ea5605e3b70e5c37ccd65262eb0534377fb56d8ca29d02058f3dd9`: No such file or directory: OCI runtime attempted to invoke a command that was not found
------
 > [web internal] booting buildkit:
------
Error response from daemon: crun: creating cgroup directory `/sys/fs/cgroup/misc/docker/buildx/libpod-e8e918dd83ea5605e3b70e5c37ccd65262eb0534377fb56d8ca29d02058f3dd9`: No such file or directory: OCI runtime attempted to invoke a command that was not found

Additional context

This is a sub issue for a #3535 which should help identify core problems with a compose. Could be upstream issue.

[cdrage]

On the new machine, were you able to reproduce this issue @odockal ?

I see that containers/podman#17042 was created, but want to confirm 100% if it's our end (PD) or not

[cdrage]

Closing this for now as I've just tried again and was unable to reproduce it.

I followed the same steps, but instead of getting: Error response from daemon: crun: creating cgroup directory /sys/fs/cgroup/misc/docker/buildx/libpod-e8e918dd83ea5605e3b70e5c37ccd65262eb0534377fb56d8ca29d02058f3dd9: No such file or directory: OCI runtime attempted to invoke a command that was not found

I was able to successfully bring up the flask application.

Let me know if this is still an issue and we'll re-open it!

[BjoernAkAManf]

Still running into this issue.
However this only occurs if podman requires to build.

This does not work:

docker-compose.yml

services:
#  alpine:
#    image: alpine:latest
  poc:
    build:
      context: poc
      args:
        VERSION_ALPINE: '3.18'

nginx/Dockerfile

ARG VERSION_ALPINE=latest
FROM alpine:${VERSION_ALPINE} as builder

This however does work:

services:
  alpine:
    image: alpine:latest
#  poc:
#    build:
#      context: poc
#      args:
#        VERSION_ALPINE: '3.18'

Building the Dockerfile also works:

podman build poc

Unsure if this is a Desktop issue, but i'd assume this is the same issue as above.

[krisdante]

I have the same on WIndows

[jeffmaury]

The command to use is podman compose up -d and not docker-compose up -d as buildkit is not supported.

[yunnysunny]

I have the same on WIndows

+1

[joaoopereira]

I had the same issue today, but after running podman machine set --rootful solved the issue

[SohanTirpude]

I had the same issue today, but after running podman machine set --rootful solved the issue

@joaoopereira, I tried your way but still I am seeing the same issue for celery. This is the exact error:

Error: unable to start container "c2e86e1945532d0cec3a3379582b4f30bea43d790462d3277f79f1d6e2587244": crun: executable file `celery` not found in $PATH: No such file or directory: OCI runtime attempted to invoke a command that was not found
exit code: 125

[joaoopereira]

@SohanTirpude what are you trying to run?

[SohanTirpude]

@joaoopereira please ignore. I managed to solve somehow but I don't remember now. Thanks anyway.