Here is the SOLUTION for Ubuntu: (Failed to load apps, please refresh later.)

[meshworkgit]

After the latest Docker update, applications are not appearing on the Casaos homepage. I have tried many methods but no solution. Please help.

[meshworkgit]

Here is the solution for Ubuntu

sudo apt update sudo systemctl stop docker sudo systemctl stop docker.socket sudo apt remove -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin sudo apt install -y docker-ce=5:28.5.2-1~ubuntu.24.04~noble docker-ce-cli=5:28.5.2-1~ubuntu.24.04~noble containerd.io sudo systemctl start docker sudo apt-mark hold docker-ce docker-ce-cli containerd.io sudo reboot

[LxR-neonhydra]

will this work on debian

[meshworkgit]

I use Ubuntu and this worked for me. For Debian, you can try the following.

for bookworm

sudo apt update sudo systemctl stop docker sudo systemctl stop docker.socket sudo apt remove -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin sudo apt install -y docker-ce=5:28.3.2~debian.12~bookworm docker-ce-cli=5:28.3.2~debian.12~bookworm containerd.io sudo systemctl start docker sudo apt-mark hold docker-ce docker-ce-cli containerd.io sudo reboot

for trixie

sudo apt update sudo systemctl stop docker sudo systemctl stop docker.socket sudo apt remove -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin sudo apt install -y docker-ce=5:28.5.2-1~debian.13~trixie docker-ce-cli=5:28.5.2-1~debian.13~trixie --allow-downgrades sudo systemctl start docker sudo apt-mark hold docker-ce docker-ce-cli containerd.io sudo reboot

[LxR-neonhydra]

how do i know what kind i have i did this so long ago i forgot

[meshworkgit]

[LxR-neonhydra]

how do i know what kind of debian i have

[donaar]

Try uname at command prompt

[LxR-neonhydra]

it just says Linux

[donaar]

try command uname

On Wed, Nov 12, 2025 at 8:33 AM LxR-neonhydra @.***> wrote:

