docs: note CUDA container and hf build requirements#71
Open
tryingET wants to merge 1 commit intoTheTom:mainfrom
Open
docs: note CUDA container and hf build requirements#71tryingET wants to merge 1 commit intoTheTom:mainfrom
tryingET wants to merge 1 commit intoTheTom:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This docs-only PR adds two CUDA build notes that came up while bootstrapping a clean Blackwell Gemma 4 canary:
nvidia/cuda:*container, the build container also needs--gpus all, otherwise the final link step can fail with missinglibcuda.so.1/ unresolved CUDA driver symbols-hf/--hf-repo, you need OpenSSL development headers available at configure time (for examplelibssl-dev+pkg-configon Debian/Ubuntu-based systems), otherwisellama-server -hf ...can fail at runtime with the existingHTTPS is not supportedmessageThe PR keeps this as one change because both notes belong to the same user-facing build path in
docs/getting-started.md, and adds one concrete CUDA container example that includes the required packages/flags.