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

Docker-compose crash if service mount device with colon in path #7909

Closed
flucciarini opened this issue Nov 4, 2020 · 7 comments
Closed

Docker-compose crash if service mount device with colon in path #7909

flucciarini opened this issue Nov 4, 2020 · 7 comments

Comments

@flucciarini
Copy link

Hi everyone,
I need to mount in service a host's path with colon (real case below) but docker-compose when start fail
How can escape or encode comma?
...
devices:
- "/sys/bus/iio/devices/iio::device0:/sys/bus/iio/devices/iio::device0:rw"
....

$ docker-compose up -d
...
Creating edgex-device-gpio ... error

ERROR: for edgex-device-gpio Cannot start service device-gpio: error gathering device information while adding custom device "/sys/bus/iio/devices/iio": no such file or directory

ERROR: for device-gpio Cannot start service device-gpio: error gathering device information while adding custom device "/sys/bus/iio/devices/iio": no such file or directory
ERROR: Encountered errors while bringing up the project.

$ docker-compose -version
docker-compose version 1.27.2, build 18f557f

SO: Ubuntu 18.04

@flucciarini flucciarini changed the title Docker-compose.yaml crash if service mount device with colon in path Docker-compose crash if service mount device with colon in path Nov 4, 2020
@yogeshk04
Copy link

@flucciarini Have you found the solution to this issue?
I'm facing the same issue.

@flucciarini
Copy link
Author

flucciarini commented Apr 11, 2021 via email

@pathros
Copy link

pathros commented Jul 12, 2021

@flucciarini Could you please give more details?

  • The symbolic link command
  • And the docker-compose.yml file code

@stale
Copy link

stale bot commented Apr 16, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Apr 16, 2022
@stale
Copy link

stale bot commented Apr 27, 2022

This issue has been automatically closed because it had not recent activity during the stale period.

@stale stale bot closed this as completed Apr 27, 2022
@huapox
Copy link

huapox commented May 3, 2023

+1

err with - ./.ctd/k3s-registry-cert.crt:/etc/docker/certs.d/server.k8s.local:18443/cert.crt

@huapox
Copy link

huapox commented May 3, 2023

ref #5363

    - type: bind
      source: ./.ctd/k3s-registry-cert.crt
      target: /etc/docker/certs.d/server.k8s.local:18443/cert.crt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants