podman-compose run ignore --no-deps

[khassad]

Describe the bug
podman-compose run --no-deps fails when the related containers doesn't exist since it generate a full podman run with all the --requires dependencies, which is wrong.

Expected behavior
--no-deps should not generate any --requires in the podman run command

Actual behavior
podman-compose generates a podman run command with a complete --requires= option, which fails.

$ podman-compose version
podman-compose version: 1.0.7
['podman', '--version', '']
using podman version: 4.5.1
podman-compose version 1.0.7
podman --version
podman version 4.5.1
exit code: 0

Environment:

• OS: Linux
• podman version: 4.5.1
• podman compose version: latest devel (1.0.7)

Additional context

Seems to be linked to #398

[jonathanspw]

+1

[Dongw1126]

Is there an update for this issue? I have the same issue in version 1.1.0.

[findurance]

podman-compose version 1.2.0
podman version 5.2.1

I'm seeing this issue too. Have a docker-compose.yml and it runs good mostly, but --no-deps has no effect when starting a container. I need to comment out the depends_on: -section, when I want to run a dependee container with Podman.

Example: 'mycontainer' has

depends_on: 
  - yourcontainer 

Then running the 'mycontainer': podman compose -f docker-compose.yml up --no-deps mycontainer

But after that podman ps lists two containers running, e.g. podman container ps --format "{{.Names}}"

yourcontainer
mycontainer

Since --no-deps was used, there should only be one container running, 'mycontainer'