62 lines
2.9 KiB
Markdown
62 lines
2.9 KiB
Markdown
# OctoPrint-Klipper
|
|
|
|
My version of a Docker image for running [OctoPrint] and [Klipper] in a single container. Includes a few plugins I find useful.
|
|
|
|
Big thanks to [sillyfrog](https://github.com/sillyfrog) for laying the groundwork for this image.
|
|
|
|
This is very much written for my purposes, so you'll likely need to modify it for your setup. I've been using it for a while now and it's going well. I've successfully run it on these platforms:
|
|
* Orange Pi Zero 512MB
|
|
* AtomicPi
|
|
* Raspberry Pi 4B 1GB (current source of `arm` images)
|
|
|
|
## Running the container
|
|
|
|
Create a directory on your host that will persist config files. I use `/home/docker/octoprint-klipper`.
|
|
|
|
Pull the image. Until I figure out multi platform aware images, you need to specify your arch. Both `arm` and `amd64` images are on DockerHub. If using Raspberry Pi or similar use `arm` in place of `[tag]`.
|
|
|
|
```shell
|
|
docker pull seanauff/octoprint-klipper:[tag]
|
|
```
|
|
|
|
Start the container once to populate your config folder:
|
|
|
|
```
|
|
docker run -d --name octoprint-klipper -e TZ=America/New_York -v /home/docker/octoprint-klipper:/home/octoprint/.octoprint --device /dev/ttyUSB0:/dev/ttyUSB0 -p 5000:5000 seanauff/octoprint-klipper:[tag]
|
|
```
|
|
|
|
Stop the container, and modify your [Klipper] `printer.cfg` and [Octoprint] `config.yaml` in the config directory as needed.
|
|
|
|
Restart the container.
|
|
|
|
A sample docker-compose file is also provided.
|
|
|
|
If you have any questions, feel free to log an issue on this project, and I'll see if I can help.
|
|
|
|
## Reconnecting to MCU after board power cycle
|
|
|
|
Depending on your power situation, removing power from the printer main board will interrupt the serial connection. I had to give my container some more permissions in order to detect the coonection again without restarting the entire container. There is some discussion [here](https://github.com/moby/moby/issues/35359) and [here](https://www.losant.com/blog/how-to-access-serial-devices-in-docker).
|
|
|
|
## Updates
|
|
|
|
The easiest way to update is to pull the latest image and recreate the container. You could also build the image yourself to get the latest updates. I have had success in using the Octoprint built in updater to upgrade plugins, as well as install new ones. Any upgrades conducted in this manner will be lost upon recreation of the container.
|
|
|
|
## Build the image yourself
|
|
|
|
The DockerHub images may not be as up to date as the repo (`amd64` is autobuilt, but not `arm`), so you can ensure you have the latest by building yourself.
|
|
|
|
Clone the repository and build the image:
|
|
|
|
```shell
|
|
git clone https://github.com/seanauff/OctoPrint-Klipper.git
|
|
docker build -t seanauff/octoprint-klipper OctoPrint-Klipper
|
|
```
|
|
|
|
If you already have an image built and are trying to upgrade, you may need to force the build not to use cache:
|
|
```shell
|
|
docker build -t seanauff/octoprint-klipper --no-cache -pull OctoPrint-Klipper
|
|
```
|
|
|
|
[Octoprint]: https://github.com/foosel/OctoPrint
|
|
[Klipper]: https://github.com/KevinOConnor/klipper
|