What This CasaOS WordPress Thread Shows
The original post linked to a BigBearCasaOS WordPress installation tutorial. The most important follow-up was about CPU architecture: a Raspberry Pi 4 user initially saw an ARM64 incompatibility message, and the app maintainer later said ARM64 support had been added. Another user still reported a no matching manifest for linux/arm/v8 error, showing why the container image architecture must be checked rather than assumed.
For current Zima hardware context, WordPress can run as a containerized web stack on platforms such as ZimaBoard 2 or ZimaBlade when the selected image supports the host architecture.
Check Architecture Before Installing
On any CasaOS host, identify whether the machine is amd64, arm64, or another architecture. A container can only start if every required image has a compatible manifest. Docker's official multi-platform guidance explains how image manifests and platform selection work in Docker multi-platform documentation.
Use an Image with Current WordPress Support
The official WordPress container image documents supported tags and common database pairings. Check the current image rather than relying on a historical app-store template: official WordPress Docker image.
A typical WordPress deployment also needs persistent storage for WordPress content and a database such as MariaDB or MySQL. Back up both the content volume and database before upgrading or replacing the app template.
CasaOS App Store vs Manual Compose
An app-store package is convenient because it predefines ports, volumes and environment variables. A manual Docker Compose deployment gives more control over image tags, database versions, storage locations and architecture selection. If a community package is stale or does not expose an ARM64-compatible tag, a manual compose stack using supported upstream images may be the cleaner path.
What to Validate After Installation
- Confirm the WordPress and database containers are both healthy.
- Open the site locally before exposing it remotely.
- Verify the WordPress content directory and database are on persistent storage.
- Set strong administrator credentials and keep plugins/themes updated.
- Create a backup before changing image tags or database versions.
FAQ
Why do I see no matching manifest for linux/arm/v8?
The selected image tag does not provide a compatible ARM64 manifest, or one dependency in the stack is still architecture-limited.
Does CasaOS itself make an x86-only image work on ARM?
No. The app platform cannot create a missing upstream image architecture.
Should I copy the 2023 BigBear template exactly?
Not without checking current image tags, environment variables and architecture support. Treat the original thread as historical installation context, then validate against current upstream images.
