CoolStore can still be added to CasaOS through the App Store's Add Source function using the current ZIP URL published by the CoolStore repository. However, it is a third-party store, not an IceWhale-curated source, so review each app's image, volumes, ports, and maintainer before installing it.
The 2023 forum tutorial is now too old to use as the only instruction. The CoolStore repository currently publishes a maintained source URL, while the wider CasaOS/ZimaOS app-store ecosystem has moved toward newer store protocols and stronger validation.
Current CoolStore Source URL
The current project repository lists:
https://casaos-appstore.paodayag.dev/coolstore.zipThe CasaOS CoolStore repository should be treated as the source of truth rather than a shortened link from an old tutorial.
How to Add CoolStore in CasaOS
- Open the CasaOS dashboard.
- Open App Store.
- Choose Add Source.
- Paste the current CoolStore ZIP URL.
- Wait for the source to refresh.
- Confirm that CoolStore applications appear before installing anything.
If Add Source Says Success but No Apps Appear
Refresh the App Store page and check whether the source is still registered. CasaOS has had third-party-store compatibility issues when source formats or store roots changed, so a successful toast message does not always prove the store was parsed correctly.
Do Not Treat Third-Party Store Apps as Official CasaOS Apps
A community store can package excellent software, but the app manifest may be maintained by a different person from the upstream application developer. Before installation, inspect:
- Docker image source;
- version/tag strategy;
- host-path volume mappings;
- privileged mode or device access;
- published ports;
- update history.
Prefer Upstream Docker Documentation for Critical Apps
If you are installing a database, reverse proxy, password manager, or other important service, compare the CoolStore manifest against the upstream project's current Docker documentation. Third-party packaging can lag behind major upstream changes.
Understand the New App-Store Direction
IceWhale's current App Store developer documentation now defines a newer v2 store protocol with generated store.json, index.json, per-app Compose, metadata, and assets. Legacy ZIP stores can still exist for compatibility, but they are not the only app-store format anymore.
The current App Store developer docs explains the newer store architecture.
Remove a Store Source Without Deleting Your App Data
Removing a store source should be treated separately from uninstalling apps that were installed from it. An already running container does not automatically disappear just because the catalog source is removed.
Back up important app data before uninstalling a community-packaged application.
When Manual Docker Is Better
If a CoolStore app is outdated or requests risky permissions, install the upstream Compose definition manually instead. This makes image tags, volumes, networks, and secrets easier to audit.
The custom Docker guide provides the same transparent deployment approach.
Back Up the App Before Switching Store Packages
If you already installed an app from CoolStore and want to replace it with another store's version, do not assume both manifests use the same host paths, environment variables, or container names. Export or back up the app's persistent data first, then compare the two Compose definitions before uninstalling anything.
How to Judge Whether a Store Entry Is Healthy
Check whether the underlying Docker image still receives updates, whether the store manifest pins a sensible version, and whether recent users report successful installs. A store can remain reachable while one individual package has silently become stale.
For security-sensitive services, also verify that the manifest does not request privileged mode, host networking, raw devices, or broad filesystem mounts without a clear reason.
FAQ
Is CoolStore an official CasaOS store?
No. It is a third-party community store.
What URL should I use?
Use the current ZIP URL published in the CoolStore GitHub repository rather than an old shortened link.
Will adding CoolStore modify CasaOS itself?
It adds another app catalog source. Individual apps can still request ports, volumes, privileges, or host access, so review each manifest separately.
What if an app in CoolStore is outdated?
Use the upstream Docker/Compose documentation or another maintained store package rather than forcing an old manifest.
