Exposing a tty serial device requires privileged and doesn't work

### Expected behavior That I can expose a tty dev device from my mac to a linux container by running. ``` $ docker run --rm -it -v `pwd`:/app --device /dev/tty.usbmodem1421 node bash ``` ### Actual behavior ``` $ docker run --rm -it -v `pwd`:/app --device /dev/tty.usbmodem1421 node bash docker: Error response from daemon: linux runtime spec devices: error gathering device information while adding custom device "/dev/tty.usbmodem1421": lstat /dev/tty.usbmodem1421: no such file or directory. ``` I can work past this with `--privileged` but I don't see it in `/dev/` ``` $ docker run --rm -it -v `pwd`:/app --device /dev/tty.usbmodem1421 --privileged node bash root@5a6a7f6b8e58:/# ls /dev/tty.* ls: cannot access /dev/tty.*: No such file or directory ``` According to the docs on docker run I shouldn't need `--privileged`. ### Information - Full output of the diagnostics from "Diagnose & Feedback" in the menu ``` Docker for Mac: version: 1.12.3-beta29.3 (619507e) OS X: version 10.12.1 (build: 16B2555) logs: /tmp/E9C6B44E-7492-484A-A6EF-EE5BE163959F/20161105-153323.tar.gz [OK] vmnetd [OK] dns [OK] driver.amd64-linux [OK] virtualization VT-X [OK] app [OK] moby [OK] system [OK] moby-syslog [OK] db [OK] env [OK] virtualization kern.hv_support [OK] slirp [OK] osxfs [OK] moby-console [OK] logs [OK] docker-cli [OK] menubar [OK] disk ``` - Page URL if this is a docs issue or the name of a man page https://doc

Posted by reconbot on Nov 5, 2016, 7:37 PM

Tags

• github (SaaS)

Related issues

• 2026 - Microsoft Office 365
• [Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
• Gamut mapping
• [Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
• [Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
• [BUG]: infinite loading of videos