Docker compose pull fails with `failed to extract layer (application/vnd.oci.image.layer.v1.tar+zstd`

Troubleshooting
1

Creating a bug report/issue

I have searched the existing open and closed issues

DietPi version | cat /boot/dietpi/.version

G_DIETPI_VERSION_CORE=10
G_DIETPI_VERSION_SUB=4
G_DIETPI_VERSION_RC=2
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’

Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
trixie 0

Kernel version | uname --all
Linux PetitPois 6.18.29+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.18.29-1+rpt1 (2026-05-12) aarch64 GNU/Linux

Architecture | dpkg --print-architecture
arm64

SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
RPi 5 Model B (aarch64)

Power supply used | (EG: 5V 1A RAVpower)
official Pi power supply for Pi-5

SD card used | (EG: SanDisk ultra)
m.2 NVMe SSD

Additional Information (if applicable)

Software title | (EG: Nextcloud)
Docker / homeassistant

Was the software title installed freshly or updated/migrated?
Docker was updated recently (with app update, I think)

Can this issue be replicated on a fresh installation of DietPi?
No, It worked fine with my other DietPi install

Bug report ID | echo $G_HW_UUID
c994216d-f169-4b5e-989e-b2c1b4a74761

Steps to reproduce

  1. run docker compose pull

Expected behaviour

  • expect pull to complete without errors

Actual behaviour

root@PetitPois:/mnt/dietpi_userdata# docker compose up -d uptime-kuma
[+] up 1/1
 ✔ Container uptime-kuma Started                                                                                          4.5s
root@PetitPois:/mnt/dietpi_userdata# docker compose pull
[+] pull 12/14
 ✔ Image eclipse-mosquitto                                                           Pulled                               1.3s
 ✔ Image koenkk/zigbee2mqtt                                                          Pulled                               1.5s
 ⠹ Image ghcr.io/home-assistant/home-assistant:stable [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿] 500.2MB / 502.4MB Pulling                             96.2s
 ✔ Image louislam/uptime-kuma:2                                                      Pulled                               1.4s
failed to extract layer (application/vnd.oci.image.layer.v1.tar+zstd sha256:4c46ee32c2704a325cc86f1207455c8afd46714e94d146a8020d11df0585ea79) to overlayfs as "extract-471586625-kycr sha256:14000ee96b40b98022e1c627545f7f254775d3a9707cdd4c22e53aec5c9ad9c3": corruption detected: stream overrun 4
root@PetitPois:/mnt/dietpi_userdata# apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@PetitPois:/mnt/dietpi_userdata# dietpi-update

Extra details

  • I’m trying to update Homeassistant Container from 20206.5.3 to 2026.5.4.
  • I’m not sure this is a DietPi issue but hoping someone might know what’s happening.
2

I doubt this is a DietPi issue. Looks like corruption of the docker image or download issue or a full file system

3

Thanks

edit: a restart fixed it.

edit: …then it happened again and this time a restart did not fix.

However, for anyone with the same issue, this is the solution:

The solution is to disable parallel decompression for docker images on the host. Here’s how you can do it:

  1. Open the Docker systemd unit file /lib/systemd/system/docker.service using a text editor with root permissions:

sudo nano /lib/systemd/system/docker.service

  1. Add the following line under the [Service] section:

Environment=MOBY_DISABLE_PIGZ=1

  1. Save the file and reload the systemd configuration:

sudo systemctl daemon-reload

  1. Restart the Docker daemon for the changes to take effect:

sudo systemctl restart docker

After restarting the Docker daemon, parallel decompression should be disabled for Docker images on the host.

Note that this method modifies the Docker service directly, so any changes made to the systemd unit file will persist across system reboots.

Also, the downside to this workaround is that it’ll take longer for you to pull images.