Describe the bug

from docker-compose.yaml

devices: - /dev/tty.usbserial-830:/dev/tty.usbserial-830

results in "Error response from daemon: error gathering device information while adding custom device "/dev/tty.usbserial-830": not a device node"

and if I try mapping it as a file, i.e. in docker-compose.yaml:

volumes: - /dev/tty.usbserial-830:/dev/tty.usbserial-830

it results in that path being created as a directory in the container. Argh.

To me - it seems that simple mapping of the serial device file should "just work". It's a simple serial device. I want to access it in a container hosted by OrbStack. Simply. Thus far I've found no way to do so. Open to any suggestions on on alternatives to access the serial device within the container, given I don't want to run a VM to do so, nor do want to run a process on the host itself outside of the docker environment.

To Reproduce

No response

Expected behavior

No response

Diagnostic report (REQUIRED)

OrbStack info:
Version: 2.0.5
Commit: cfe47627f138ffd822c958553b0a93eaf2692c71 (v2.0.5)

System info:
macOS: 26.4 (25E246)
CPU: arm64, 10 cores
CPU model: Apple M2 Pro
Model: Mac14,12
Memory: 32 GiB

Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2026-03-24T22-41-37.588218Z.zip

Screenshots and additional context (optional)

No response