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

[GH-ISSUE #15091] Ollama pull will fully hang #71735

New Issue
Open
opened 2026-05-05 02:26:01 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-05 02:26:01 -05:00
Owner
Copy Link

Originally created by @Cazforshort on GitHub (Mar 27, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/15091

What is the issue?

ollama pulls dont get to the "pulling manifest" print. No log output.

Shutting down wsl fixed the issue.

Relevant log output

Codex was running in VSCode (via WSL) actively. Not sure if that had something to do with it, but it was also killed with wsl shutdown.

OS

WSL2

GPU

Nvidia

CPU

Intel

Ollama version

0.18.3

Originally created by @Cazforshort on GitHub (Mar 27, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/15091 ### What is the issue? ollama pulls dont get to the "pulling manifest" print. No log output. Shutting down wsl fixed the issue. ### Relevant log output ```shell Codex was running in VSCode (via WSL) actively. Not sure if that had something to do with it, but it was also killed with wsl shutdown. ``` ### OS WSL2 ### GPU Nvidia ### CPU Intel ### Ollama version 0.18.3
GiteaMirror added the bug label 2026-05-05 02:26:01 -05:00
GiteaMirror commented 2026-05-05 02:26:02 -05:00
Author
Owner
Copy Link

@ssam18 commented on GitHub (Mar 28, 2026):

Can you please provide the stack trace to take a look into this issue?

<!-- gh-comment-id:4148755805 --> @ssam18 commented on GitHub (Mar 28, 2026): Can you please provide the stack trace to take a look into this issue?
GiteaMirror commented 2026-05-05 02:26:03 -05:00
Author
Owner
Copy Link

@PureBlissAK commented on GitHub (Apr 18, 2026):

🤖 Automated Triage & Analysis Report

Issue: #15091
Analyzed: 2026-04-18T18:23:06.527874

Analysis

  • Type: unknown
  • Severity: medium
  • Components: unknown

Implementation Plan

  • Effort: medium
  • Steps:

This issue has been triaged and marked for implementation.

<!-- gh-comment-id:4274311243 --> @PureBlissAK commented on GitHub (Apr 18, 2026): <!-- ollama-issue-orchestrator:v1 issue:15091 --> ## 🤖 Automated Triage & Analysis Report **Issue**: #15091 **Analyzed**: 2026-04-18T18:23:06.527874 ### Analysis - **Type**: unknown - **Severity**: medium - **Components**: unknown ### Implementation Plan - **Effort**: medium - **Steps**: *This issue has been triaged and marked for implementation.*
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#71735
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?