IceWhaleTech
Sharing solution to continue use CasaOS with latest docker 29
Hi all, i saw this solution suggested by Docker and someone else from reddit, i tested it and confirm working, you dont need to downgrade the docker to 28, you can use 29.
TLDR
You can fix it without downgrading Docker or Portainer. You can add the variable DOCKER_MIN_API_VERSION=1.24 to the docker service config ( this fixes the issue for Traefik aswell if you are using this, since traefik uses the version 1.24 )
systemctl edit docker.service
Add this part above the line ### Lines below this comment will be discarded:
[Service]
Environment=DOCKER_MIN_API_VERSION=1.24
Save the file and exit systemctl restart docker
https://www.docker.com/blog/docker-engine-version-29/
hope this help. but still this is not long term solution and i hope IceWhaleTech team will get CasaOS updated soon.
This is really helpful, thank you. Much less intrusive than downgrading docker. Has anything actually been said by the devs yet?
i cannot seem to get this working :(
Can you provide more details about the steps you tried and your OS?
i cannot seem to get this working :(
Can you provide more details about the steps you tried and your OS?
Running Ubuntu Server. and i did sudo systemctl edit docker.service, went down to [Service] and added a new line beneath it with a # Environment=(therest of what was said) then saved and exited and sudo systemctl restart docker. and it didn’t work. i also tried it WITHOUT the # and it made no difference.
Check which directory you're updating the env file. Mine was under my user directory, not a unbuntu system directory.
On 11/19/2025 4:28 PM CST atsuen @.***> wrote:
atsuenn left a comment (IceWhaleTech/CasaOS#2407) https://github.com/IceWhaleTech/CasaOS/issues/2407#issuecomment-3554880911
i cannot seem to get this working :(
Can you provide more details about the steps you tried and your OS?
Running Ubuntu Server. and i did sudo systemctl edit docker.service, went down to [Service] and added a new line beneath it with a # Environment=(therest of what was said) then saved and exited and sudo systemctl restart docker. and it didn’t work. i also tried it WITHOUT the # and it made no difference.
— Reply to this email directly, view it on GitHub https://github.com/IceWhaleTech/CasaOS/issues/2407#issuecomment-3554880911, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2QNCPICQL7EXG2MZ5ED5UD35TVH5AVCNFSM6AAAAACMCSJW4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNJUHA4DAOJRGE. You are receiving this because you commented.Message ID: @.***>
Check which directory you're updating the env file. Mine was under my user directory, not a unbuntu system directory. …
What do you mean?
Very simple and worked for me also. This issue have been driving me mad for two days. Thanks a lot!!
Docker is installed by default in the /var/lib/docker directory.
On my CasaOs install it was in the /usr/ subdirectory. You can run this terminal cmd to find instances of docker: sudo dpkg -l | grep docker
Good luck.
On 11/20/2025 7:03 AM CST atsuen @.***> wrote:
atsuenn left a comment (IceWhaleTech/CasaOS#2407) https://github.com/IceWhaleTech/CasaOS/issues/2407#issuecomment-3557950589
Check which directory you're updating the env file. Mine was under my user directory, not a unbuntu system directory. …
What do you mean?
Message ID: @.***>
Solved Solution
🛠️ CasaOS App Store Fix: Docker API Version Incompatibility This solution addresses the common CasaOS error when trying to load the App Store, which results in the message:
"Failure to load apps. Please refresh later casaos"
The root cause, as seen in the system logs, is a version mismatch between the CasaOS App Management client and a modern Docker Engine (e.g., v23.0.0+):
Error response from daemon: client version 1.42 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version
Even if your Docker Engine is up-to-date (e.g., API v1.52), the CasaOS client component is stuck requesting the old v1.42 API.
✅ The Solution: Force the Correct Docker API Version We resolve this by forcing the casaos-app-management service to use the higher API version supported by your Docker Engine (e.g., v1.52) using the DOCKER_API_VERSION environment variable.
Step 1: Find the Exact Service File Location First, confirm the exact path of the service file. The output will show the path next to Loaded::
Bash
sudo systemctl status casaos-app-management The common path is usually: /usr/lib/systemd/system/casaos-app-management.service
Step 2: Edit the Service File Use your preferred text editor (e.g., nano or xed) to open the service file. Remember to use sudo:
Bash
sudo nano /usr/lib/systemd/system/casaos-app-management.service
Use the path found in Step 1 if different!
Step 3: Add the Environment Variable Locate the [Service] section and add the Environment="DOCKER_API_VERSION=X.XX" line before the ExecStart line.
Note: Replace 1.52 below with the API version your Docker Engine supports (you can check with docker version --format '{{.Server.APIVersion}}').
Corrected Service File Content:
Ini, TOML
[Unit] After=casaos-message-bus.service After=docker.service Description=CasaOS App Management Service
[Service] ExecStartPre=/usr/bin/casaos-app-management -v Environment="DOCKER_API_VERSION=1.52" # <-- ADD THIS LINE ExecStart=/usr/bin/casaos-app-management -c /etc/casaos/app-management.conf PIDFile=/var/run/casaos/app-management.pid Restart=always Type=notify
[Install] WantedBy=multi-user.target Step 4: Reload and Restart the Service Finally, reload the systemd configuration and restart the CasaOS component to apply the fix:
Bash
sudo systemctl daemon-reload sudo systemctl restart casaos-app-management The CasaOS App Store should now load correctly upon refreshing your browser.
Solved Solution
🛠️ CasaOS App Store Fix: Docker API Version Incompatibility This solution addresses the common CasaOS error when trying to load the App Store, which results in the message:
"Failure to load apps. Please refresh later casaos"
The root cause, as seen in the system logs, is a version mismatch between the CasaOS App Management client and a modern Docker Engine (e.g., v23.0.0+):
Error response from daemon: client version 1.42 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version
Even if your Docker Engine is up-to-date (e.g., API v1.52), the CasaOS client component is stuck requesting the old v1.42 API.
✅ The Solution: Force the Correct Docker API Version We resolve this by forcing the casaos-app-management service to use the higher API version supported by your Docker Engine (e.g., v1.52) using the DOCKER_API_VERSION environment variable.
Step 1: Find the Exact Service File Location First, confirm the exact path of the service file. The output will show the path next to Loaded::
Bash
sudo systemctl status casaos-app-management The common path is usually: /usr/lib/systemd/system/casaos-app-management.service
Step 2: Edit the Service File Use your preferred text editor (e.g., nano or xed) to open the service file. Remember to use sudo:
Bash
sudo nano /usr/lib/systemd/system/casaos-app-management.service
Use the path found in Step 1 if different!
Step 3: Add the Environment Variable Locate the [Service] section and add the Environment="DOCKER_API_VERSION=X.XX" line before the ExecStart line.
Note: Replace 1.52 below with the API version your Docker Engine supports (you can check with docker version --format '{{.Server.APIVersion}}').
Corrected Service File Content:
Ini, TOML
[Unit] After=casaos-message-bus.service After=docker.service Description=CasaOS App Management Service
[Service] ExecStartPre=/usr/bin/casaos-app-management -v Environment="DOCKER_API_VERSION=1.52" # <-- ADD THIS LINE ExecStart=/usr/bin/casaos-app-management -c /etc/casaos/app-management.conf PIDFile=/var/run/casaos/app-management.pid Restart=always Type=notify
[Install] WantedBy=multi-user.target Step 4: Reload and Restart the Service Finally, reload the systemd configuration and restart the CasaOS component to apply the fix:
Bash
sudo systemctl daemon-reload sudo systemctl restart casaos-app-management The CasaOS App Store should now load correctly upon refreshing your browser.
Thankyou, this actually helped massively!!
ngl, the fix in this OP is WAY more big brain than mine, go use that instead! I was honestly trying to figure out how to set up that variable, but gave up. Just remember to run "sudo systemctl daemon-reload && sudo systemctl restart docker.service" afterwards!
Hi all! Sorry for the long wait, with the help of Sabitech, the installation script has been fixed 🙂 , now you can just do a clean install or use the current installation script to fix the previous docker app not loading. The new script has the following features:
Install the latest available Docker engine instead of Docker 24.0.7
Apply a Docker API compatibility override for newer Docker versions
Allow CasaOS services and baked-in apps to work with modern Docker
Please rest assured that we will continue to improve user experience and working hard to ensure compatibility across multiple platforms.
