You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using devcontainers with docker desktop, and mounting in a barcode reader (a Datalogic GFS4520, as a USB-COM serial device).
I can mount the device to the host distro, and it shows up with ls and lsusb, however it mounts as:
crw------- 1 root root 166, 0 Aug 9 20:32 /dev/ttyACM0
... and not the proper
crw-rw---- 1 root dialout 166, 0 Aug 9 20:39 /dev/ttyACM0
... which then causes various problems inside my devcontainer.
I can work around this by attaching to another distro (in this case a manual Ubuntu installation). However this is obviously not ideal.
This is less a problem with docker itself and more an issue with setup of the host distro in WSL.
Reproduce
Somehow acquire a Datalogic Gryphon 4520 (other serial devices may behave similarly, but this is the device I have)
Install usbipd-win via winget install -e --id dorssel.usbipd-win
Restart computer
The hardware id of the specified Datalogic device is 05f9:4204. If you're using a different device, you can find it via usbipd list
Bind the device. From an elevated command prompt run usbipd bind -i <device id>
From a normal command prompt, run usbipd attach -i <device id> --wsl docker-desktop
Run ls -al /dev/ttyA* from the docker-desktop distro, and observe that the group/permissions are wrong.
Expected behavior
The bound device should have the correct group/permissions.
My devcontainer is using a compose file which contains the following:
services:
app:
image: mcr.microsoft.com/devcontainers/dotnet:1.1.9-8.0-bookwormports:
- "5020:5020"# Overrides default command so things don't shut down after the process ends.command: sleep infinitygroup_add:
- dialout # Required for accessing serial devicesdevices:
- /dev/ttyACM0
... but that of course only adds the group to the container user, not modify the group on the device in the container (and of course can't change the group on the host, which would be more relevant).
The text was updated successfully, but these errors were encountered:
Description
I'm using devcontainers with docker desktop, and mounting in a barcode reader (a Datalogic GFS4520, as a USB-COM serial device).
I can mount the device to the host distro, and it shows up with
ls
andlsusb
, however it mounts as:... and not the proper
... which then causes various problems inside my devcontainer.
I can work around this by attaching to another distro (in this case a manual Ubuntu installation). However this is obviously not ideal.
This is less a problem with docker itself and more an issue with setup of the host distro in WSL.
Reproduce
winget install -e --id dorssel.usbipd-win
05f9:4204
. If you're using a different device, you can find it viausbipd list
usbipd bind -i <device id>
usbipd attach -i <device id> --wsl docker-desktop
ls -al /dev/ttyA*
from thedocker-desktop
distro, and observe that the group/permissions are wrong.Expected behavior
The bound device should have the correct group/permissions.
docker version
Client: Version: 27.1.1 API version: 1.46 Go version: go1.21.12 Git commit: 6312585 Built: Tue Jul 23 19:57:57 2024 OS/Arch: windows/amd64 Context: desktop-linux Server: Docker Desktop 4.33.1 (161083) Engine: Version: 27.1.1 API version: 1.46 (minimum version 1.24) Go version: go1.21.12 Git commit: cc13f95 Built: Tue Jul 23 19:57:19 2024 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.7.19 GitCommit: 2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41 runc: Version: 1.7.19 GitCommit: v1.1.13-0-g58aa920 docker-init: Version: 0.19.0 GitCommit: de40ad0
docker info
Diagnostics ID
0367124B-409E-4810-9084-D63AB8576470/20240810171012
Additional Info
Possibly related to #13940
My devcontainer is using a compose file which contains the following:
... but that of course only adds the group to the container user, not modify the group on the device in the container (and of course can't change the group on the host, which would be more relevant).
The text was updated successfully, but these errors were encountered: