Markus Küffner

> Would love to work on this, but as stated in #332 I don't have a multi-extruder printer to test this on, which makes it really hard for me to...

My first reaction would be to set udev rules as @ximikator suggested. Check the file permissions on your printers serial port. ``` ls -al /dev docker compose exec klipper ls...

Hi There, when it comes to competing requirements I'd argue that the small Image is a common denominator for all Klipper users, as it contains the same things as a...

Hi there, please execute the get-info script from the root of the repository and upload it again. It seems your pwd was `/scripts` when executing the script. This causes it...

Please be patient. I also have other obligations and hadn't found any Time to dive into your issue. Where there any errors displayed when you started the stack? The runtime-info...

The ShellCommandError is expected, as the process is running isolated in docker. With adding the privileged flag you cancel this isolation and grant the container access to your host. This...

@jmis please also execute the latest version of the get-info script as mentioned in https://github.com/mkuf/prind/issues/38#issuecomment-1252584536 and upload the archive here.

@pelaxa > ok. here is the get-info details from before my change [prind-info-21092022-172030.tar.gz](https://github.com/mkuf/prind/files/9619758/prind-info-21092022-172030.tar.gz) This archive was generated using the outdated get-info script. Please update the Prind repository on your host...

Thanks, @jmis. You're not using the compose file from this repository to start your stack. Therefore the get-info script did not export the logs for your moonraker and klipper containers....

Closing this issue as it is missing Troubleshooting information. Feel free to open a new issue if you'd like to further troubleshoot this. -Markus