[GH-ISSUE #1657] /tmp failed to start llama runner because of security policy #47441

Closed
opened 2026-04-28 03:48:18 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @haraldujc on GitHub (Dec 21, 2023).
Original GitHub issue: https://github.com/ollama/ollama/issues/1657

I'm doing a proof-of-concept on RHEL and the issue is that our policy forbids running executables in /tmp so I am getting the failed to start llama runner message when doing an ollama run mistral.

Was wondering if the fix described in other /tmp issues provides a work around?

Thanks!

Originally created by @haraldujc on GitHub (Dec 21, 2023). Original GitHub issue: https://github.com/ollama/ollama/issues/1657 I'm doing a proof-of-concept on RHEL and the issue is that our policy forbids running executables in /tmp so I am getting the failed to start llama runner message when doing an ollama run mistral. Was wondering if the fix described in other /tmp issues provides a work around? Thanks!
Author
Owner

@mxyng commented on GitHub (Jan 8, 2024):

This should no longer be an issue as of v0.1.18 which removes the temporary executables

<!-- gh-comment-id:1881673860 --> @mxyng commented on GitHub (Jan 8, 2024): This should no longer be an issue as of v0.1.18 which removes the temporary executables
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#47441