octoprint-docker VS dockerfiles

I set up Octoprint in a Docker Container and used the docker compose from github (https://github.com/OctoPrint/octoprint-docker/blob/master/docker-compose.yml)

And my 71-octoprint.docker.rules sourced from this piece of documentation where /dev/byregot_temp is where the printer is to be mounted in the container.

I have a host machine with Docker that I would like to control two printers over USB using the Docker image. The printers won't always be powered, and when they're on, won't necessarily be on at the same time/powered in the same order. This results in them being mounted to different locations depending on which is powered first. I have been looking through similar posts such as this and this which had some great answers from the maintainer of the image.

And after this, you can run the docker image of octopi https://github.com/OctoPrint/octoprint-docker

Have a look here https://github.com/OctoPrint/octoprint-docker very easy and simple to setup, takes 5 min

OctoPrint is not designed to be used as outlined in this tutorial as such there are known issues; refer here for documentation. Furthermore, since this is an unsupported configuration do NOT contact the developers of OctoPrint nor those of your printer's firmware with troubleshooting or bug reporting. Think of it this way, imagine you paid for OctoPrint or some really awesome community firmware and it came with a lifetime warranty, by proceeding with this guide you would be voiding that warranty. But, guess what? You did not and it does not so you have less than zero right to ask for, much less expect any level of support from them. That said, should you have issues I will try my best to help, but I am not a linux Yoda, I'm not even a bash Grogu (I'm just a random self-taught internet dude with slightly below average intelligence who fancies bending machines to his will like Professor Xavier does minds; SkyNet will find no quarters on my networks or devices!) so it's best to continue with the mindset that basically you're on your own from here on out. If anything I say is imprecise or inaccurate, please kindly let me know and I will make the appropriate edits.

https://blog.jessfraz.com/post/docker-containers-on-the-desk... is the one I remember, a bit old but still useful to see how she does it.

Seems super painful and indirected for a nebulous gain to me, but find your joy however you want I guess

Jess does some awesome stuff and this is literally what you asked for. hollywood

mildly relevant https://blog.jessfraz.com/post/docker-containers-on-the-desktop/

Some of my day-to-day software.

After knowing that saved Chrome passwords and cookies in Linux are not protected against malicious dependencies in our development environment or other apps in our system, I decided to run my core apps in Docker containers, where their data is not accessible without sudo, and a personal understanding of where stuff is being saved.

These docker containers are also an improved version of https://github.com/jessfraz/dockerfiles/

Contrary to the project above, docker-workspaces runs Chrome in a sandbox, encrypts keys with the help of an also dockerized gnome-keychain, and works in tandem with pulseaudio, so you can use wired headphones (i still need to add some dependencies for it to work with bluetooth headphones).

Thank you. As someone who uses containers a lot (even to run local programs, shout out to https://blog.jessfraz.com/post/docker-containers-on-the-desk...) this makes some sense to me.

I'm a little way into the Nix Pills document (https://nixos.org/guides/nix-pills/why-you-should-give-it-a-...) which seems to start the explanation from a place where I can understand.