You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|Cmd|`-I run/klipper.tty -a run/klipper.sock cfg/printer.cfg`|
91
+
|Cmd|`-I printer_data/run/klipper.tty -a printer_data/run/klipper.sock printer_data/config/printer.cfg`|
92
92
93
93
## Ports
94
94
none
95
95
96
96
## Volumes
97
97
|Volume|Description|
98
98
|---|---|
99
-
|`/opt/run`| Default Location for runtime Files generated by Klipper. <br>Namely `klipper.tty`, the emulated Serial device <br>and `klipper.sock`, the unix socket that is used for communation with moonraker |
100
-
|`/opt/cfg`|Config directory to host `printer.cfg`|
101
-
|`/opt/gcode`|Stores GCODE Files to be used by Klipper|
99
+
|`/opt/printer_data`| Default Location for printer data as proposed by Moonraker |
Moonraker requires Klipper to operate. See the Images' [README.md](../klipper/README.md) on how to run the Klipper Image.
10
-
Both Containers need to share their `run` Volume in order to be able to communicate via klippers unix socket. Configure Moonraker to use `/opt/run/klipper.sock` as klippys uds address.
10
+
Both Containers need to share their `run` Volume in order to be able to communicate via klippers unix socket. Configure Moonraker to use `/opt/printer_data/run/klipper.sock` as klippys uds address.
11
11
12
-
Create `moonraker.cfg` and `printer.cf` as well as the directories `run` and `gcode`, then run the containers.
12
+
Create `moonraker.conf` and `printer.cfg` as well as the directories `run` and `gcode`, then run the containers.
|`/opt/run`| Default Location for runtime Files generated by Klipper. Used to access `klipper.sock`, the unix socket that is used for communation with klipper |
70
-
|`/opt/cfg`|Config directory to host `moonraker.cfg`|
71
-
|`/opt/gcode`|Stores uploaded GCODE Files|
69
+
|`/opt/printer_data`| Default Location for printer data by Moonraker |
0 commit comments