Everything posted by abra5umente
-
[Support] Octoprint docker template - Spants
Latest stable, 6.9.2. I've moved my docker to a folder rather than an image - but another strange thing is I added a camera and installed the drivers etc, but now 50% of the time when I restart Octoprint the camera port changes. Last night I restarted it and it grabbed my USB backup drive as the printer port. Got no idea what's going on with it, but I can work around it by just rebuilding the container every day.
-
[Support] Octoprint docker template - Spants
Had to wait for it to do a backup before I could show it. It does this - I had previously removed the webcam device key, as well as ENABLE_MJPG_STREAMER, CAMERA_DEV, MJPG_STREAMER_INPUT, webcam, and snapshot. All I had was the printer USB port key - as you can see it's removed the printer USB port and replaced it with webcam device, which means the container doesn't start. Now that I think about it - it could be because the printer is not powered on when it does a backup, so when it comes back the USB device does not exist, but I don't know why it would change the template. I'll try creating an automation to turn the printer on during the backup window - however I have also tried setting community apps backup to ignore the octoprint folder, but it still happens. I've had plenty of containers where I've edited the templates and I've never had this happen.
-
[Support] Octoprint docker template - Spants
Thanks - I do use the By-Id method - the issue is that the template changes the key from printer port to camera port - so it thinks the camera should be my printer.
-
[Support] Octoprint docker template - Spants
It seems as though every day this breaks for me - when I restart the docker after doing a backup, it moves all the keys around, resulting in the key for the USB ID of the printer being changed to the setting for camera, etc. I don't have a camera plugged in and I have removed those entries to allow it to start - it works fine until it restarts and then it dies, so I have to reinstall it again. Any workaround?