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

[GH-ISSUE #6499] Docker: "layers from manifest don't match image configuration" when pulling ROCm image #4091

New Issue
Closed
opened 2026-04-12 14:59:42 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-12 14:59:42 -05:00
Owner
Copy Link

Originally created by @bitfl0wer on GitHub (Aug 25, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/6499

What is the issue?

When trying to pull the rocm tagged versions of the ollama/ollama image from Docker Hub, the pull ultimately fails for me with the message layers from manifest don't match image configuration. Pulling the non-rocm versions of the image works fine, however.

So far, I have tried pulling the following tags using docker pull:

  • rocm (digest matches 0.3.5-rocm, assuming they are the same)
  • 0.3.6-rocm
  • 0.3.4-rocm

all of which yielded the same failing result.

Additional System Information:

  • OS: Fedora Linux 40 (Workstation) x64
  • Docker: Version 27.1.2, build d01f264

I do not have an ollama image already pulled: docker image ls | grep ollama yields no output.

I have also removed all containers using an ollama image.

OS

Linux

GPU

AMD

CPU

AMD

Ollama version

No response

Originally created by @bitfl0wer on GitHub (Aug 25, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/6499 ### What is the issue? When trying to pull the `rocm` tagged versions of the `ollama/ollama` image from Docker Hub, the pull ultimately fails for me with the message `layers from manifest don't match image configuration`. Pulling the non-rocm versions of the image works fine, however. So far, I have tried pulling the following tags using `docker pull`: - `rocm` (digest matches `0.3.5-rocm`, assuming they are the same) - `0.3.6-rocm` - `0.3.4-rocm` all of which yielded the same failing result. Additional System Information: - OS: Fedora Linux 40 (Workstation) x64 - Docker: Version 27.1.2, build d01f264 I do not have an ollama image already pulled: `docker image ls | grep ollama` yields no output. I have also removed all containers using an ollama image. ### OS Linux ### GPU AMD ### CPU AMD ### Ollama version _No response_
GiteaMirror added the bug label 2026-04-12 14:59:42 -05:00
GiteaMirror commented 2026-04-12 14:59:43 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Aug 25, 2024):

Apparently a problem with pigz on Fedora: https://github.com/ollama/ollama/issues/6413

FWIW pulling 0.3.4-rocm on Mint (Ubuntu/Debian based) works fine.

<!-- gh-comment-id:2308777927 --> @rick-github commented on GitHub (Aug 25, 2024): Apparently a problem with pigz on Fedora: https://github.com/ollama/ollama/issues/6413 FWIW pulling 0.3.4-rocm on Mint (Ubuntu/Debian based) works fine.
GiteaMirror commented 2026-04-12 14:59:44 -05:00
Author
Owner
Copy Link

@bitfl0wer commented on GitHub (Aug 25, 2024):

Can confirm that running dnf remove pigz solves this. Thank you!

<!-- gh-comment-id:2308781253 --> @bitfl0wer commented on GitHub (Aug 25, 2024): Can confirm that running `dnf remove pigz` solves this. Thank you!
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#4091
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?