MAC OS Docker Desktop unable to connect Serial device running micro-ros-agent image
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 59
- Forks
- 32
- Avg merge
- 16m
- Merged PRs (30d)
- 1
Description
## Issue template
- Hardware description: MAC M1 Sierra Docker Desktop 4.42 Engine Version 28.2.2. Raspberry Pico with USB
- RTOS: Following https://github.com/hippo5329/micro_ros_arduino_examples_platformio/wiki#install-the-software-tools
- Installation type: Pulled microros/micro-ros-agent:jazzy
- Version or commit hash: micro_ros_version 5.0.0
#### Steps to reproduce the issue
Verified Serial port name:
Ross@Kepler ~ % ls /dev/cu*
/dev/cu.Bluetooth-Incoming-Port /dev/cu.usbmodem1301
Start Docker Desktop, % docker run -it --net=host --device=/dev/cu.usbmodem1301 microros/micro-ros-agent:jazzy serial
#### Expected behavior
Connect to Pico USB Port
#### Actual behavior
docker: Error response from daemon: error gathering device information while adding custom device "/dev/cu.usbmodem1301": no such file or directory
Run 'docker run --help' for more information
#### Additional information
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported Docker Desktop command using /dev/cu.usbmodem1301 and the microros/micro-ros-agent:jazzy image. Investigate how the macOS serial device is exposed to Docker, and consider the issue done when the image can connect to the Raspberry Pico over USB.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, macos
- Domain
- devops, embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100