<![CDATA[Upgrade docker from 2.33 to 2.36 failure]]>Trying to upgrade my RPI5 v2.33 to V2.36 and get the following error while doing the “docker compose Pull”:

ron@rpi5:~/magicmirror/run $ docker compose pull
[+] Pulling 16/18
 ✔ init Skipped - Image is already being pulled by magicmirror             0.0s 
 ⠏ magicmirror [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿] 386.2MB / 390.3MB Pulling               23.9s 
   ⠏ 76b7b92b680d Extracting         181kB/181kB                          22.9s 
   ✔ 0479d40f39a3 Download complete                                        2.4s 
   ✔ 2d0f308d8afe Download complete                                        0.4s 
   ✔ 06d4fbe68d7c Download complete                                        5.6s 
   ✔ 245238857a72 Download complete                                        5.7s 
   ✔ 50618a6ac35d Download complete                                        7.2s 
   ✔ d0d0bce19890 Download complete                                       10.8s 
   ✔ d0326d1e8758 Download complete                                       10.8s 
   ✔ 22ef58b941aa Download complete                                       10.8s 
   ✔ 3cbe9d4d3f1b Download complete                                       11.1s 
   ✔ 8ce16659ba64 Download complete                                       11.1s 
   ✔ bd6473435aa5 Download complete                                       11.1s 
   ✔ 153a60e41e92 Download complete                                       19.2s 
   ✔ 4ac394d170cb Download complete                                       11.3s 
   ✔ 7c3a6344e52e Download complete                                       22.9s 
   ✔ 4f4fb700ef54 Download complete                                       16.7s 
failed to register layer: Error processing tar file(exit status 1): archive/tar: invalid tar header

Tried it twice with the same error
system info:
RPI 5, 4GB ram, 128GB SSD, RPI OS Bookworm

]]>https://forum.magicmirror.builders/topic/20244/upgrade-docker-from-2.33-to-2.36-failureRSS for NodeSun, 17 May 2026 05:42:44 GMTSat, 16 May 2026 12:36:20 GMT60<![CDATA[Reply to Upgrade docker from 2.33 to 2.36 failure on Sun, 17 May 2026 01:11:46 GMT]]>@RonR wasn’t me. Karsten does the docker container, he replied with the link

]]>https://forum.magicmirror.builders/post/131158https://forum.magicmirror.builders/post/131158Sun, 17 May 2026 01:11:46 GMT<![CDATA[Reply to Upgrade docker from 2.33 to 2.36 failure on Sun, 17 May 2026 00:42:48 GMT]]>Sam thanks for the info on out of date docker.

I updated docker from 20.10 to 29.5 and then was able to install MM cleanly and my delay problem has disappeared. All that fighting because I was unsure about updating docker with out wiping it out first.
It is nice to not have to wait for MM to come up any more.

THANK YOU VERY MUCH FOR YOUR HELP.
Ron

]]>https://forum.magicmirror.builders/post/131157https://forum.magicmirror.builders/post/131157Sun, 17 May 2026 00:42:48 GMT<![CDATA[Reply to Upgrade docker from 2.33 to 2.36 failure on Sat, 16 May 2026 16:36:27 GMT]]>@RonR

see https://gitlab.com/khassel/magicmirror/-/work_items/103

]]>https://forum.magicmirror.builders/post/131156https://forum.magicmirror.builders/post/131156Sat, 16 May 2026 16:36:27 GMT<![CDATA[Reply to Upgrade docker from 2.33 to 2.36 failure on Sat, 16 May 2026 12:41:59 GMT]]>@sdetweil Thank you, mind slip again. I ment to put that in.

]]>https://forum.magicmirror.builders/post/131153https://forum.magicmirror.builders/post/131153Sat, 16 May 2026 12:41:59 GMT<![CDATA[Reply to Upgrade docker from 2.33 to 2.36 failure on Sun, 17 May 2026 01:18:28 GMT]]>@RonR I edited the title

Correct answer below

]]>https://forum.magicmirror.builders/post/131152https://forum.magicmirror.builders/post/131152Sun, 17 May 2026 01:18:28 GMT