github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 16:11:34 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #5979] 0.2.6-rocm and above cannot be pulled with containerd on fedora #29499

New Issue
Open
opened 2026-04-22 08:26:39 -05:00 by GiteaMirror · 8 comments
GiteaMirror commented 2026-04-22 08:26:39 -05:00
Owner
Copy Link

Originally created by @volatilemolotov on GitHub (Jul 26, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/5979

What is the issue?

Pulling the image results in

Error: failed to extract layer sha256:00d2c36d84f963d50ac6a568b0be71eea96f3579770ef47c2ac3f94d4d3c346a: exit status 1: unpigz: skipping: <stdin>: corrupted -- crc32 mismatch

This happens for 0.2.6-rocm and further vesions
Not sure why it fails and what kind of issue pigz has here. Im using k0s which comes packaged with its own containerd so its not using fedora installed.

Really not sure where to look for a potential cause

OS

Linux

GPU

No response

CPU

Intel, AMD

Ollama version

0.3.0

Originally created by @volatilemolotov on GitHub (Jul 26, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/5979 ### What is the issue? Pulling the image results in ``` Error: failed to extract layer sha256:00d2c36d84f963d50ac6a568b0be71eea96f3579770ef47c2ac3f94d4d3c346a: exit status 1: unpigz: skipping: <stdin>: corrupted -- crc32 mismatch ``` This happens for 0.2.6-rocm and further vesions Not sure why it fails and what kind of issue pigz has here. Im using k0s which comes packaged with its own containerd so its not using fedora installed. Really not sure where to look for a potential cause ### OS Linux ### GPU _No response_ ### CPU Intel, AMD ### Ollama version 0.3.0
GiteaMirror added the bug label 2026-04-22 08:26:40 -05:00
GiteaMirror commented 2026-04-22 08:26:43 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Jul 26, 2024):

fwiw, I'm able to pull and run with Docker Desktop. (confirmed with ollama/ollama:0.2.6-rocm as well as ollama/ollama:rocm) so I think the images we pushed up to Docker Hub are valid.

<!-- gh-comment-id:2253294172 --> @dhiltgen commented on GitHub (Jul 26, 2024): fwiw, I'm able to pull and run with Docker Desktop. (confirmed with `ollama/ollama:0.2.6-rocm` as well as `ollama/ollama:rocm`) so I think the images we pushed up to Docker Hub are valid.
GiteaMirror commented 2026-04-22 08:26:45 -05:00
Author
Owner
Copy Link

@volatilemolotov commented on GitHub (Jul 27, 2024):

Im also able to pull with docker on my PC.

Need it on k8s and cannot pull it nor understand what is the issue, im here looking for ideas

<!-- gh-comment-id:2254234639 --> @volatilemolotov commented on GitHub (Jul 27, 2024): Im also able to pull with docker on my PC. Need it on k8s and cannot pull it nor understand what is the issue, im here looking for ideas
GiteaMirror commented 2026-04-22 08:26:45 -05:00
Author
Owner
Copy Link

@Krios0815 commented on GitHub (Jul 29, 2024):

Having the same problem here. When I start pulling an image, either via the command line or via Portainer, it works normall at first.
Only after the download and extraction finished, the pulling exited with the error: „layers from manifest don't match image configuration“.

The „normal“ :latest image is working fine, just my homeserver cant take ithe load without the GPU.

Are there any alternative downloads available?

<!-- gh-comment-id:2254728931 --> @Krios0815 commented on GitHub (Jul 29, 2024): Having the same problem here. When I start pulling an image, either via the command line or via Portainer, it works normall at first. Only _after_ the download and extraction finished, the pulling exited with the error: **„layers from manifest don't match image configuration“**. _The „normal“ :latest image is working fine_, just my homeserver cant take ithe load without the GPU. Are there any alternative downloads available?
GiteaMirror commented 2026-04-22 08:26:45 -05:00
Author
Owner
Copy Link

@rmcmilli commented on GitHub (Jul 29, 2024):

I'm also having this issue on Fedora 40 with docker engine (non-desktop)

<!-- gh-comment-id:2256826127 --> @rmcmilli commented on GitHub (Jul 29, 2024): I'm also having this issue on Fedora 40 with docker engine (non-desktop)
GiteaMirror commented 2026-04-22 08:26:46 -05:00
Author
Owner
Copy Link

@anaxios commented on GitHub (Jul 31, 2024):

I'm having the same issue.

<!-- gh-comment-id:2259426356 --> @anaxios commented on GitHub (Jul 31, 2024): I'm having the same issue.
GiteaMirror commented 2026-04-22 08:26:46 -05:00
Author
Owner
Copy Link

@rkoopmans commented on GitHub (Jul 31, 2024):

I have the same problem. Normal image works fine, rocm build (layers from manifest don't match image configuration)

<!-- gh-comment-id:2259820056 --> @rkoopmans commented on GitHub (Jul 31, 2024): I have the same problem. Normal image works fine, rocm build (layers from manifest don't match image configuration)
GiteaMirror commented 2026-04-22 08:26:46 -05:00
Author
Owner
Copy Link

@volatilemolotov commented on GitHub (Aug 1, 2024):

Seems that the issue is with the package pigz which in my case when detected on system means that containerd will use unpigz to exctract the image. Removing the package and reboot works. In my case pigz was not a dependency of anything to it was easy to remove

<!-- gh-comment-id:2263009015 --> @volatilemolotov commented on GitHub (Aug 1, 2024): Seems that the issue is with the package pigz which in my case when detected on system means that containerd will use unpigz to exctract the image. Removing the package and reboot works. In my case pigz was not a dependency of anything to it was easy to remove
GiteaMirror commented 2026-04-22 08:26:47 -05:00
Author
Owner
Copy Link

@volatilemolotov commented on GitHub (Aug 1, 2024):

Containerd on start detects if there is unpigz and should it use it

https://github.com/containerd/containerd/issues/3824#issuecomment-553802643

<!-- gh-comment-id:2263039911 --> @volatilemolotov commented on GitHub (Aug 1, 2024): Containerd on start detects if there is unpigz and should it use it https://github.com/containerd/containerd/issues/3824#issuecomment-553802643
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#29499
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?