CB1 Image Ships With Unnecessary, Locked Klipper/Moonraker Configs That Prevent a Clean Install

[twanskys]

Summary
The current CB1 OS image includes preloaded Klipper, Moonraker, and system configuration files that are unnecessary, undocumented, and cannot be removed or modified. These files interfere with clean Klipper installations, override user configurations, and prevent users from building their own modular setup. The image does not behave like a standard Linux environment and blocks normal Klipper workflows.

Environment
Board: BTT CB1

Image: Latest release from GitHub

Use case: Clean Klipper + Moonraker installation

Multiple SD cards tested

No custom modifications

Major Problems

1. Unneeded Klipper/Moonraker configs are preinstalled
   The image ships with:

Predefined printer.cfg fragments
Preloaded Moonraker configs
Old or mismatched Klipper directories
Precreated service files
These configs:
Do not match the user’s hardware
Are not documented
Cannot be safely removed
Cause conflicts with fresh installs
Break modular configuration setups
A CB1 image should not include any printer‑specific or user‑specific configs.

2. These configs are locked read‑only
   Even with root access, the preloaded configs cannot be edited or deleted.
   Attempts to modify or remove them result in: Read-only file system

This prevents:

Replacing incorrect configs
Removing vendor presets
Installing a clean Klipper environment
Using KIAUH
Creating a modular config structure
This forces users into a locked, vendor‑defined configuration that is unusable for most printers.

3. Clean Klipper workflows are blocked
   Because the preloaded configs cannot be removed or overwritten, users cannot:

Install their own Klipper version
Install their own Moonraker version
Create their own service files
Use their own printer.cfg
Build a clean, modular configuration
This breaks every standard Klipper installation method.

4. Image behavior does not match documentation
   Documentation suggests:

Users can install Klipper normally
Users can configure their own printer
The system behaves like a standard Linux environment
But the actual image:
Locks critical directories
Forces vendor configs
Prevents clean installs
Contains mismatched or outdated components
This creates confusion and makes troubleshooting impossible.

Expected Behavior

No preinstalled Klipper or Moonraker configs
No vendor printer.cfg
Writable filesystem
Ability to install Klipper cleanly
Ability to create a modular config structure
Behavior consistent with documentation

Actual Behavior

Unnecessary configs are preloaded
These configs are locked read‑only
Clean installs are blocked
User configs cannot be applied
System behaves inconsistently with documentation

Request

Please provide a clean CB1 image with:

No preinstalled Klipper/Moonraker configs
No vendor printer.cfg
No locked configuration directories
A writable filesystem
A standard Linux environment suitable for clean Klipper installs
This would restore the CB1 to a usable state for the majority of Klipper users.

[Skedar]

Are you blind? you have TWO imgs....one WITH klipper, and other WITHOUT any config. clean install.

[twanskys]

@Skedar

It’s possible that a truly clean CB1 image exists or could be made to work under ideal conditions. However, that does not change the core issue being reported here.

The Klipper/Mainsail‑preinstalled CB1 image is fundamentally broken in ways that cannot be corrected from user space.

Specifically, the Klipper image:

Executes motion and heater behavior before user start G‑code runs

Restores G‑code state automatically (e.g. relative positioning / offsets)

Overrides explicit heater ordering defined in slicer start G‑code

Causes startup crashes even when user initialization (G90, M82, G92) is present

Loads locked, undocumented system‑level behavior that cannot be disabled or audited

These behaviors violate a core Klipper expectation: that user start G‑code is authoritative and runs first.

Whether or not a separate “clean” image can be made to work does not resolve the fact that the officially provided Klipper/Mainsail image ships in a state that is hostile to normal Klipper operation and leads to unpredictable, unsafe behavior.

This issue is therefore not about image selection or user error — it is about the design and contents of the Klipper/Mainsail CB1 image itself.