Safe way to run apt upgrade on ZimaBlade with CasaOS v0.4.15?

Insight & Feedback
1

Hi everyone,

I’m running a ZimaBlade (build 20240509) with CasaOS v0.4.15 on Debian 11 Bullseye. The
system has been running great, but I’m aware that there are around 150 pending security
updates (kernel, openssl, libc6, openssh, samba, curl, systemd and more).

Before touching anything I’d like to understand the safe procedure, since I couldn’t
find official IceWhale documentation covering this scenario.

My setup:

  • ZimaBlade, Debian 11 Bullseye
  • CasaOS v0.4.15 (already at latest)
  • Docker CE 24.0.5
  • Two 3.6TB HDDs mounted via casaos-local-storage (not in fstab)
  • Several Docker apps running (Jellyfin, Immich, Samba shares)

My specific questions:

  1. Is it safe to run apt update && apt upgrade on a ZimaBlade without breaking CasaOS or
    the disk mounts?
  2. I’m aware of the Docker v29 API breaking change (issue #2390 on GitHub). Should I
    hold Docker back with apt-mark hold docker-ce before upgrading?
  3. Does a kernel upgrade + reboot cause any issues with how CasaOS remounts the data
    disks?
  4. Is there any official or community-recommended procedure for keeping the underlying
    Debian system patched while preserving CasaOS stability?

Any experience or advice is much appreciated. Thanks!

2

Yeah you’re right to pause before updating, this is one of those cases where Debian flexibility vs CasaOS stability can clash a bit.

Answers to your 4 points:

1. Is apt upgrade safe?
Generally yes for normal packages, but the risk is when core components change. CasaOS expects a fairly fixed environment, so big upgrades can cause weird behaviour rather than outright failure.

2. Should Docker be held back?
Yes, this is the main one. Newer Docker versions have changed APIs before, and CasaOS v0.4.15 isn’t guaranteed to handle that cleanly. Most breakages people hit are Docker-related.

3. Kernel upgrade + reboot issues?
This is the biggest risk area. Your data isn’t lost, but mounts can come back differently or not at all since CasaOS manages them itself. That’s when apps suddenly see empty folders.

4. Recommended approach?
There’s no official IceWhale guide for this scenario, so it’s mostly community best practice:

  • keep updates conservative
  • avoid major jumps (Docker/kernel if possible)
  • prioritise stability over chasing every update

Small updates are usually fine. The problems come from Docker changes and kernel/mount behaviour after reboot, that’s where most CasaOS setups get tripped up.