If a third-party Paperless-ngx app fails because its Compose file references a bad Tika image, fix the app definition or use a maintained package rather than repeatedly reinstalling the same broken Compose. In the original thread, the Coolstore package pointed at a Tika image the user believed was wrong, while a BigBear package eventually installed successfully after several attempts.
The thread never established why the earlier BigBear attempts failed, so it would be inaccurate to say that changing only the IP section is a universal fix. The durable approach is to compare the third-party Compose against current Paperless-ngx upstream requirements.
Tika Is an Optional Paperless Service
The current Paperless-ngx configuration reference explains that Tika and Gotenberg are optional services used for Office documents and email parsing. Paperless must be configured with reachable endpoints when that integration is enabled.
That means a faulty Tika service image can break an installation that enables the integration even if the core Paperless container definition is otherwise valid.
Treat Coolstore and BigBear as Third-Party Packages
A community reply correctly pointed out that Coolstore is a third-party app source. A broken image reference in that package should be reported to its maintainer instead of being interpreted as a ZimaOS core defect.
If one store package is stale, compare it with upstream Paperless Docker examples or another maintained package. Preserve your existing data paths before changing stacks.
Edit or Re-Import the Compose Carefully
Current ZimaOS can import custom Docker Compose definitions. The custom Compose troubleshooting guide is the safer route when an app-store definition contains a bad image or unsupported field.
ZimaOS 1.7.1 also lists improved YAML saving compatibility in the current release notes. That improvement does not repair a third-party repository's incorrect image reference automatically.
Before You Reinstall Paperless Again
- Back up the Paperless data, media and database locations.
- Confirm every image reference exists and is maintained.
- Keep Paperless, its database, Redis, Tika and Gotenberg on the intended Compose networks.
- Change only one failure source at a time so the successful fix is identifiable.
If an installation suddenly succeeds after several retries, as it did in the thread, do not invent a cause. Keep the result labeled as user-verified success with an unresolved original failure.
