Thanks for the resource links.
I have had the same issues. Running on a synology in DSM6 (DS218+).
Looks like a bit of careful fiddling required to ensure log files move across for portainer to use.
I am quite wary as all my setup is running in docker on this box: ubiquity controller, adguard, homeassistant etc.
I was able to get the new image running in old docker. I first pulled the image to a newer docker, then saved it, moved the saved file to my older docker, then load and recreated my container.
# on newer docker
docker pull homeassistant/home-assistant:stable
docker save homeassistant/home-assistant:stable -o homeassistant-2026.3.1.tar
# move file
# on NAS with older docker
docker load -i homeassistant-2026.3.1.tar
I have been running HA under udocker on Android with Termux. I have installed and updated a couple of time in 2026.
With 2026.3 I am now getting an error message with the pull:
no image found in manifest for platform (android/arm64)
no manifest for given image and platform
Error: no files downloaded
Did something change in the platforms that HA supports?
To upgrade docker on my Debian system I followed:-
https://linuxconfig.org/how-to-update-docker-on-debian-ubuntu-linux
sudo apt update
sudo apt install docker.io
docker --version
You can check if docker is running by running sudo systemctl status docker
(you may need to restart the service)
It’s usually good idea to use the official docker repo.
Thank you for the fix. My system is running on a Raspberry PI 5 using Portainer. With your fix my system is now running HA version 2026.3.2!!
I spent a bunch of time working with Termux maintainers of udocker. The problems for android/arm64 have been fixed and should make their way out shortly.
There was a related problem for Android 7 devices that has also been fixed.
There may be one remaining problem with Android 7, but a fix is being reviewed.
For some reason I can’t update docker even following the advice by @robfish above.
I keep staying on Docker version 20.10.5+dfsg1, build 55c4c88
Any suggestions?
I’m no expert but could you have used a different method to install docker originally?
(so maybe it requires a different method of upgrading)
Perhaps, if all else fails,after backing up your docker file and HA,
you could uninstall your current docker app then reinstall it and restore your docker compose file and HA
Yeah, I figured out that I installed Docker via Docker.io which was version limited to the version I posed above.
I did need to completely uninstall docker.io and re-install docker-ce from the official docker repo.
Help! I’m running hass on a Synology DS412+ which is stuck on a very old version of docker…
It’s also not upgradable to DSM 7 which has the updated docker.
I tried the update pvh0 referenced but it also seems incompatible with this model. It will load and allow image download but it is listed as null size and won’t run at all…
Also tried Windows version of docker and exporting the image (in Linux format) but that did not work either…
Any other suggestions would be very much appreciated… I’ve been on hass since the beginning and can’t bear the thought of being stuck on 2026.2.3 forever!
Cheers!
Same ‘synology’ issue here. A DS1512+ so stuck on DSM6, and older docker.
Several containers running in docker, so would be quite a challenge if a docker from another repository doesn’t work. or overwrites all kinds of things it shouldn’t.
Hopefully someone will write a useable step-by-step article and test it a bit to see if this is reasonably safe to do.
For those who have no way to update docker:
From "invalid tar header" when pulling HA 2026.03.00 Docker image · Issue #165012 · home-assistant/core · GitHub
Just a quick workaround for people stuck with old docker versions (like me, on ubuntu 16.04 / docker 18.09.7 / containerd 1.2.9):
Go to another machine with a current version of docker
Docker pull on that machine and docker save -o the image
Transfer file to HA server, docker load -i the image
Redeploy the container
But before that workaround, try installing Docker from the Docker repository:
and make sure you do install the newer version with
sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
It works fine with a Raspberry Pi 4 on Bookworm by the way.
Just make sure you use docker compose instead of docker-compose.
Of course, updating Docker is still a workaround until we have to update the OS.
Since finding out that Raspberry Pi OS doesn’t have an upgrade path - you have to reflash a newer image and reconfigure everything from scratch - I’ve been thinking about switching to NixOS.
The initial config still has to be done (there are guides with configs available), but once it is, updating the whole system is just a command away.