ollama - 💡(How to fix) Fix Add flag to the install script to skip NVIDIA/CUDA and force Vulkan or CPU-only [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
ollama/ollama#15510Fetched 2026-04-12 13:24:10
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Participants
Timeline (top)
labeled ×1
RAW_BUFFERClick to expand / collapse

Hi team,

I'm currently using Ollama on Linux and I've noticed that the current install.sh script automatically assumes an NVIDIA setup if it detects certain drivers or binaries, even when the user intends to use Vulkan or strictly CPU.

This often results in unnecessary downloads of heavy CUDA dependencies or installation failures when the environment doesn't perfectly match the script's detection logic.

Proposed Feature: It would be extremely helpful to have a flag (e.g., --vulkan or --skip-nvidia) in the installer script to:

Manually select the backend: Force the installation of Vulkan-compatible libraries.

Minimize footprint: Avoid downloading several GBs of CUDA-related data when they aren't needed.

Improve Container Compatibility: Allow for cleaner installs in specialized environments like Fedora Silverblue (Toolbox) or SteamOS.

Example usage: curl -fsSL https://ollama.com/install.sh | sh -s -- --vulkan

Having this level of control would greatly improve the experience for Linux users who are moving away from proprietary stacks or working in restricted environments.

Thanks for the amazing work on Ollama!

extent analysis

TL;DR

Adding a flag to the install script, such as --vulkan or --skip-nvidia, would allow users to manually select the backend and avoid unnecessary CUDA downloads.

Guidance

  • Consider modifying the install.sh script to include a flag for manually selecting the backend, such as --vulkan or --skip-nvidia.
  • Evaluate the current detection logic to determine why it's assuming an NVIDIA setup even when the user intends to use Vulkan or CPU.
  • Test the proposed flag with various environments, including Fedora Silverblue (Toolbox) and SteamOS, to ensure compatibility.
  • Document the new flag and its usage, such as curl -fsSL https://ollama.com/install.sh | sh -s -- --vulkan, to inform users of the new functionality.

Example

# Proposed example usage
curl -fsSL https://ollama.com/install.sh | sh -s -- --vulkan

Notes

The implementation of the flag would require modifications to the install.sh script, and thorough testing would be necessary to ensure the flag works as expected in different environments.

Recommendation

Apply workaround: Add a flag to the install script to allow manual selection of the backend, as this would provide users with more control over the installation process and improve compatibility with restricted environments.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

ollama - 💡(How to fix) Fix Add flag to the install script to skip NVIDIA/CUDA and force Vulkan or CPU-only [1 participants]