CasaOS icon indicating copy to clipboard operation
CasaOS copied to clipboard

[Feedback]app doesnt load

Open froz3n73 opened this issue 1 month ago • 5 comments

froz3n73 avatar Nov 11 '25 16:11 froz3n73

+1

x3llaz avatar Nov 11 '25 17:11 x3llaz

This is related to a recent Docker update. CasaOS doesn't communicate using the new API version. They'll need to release an update to use a minimum Docker API version 1.44. In the meantime, you could downgrade your docker to the latest version that respects API 1.43.

perdomon avatar Nov 11 '25 17:11 perdomon

This is related to a recent Docker update. CasaOS doesn't communicate using the new API version. They'll need to release an update to use a minimum Docker API version 1.44. In the meantime, you could downgrade your docker to the latest version that respects API 1.43.

sigh

TL;DR: I fault Docker for this one. I think they did an extremely poor job (and continue to do so) in making this breaking change clear.

Initially I was not sure I believed this to be true.

A given version of the Docker Engine SDK supports a specific version of the Docker Engine API, as well as all earlier versions. If breaking changes occur, they are documented prominently. -- From https://docs.docker.com/reference/api/engine/

This is pretty standard REST fare. So the notion that CasaOS "doesn't communicate using the new API version" should not have had bearing... under normal circumstances.

The recent Docker update, at least on Ubuntu, updated the Docker Engine to 29.0.0, which has API version 1.52. So if the above docs were accurate, that Docker Engine supports any calls made to it for that version or earlier. And for sure the version of the API that CasaOS is referencing will be earlier.

And looking at the Docker API version history, I saw no prominently documented breaking changes.

HOWEVER, what I DID see was that v1.52 was not listed. That indicated it was very new. And digging further, found various indications that yeah, this Docker update has broken a lot of things; e.g.,

https://forums.docker.com/t/docker-29-increased-minimum-api-version-breaks-traefik-reverse-proxy/150384

Traefik is updated regularly. And it's rather heavily used in containerized situations. I'm still looking up what other apps this update has broken.

So if anything, it sounds like Docker failed to properly alert folks ahead of time, and has broken backward compatibility when it should not have. This is likely going to piss off quite a few folks.

I would also like to know how you came to the information regarding this latest Docker update suddenly has a minimum API version requirement of v1.44+? I have yet to find this anywhere official.

fseesink avatar Nov 11 '25 23:11 fseesink

Son of a...

Ok, I found it: https://docs.docker.com/engine/release-notes/29/

So they haven't even yet put the official 29.0 version on the page, yet they pushed out the update.

Yeah, this one is going to annoy folks. I don't see Docker looking good in this.

fseesink avatar Nov 11 '25 23:11 fseesink

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.

Dev01-D avatar Dec 10 '25 20:12 Dev01-D