-
Notifications
You must be signed in to change notification settings - Fork 85
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
could not open port /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0: #64
Comments
I found a solution, which is logging in to the Klipper docker as root and manually changing the group of the dev to dialout. I'm trying to see how to accomplish this in the docker-compose file, but would be nice to:
|
I ran into the same problem on an Arch-based distribution (EndeavourOS). |
@Abikebuk awesome I was helpful! Spent several hours on this :) Im also using Arch, but in the form of ArchlinuxARM. I made a little script to set the permissions after the container is running:
|
This might not be the best solution, but I normally add a udev rule on the host, for the USB-device, granting access. At the same time, I add a fixed device path (think /dev/usbRUMBA) to make life easier. |
Thanks Pip, thats a good one to try, should work after every reboot. Until this gets fixed in the docker-compose script. |
@Pipshag I have to specifilcally set it to dialout with my script:
crw-rw---- 1 root dialout 188, 0 Mar 31 01:08 ender6 |
Please run the following commands on your host before any permissions have been modified.
Without any further info, the solution proposed by @Pipshag makes most sense to me, as long as you use numeric groupids in the udev rule, not named groupids. -Markus |
Looks like using numbers instead of text worked:
This code is for a CUBOXi4-Pro. Dont know if you Markus can implement something automated or its not necessary, but looks like at least two already had to do some workarounds with permissions. At the very minimum we need another bullet point in the troubleshooting section of the Readme. |
Could you share the output of the commands I mentioned? Without any further info I can not assess if a automated solution can be implemented into the project. |
|
I think you will also want this:
|
Ok, so there is nothing I can do in docker or compose that could fix the mismatching groupids. This would inevitably break if someone uses another distro with completely different groupids again. Creating a udev rule on the host is the simplest solution to fix this. -Markus |
Hey there. What permissions should i have in both, the metal and docker to let Klipper access the device? And also, how do i set them in the docker container? I dont know the root password of it.
Thanks!
The text was updated successfully, but these errors were encountered: