Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

podman-compose does not respect -v mount parameter for run #464

Closed
diodakus opened this issue Mar 29, 2022 · 1 comment
Closed

podman-compose does not respect -v mount parameter for run #464

diodakus opened this issue Mar 29, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@diodakus
Copy link

diodakus commented Mar 29, 2022

Describe the bug
podman-compose not respect -v mount parameter for run.

To Reproduce
Steps to reproduce the behavior:

  1. create docker-compose.yml file according below content:
version: '3.5'
services:
  sh:
    command: [/bin/sh]
    image: busybox
    volumes:
      - /tmp/service_sh:/tmp/service_sh:rw
  1. Run command: podman-compose run -v /tmp/test:/tmp/test sh sh

Expected behavior
two mounts:

  • /tmp/service_sh:/tmp/service_sh - from docker-compose.yml
  • /tmp/test:/tmp/test - from command line

podman run --name=slawek_sh_tmp35209 --rm -i --pod=pod_slawek --label io.podman.compose.config-hash=8046c9387919915040c14f6ec8fba1058b3ba36d6880deafbb67234245f55384 --label io.podman.compose.project=slawek --label io.podman.compose.version=1.0.4 --label com.docker.compose.project=slawek --label com.docker.compose.project.working_dir=/home/slawek --label com.docker.compose.project.config_files=docker-compose.yml --label com.docker.compose.container-number=1 --label com.docker.compose.service=sh -v /tmp/service_sh:/tmp/service_sh:rw -v /tmp/test:/tmp/test --net slawek_default --network-alias sh --tty busybox sh

Actual behavior

  • /tmp/service_sh - only one mount from docker-compose.yml
    podman run --name=slawek_sh_tmp35209 --rm -i --pod=pod_slawek --label io.podman.compose.config-hash=8046c9387919915040c14f6ec8fba1058b3ba36d6880deafbb67234245f55384 --label io.podman.compose.project=slawek --label io.podman.compose.version=1.0.4 --label com.docker.compose.project=slawek --label com.docker.compose.project.working_dir=/home/slawek --label com.docker.compose.project.config_files=docker-compose.yml --label com.docker.compose.container-number=1 --label com.docker.compose.service=sh -v /tmp/service_sh:/tmp/service_sh:rw --net slawek_default --network-alias sh --tty busybox sh

Output

$ podman-compose version # Version from 28.03.2022 with fix for https://github.com/containers/podman-compose/issues/462 
podman-compose version: 1.0.4
['podman', '--version', '']
using podman version: 3.4.2
podman-composer version 1.0.4
podman --version 
podman version 3.4.2
exit code: 0

Environment:

  • OS: Rocky Linux release 8.5 (Green Obsidian)
  • podman version: 3.4.2
  • podman compose version: (git hex): fc34703

Additional context

Sometimes I need to add to run some extra mount parameter by -v from command line - like in docker-compose.

@diodakus diodakus added the bug Something isn't working label Mar 29, 2022
@diodakus diodakus changed the title podman-compose not respect -v mount parameter for run podman-compose does not respect -v mount parameter for run Mar 29, 2022
@diodakus
Copy link
Author

@muayyad-alsadi I confirm that issue were solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant