Persistent Mod Mismatch on Pi 5 (box64 + factorio-tools Docker)
Posted: Wed May 13, 2026 9:06 am
Hi everyone,
I’m running into a persistent Mod Mismatch error on my headless server and could really use some advice. I'm trying to host a pure Vanilla server, but I keep getting blocked when trying to connect.
My Setup:
Hardware: Raspberry Pi 5
Software: Docker using the factorio-tools/factorio-docker image.
Emulation: Running via box64 to handle the x86 binary on ARM.
Goal: Play 100% Vanilla (no mods, just the base game).
Client: Windows laptop, fresh Vanilla state.
What I've tried to fix the Mismatch:
To ensure the server is completely vanilla, I accessed my Docker mods volume and did the following:
Deleted all existing .zip mod files in the directory.
Created a clean mod-list.json with only the "base" game enabled.
Deleted the mod-settings.dat file so the server would auto-generate a fresh, unmodded one on boot.
Restarted the Docker container.
The Issue:
Despite wiping the directory and forcing a vanilla state, the Mod Mismatch error persists when I try to connect with my vanilla client.
Is there a known issue with the factorio-tools image caching old mod data elsewhere? Could it be a file permission issue where the container user (UID 845) isn't reading the new mod-list.json and defaults to an old state? Or does running it through box64 introduce a quirk with how mods are synced?
Any insights or troubleshooting steps would be massively appreciated!
I’m running into a persistent Mod Mismatch error on my headless server and could really use some advice. I'm trying to host a pure Vanilla server, but I keep getting blocked when trying to connect.
My Setup:
Hardware: Raspberry Pi 5
Software: Docker using the factorio-tools/factorio-docker image.
Emulation: Running via box64 to handle the x86 binary on ARM.
Goal: Play 100% Vanilla (no mods, just the base game).
Client: Windows laptop, fresh Vanilla state.
What I've tried to fix the Mismatch:
To ensure the server is completely vanilla, I accessed my Docker mods volume and did the following:
Deleted all existing .zip mod files in the directory.
Created a clean mod-list.json with only the "base" game enabled.
Deleted the mod-settings.dat file so the server would auto-generate a fresh, unmodded one on boot.
Restarted the Docker container.
The Issue:
Despite wiping the directory and forcing a vanilla state, the Mod Mismatch error persists when I try to connect with my vanilla client.
Is there a known issue with the factorio-tools image caching old mod data elsewhere? Could it be a file permission issue where the container user (UID 845) isn't reading the new mod-list.json and defaults to an old state? Or does running it through box64 introduce a quirk with how mods are synced?
Any insights or troubleshooting steps would be massively appreciated!