LxR-neonhydra left a comment (IceWhaleTech/CasaOS#2399) https://github.com/IceWhaleTech/CasaOS/issues/2399#issuecomment-3521962962

how do i know what kind of debian i have

— Reply to this email directly, view it on GitHub https://github.com/IceWhaleTech/CasaOS/issues/2399#issuecomment-3521962962, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHSDZGD66O7AW76ROAQGZH334MZJ5AVCNFSM6AAAAACL4DMH6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMRRHE3DEOJWGI . You are receiving this because you are subscribed to this thread.Message ID: @.***>

-- https://about.me/Donaar?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=edit_panel&utm_content=thumb Robert Rogers about.me/Donaar https://about.me/Donaar?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=edit_panel&utm_content=thumb

Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety. Memoirs of the life and writings of Benjamin Franklin http://books.google.com/books?id=W2MFAAAAQAAJ&pg=PA270&lpg=PA270t#PPA270,M1 (1818)

Grid Square [EN72eh]

[LxR-neonhydra]

i did it just says Linux

[donaar]

try one of these

lsb_release -a

cat /etc/*-release

cat /proc/version

lsb_release -a

[LxR-neonhydra]

thank you the first one worked i have bookworm

[LxR-neonhydra]

this is what happed Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://security.debian.org/debian-security bookworm-security InRelease
Get:3 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
Hit:4 https://playit-cloud.github.io/ppa/data ./ InRelease
Hit:5 https://download.docker.com/linux/debian bookworm InRelease
Hit:6 https://cdn-repo.c7rs.com debian/ InRelease
Fetched 55.4 kB in 1s (46.2 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. Warning: Stopping docker.service, but it can still be activated by: docker.socket Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libltdl7 linux-image-6.1.0-35-amd64 linux-image-6.1.0-37-amd64 pigz Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: containerd.io docker-buildx-plugin docker-ce docker-ce-cli docker-compose-plugin 0 upgraded, 0 newly installed, 5 to remove and 0 not upgraded. After this operation, 383 MB disk space will be freed. (Reading database ... 50952 files and directories currently installed.) Removing docker-ce (5:29.0.0-1~debian.12~bookworm) ... Removing containerd.io (2.1.5-1~debian.12~bookworm) ... Removing docker-buildx-plugin (0.29.1-1~debian.12~bookworm) ... Removing docker-ce-cli (5:29.0.0-1~debian.12~bookworm) ... Removing docker-compose-plugin (2.40.3-1~debian.12~bookworm) ... Processing triggers for man-db (2.11.2-2) ... Reading package lists... Done Building dependency tree... Done Reading state information... Done Package docker-ce is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: docker-ce-cli

Package docker-ce-cli is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: docker-ce docker-buildx-plugin

E: Version '5:28.3.2debian.12bookworm' for 'docker-ce' was not found E: Version '5:28.3.2debian.12bookworm' for 'docker-ce-cli' was not found Failed to start docker.service: Unit docker.service not found. docker-ce set on hold. docker-ce-cli set on hold. containerd.io set on hold.

[AndreFelipeCL]

I use Ubuntu and this worked for me. For Debian, you can try the following.

for bookworm

sudo apt update sudo systemctl stop docker sudo systemctl stop docker.socket sudo apt remove -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin sudo apt install -y docker-ce=5:28.3.2~debian.12~bookworm docker-ce-cli=5:28.3.2~debian.12~bookworm containerd.io sudo systemctl start docker sudo apt-mark hold docker-ce docker-ce-cli containerd.io sudo reboot

for trixie

sudo apt update sudo systemctl stop docker sudo systemctl stop docker.socket sudo apt remove -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin sudo apt install -y docker-ce=5:28.5.2-1~debian.13~trixie docker-ce-cli=5:28.5.2-1~debian.13~trixie --allow-downgrades sudo systemctl start docker sudo apt-mark hold docker-ce docker-ce-cli containerd.io sudo reboot

That's worked for me on a Raspberry Pi: sudo apt install -y docker-ce=5:28.5.2-1~debian.13~trixie docker-ce-cli=5:28.5.2-1~debian.13~trixie --allow-downgrades

[khalilsantarem]

Here is the solution for Ubuntu

sudo apt update sudo systemctl stop docker sudo systemctl stop docker.socket sudo apt remove -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin sudo apt install -y docker-ce=5:28.5.2-1~ubuntu.24.04~noble docker-ce-cli=5:28.5.2-1~ubuntu.24.04~noble containerd.io sudo systemctl start docker sudo apt-mark hold docker-ce docker-ce-cli containerd.io sudo reboot

Did something like this on Ubuntu Server 24.04.03 LTS and it worked.

[onefish2]

A workaround without the need to downgrade docker version or portainer, which is to manually lower the minimum API version of docker:

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 and exit systemctl restart docker

[fjduarte95]

A workaround without the need to downgrade docker version or portainer, which is to manually lower the minimum API version of docker:

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 and exit systemctl restart docker

Thank you so much, my Debian Bookworm based system is showing apps once again.

[andyteg]

I use Ubuntu and this worked for me. For Debian, you can try the following.

for bookworm

sudo apt update sudo systemctl stop docker sudo systemctl stop docker.socket sudo apt remove -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin sudo apt install -y docker-ce=5:28.3.2~debian.12~bookworm docker-ce-cli=5:28.3.2~debian.12~bookworm containerd.io sudo systemctl start docker sudo apt-mark hold docker-ce docker-ce-cli containerd.io sudo reboot

for trixie

sudo apt update sudo systemctl stop docker sudo systemctl stop docker.socket sudo apt remove -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin sudo apt install -y docker-ce=5:28.5.2-1~debian.13~trixie docker-ce-cli=5:28.5.2-1~debian.13~trixie --allow-downgrades sudo systemctl start docker sudo apt-mark hold docker-ce docker-ce-cli containerd.io sudo reboot

Hi - I tried this for Bookworm and I am getting loads of errors now. I then attempted to edit the file to set the version but I get this error. systemctl edit docker.service No files found for docker.service. Can anyone suggest what to do? Same issue as before CasaOS but greyed out blank app icons. I think my PiHole has stopped working as I have screwed up the Docker by trying to follow the instructions above. Any help greatly appreciated - rather fix than have to do a complete wipe and re-install.

[DebankurMandal]

A workaround without the need to downgrade docker version or portainer, which is to manually lower the minimum API version of docker:

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 and exit systemctl restart docker

Thanks this worked for me

[diegosousag-ux]

I fixed it like this on Debian 12

1️⃣ (Re)configure the official Docker repository

You can run it again, no problem if you already did it:

sudo apt update sudo apt install -y ca-certificates curl gnupg

sudo install -m 0755 -d /etc/apt/keyrings curl -fsSL https://download.docker.com/linux/debian/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg sudo chmod a+r /etc/apt/keyrings/docker.gpg

echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg]
https://download.docker.com/linux/debian
$(. /etc/os-release && echo "$VERSION_CODENAME") stable" |
sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

sudo apt update

2️⃣ Reinstall Docker (without deleting containers) sudo apt install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin sudo systemctl enable --now docker

Now the docker.service exists again.

3️⃣ Create the override with DOCKER_MIN_API_VERSION=1.24

To avoid depending on an editor, create the file directly:

sudo mkdir -p /etc/systemd/system/docker.service.d

printf "[Service]\nEnvironment=DOCKER_MIN_API_VERSION=1.24\n" |
sudo tee /etc/systemd/system/docker.service.d/override.conf

Apply the changes:

sudo systemctl daemon-reload sudo systemctl restart docker

4️⃣ Restart CasaOS services sudo systemctl restart casaos-gateway casaos-app-management casaos-user-service

Then, in the browser, open CasaOS and press Ctrl + F5 (force refresh).

[Dev01-D]

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.