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

[GH-ISSUE #10902] Cannot run ollama docker any version higher than 0.6.5 #7167

New Issue
Closed
opened 2026-04-12 19:09:53 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-04-12 19:09:53 -05:00
Owner
Copy Link

Originally created by @DillonN on GitHub (May 29, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/10902

What is the issue?

Every docker version higher than 0.6.5 crashes on startup on my system.

  • 0.6.5: works fine
  • 0.6.6: crashes with ollama | exec /bin/ollama: input/output error
  • 0.6.7: crashes with ollama | exec /bin/ollama: exec format error
  • 0.6.8 and all subsequent versions: crashes with ollama | exec /bin/ollama: input/output error

Running in docker with WSL2 backend. Problem occurs even when no GPUs/volumes/ports are passed through; the container just won't start on this machine.

Relevant log output

ollama  | exec /bin/ollama: input/output error
ollama exited with code 255

OS

WSL2

GPU

Nvidia

CPU

AMD

Ollama version

0.6.6+

Originally created by @DillonN on GitHub (May 29, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/10902 ### What is the issue? Every docker version higher than 0.6.5 crashes on startup on my system. * 0.6.5: works fine * 0.6.6: crashes with `ollama | exec /bin/ollama: input/output error` * 0.6.7: crashes with `ollama | exec /bin/ollama: exec format error` * 0.6.8 and all subsequent versions: crashes with `ollama | exec /bin/ollama: input/output error` Running in docker with WSL2 backend. Problem occurs even when no GPUs/volumes/ports are passed through; the container just won't start on this machine. ### Relevant log output ```shell ollama | exec /bin/ollama: input/output error ollama exited with code 255 ``` ### OS WSL2 ### GPU Nvidia ### CPU AMD ### Ollama version 0.6.6+
GiteaMirror added the bug label 2026-04-12 19:09:53 -05:00
GiteaMirror commented 2026-04-12 19:09:54 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (May 29, 2025):

What version of docker?

<!-- gh-comment-id:2920112209 --> @rick-github commented on GitHub (May 29, 2025): What version of docker?
GiteaMirror commented 2026-04-12 19:09:54 -05:00
Author
Owner
Copy Link

@DillonN commented on GitHub (May 29, 2025):

What version of docker?

Docker version 28.1.1, build 4eba377

There are updates available, let me try that.

<!-- gh-comment-id:2920132483 --> @DillonN commented on GitHub (May 29, 2025): > What version of docker? `Docker version 28.1.1, build 4eba377` There are updates available, let me try that.
GiteaMirror commented 2026-04-12 19:09:54 -05:00
Author
Owner
Copy Link

@DillonN commented on GitHub (May 29, 2025):

@rick-github apparently the update was only for the docker desktop portion, docker engine is still at Docker version 28.1.1, build 4eba377. So still getting the error with latest version.

<!-- gh-comment-id:2920144663 --> @DillonN commented on GitHub (May 29, 2025): @rick-github apparently the update was only for the docker desktop portion, docker engine is still at `Docker version 28.1.1, build 4eba377`. So still getting the error with latest version.
GiteaMirror commented 2026-04-12 19:09:55 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (May 29, 2025):

It was a long shot. I'm using an older version and have no issues.

$ docker --version
Docker version 27.3.1, build ce12230

Are you using docker compose? Can you share your docker command or docker compose config?

<!-- gh-comment-id:2920164875 --> @rick-github commented on GitHub (May 29, 2025): It was a long shot. I'm using an older version and have no issues. ```console $ docker --version Docker version 27.3.1, build ce12230 ``` Are you using docker compose? Can you share your docker command or docker compose config?
GiteaMirror commented 2026-04-12 19:09:55 -05:00
Author
Owner
Copy Link

@DillonN commented on GitHub (May 29, 2025):

I am using docker compose, but also seeing the issue just with e.g. docker run ollama/ollama:0.6.6 too.

Here's the compose config that is currently working:

volumes:
    data:
services:
    ollama:
        image: ollama/ollama:0.6.5
        container_name: ollama
        volumes:
            - data:/root/.ollama
        ports:
            - "11434:11434"
        deploy:
            resources:
                reservations:
                    devices:
                        - driver: nvidia
                          count: all
                          capabilities: [gpu]
<!-- gh-comment-id:2920197500 --> @DillonN commented on GitHub (May 29, 2025): I am using docker compose, but also seeing the issue just with e.g. `docker run ollama/ollama:0.6.6` too. Here's the compose config that is currently working: ```yaml volumes: data: services: ollama: image: ollama/ollama:0.6.5 container_name: ollama volumes: - data:/root/.ollama ports: - "11434:11434" deploy: resources: reservations: devices: - driver: nvidia count: all capabilities: [gpu] ```
GiteaMirror commented 2026-04-12 19:09:55 -05:00
Author
Owner
Copy Link

@DillonN commented on GitHub (May 29, 2025):

Hmm, I tried the "Reset to factory defaults" option in Docker Desktop, seems like that did the trick! Blew out all my volumes unfortunately but now 0.8.0 is running. Gonna close this out.

<!-- gh-comment-id:2920248380 --> @DillonN commented on GitHub (May 29, 2025): Hmm, I tried the "Reset to factory defaults" option in Docker Desktop, seems like that did the trick! Blew out all my volumes unfortunately but now 0.8.0 is running. Gonna close this out.
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#7167
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?