Skip to content

Conversation

@doringeman
Copy link
Contributor

Fixes #441.

The CLI now detects when pulling from hf.co/* repositories and automatically reads the HF_TOKEN environment variable. The token is passed through the ModelCreateRequest to the backend, which uses authn.Bearer for authentication with the registry.

The CLI now detects when pulling from hf.co/* repositories and automatically reads the HF_TOKEN environment variable. The token is passed through the ModelCreateRequest to the backend, which uses authn.Bearer for authentication with the registry.

Co-authored-by: Ignasi <[email protected]>
Signed-off-by: Dorin Geman <[email protected]>
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @doringeman, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new feature that enables seamless bearer token authentication for pulling models, specifically from Hugging Face repositories. By automatically detecting Hugging Face model references and utilizing the HF_TOKEN environment variable, the system can now authenticate model pulls, enhancing security and access to private or restricted models. This change involves modifications across the CLI, API, and backend distribution logic to properly handle and apply the authentication token.

Highlights

  • Hugging Face Token Detection: The CLI now automatically detects when a model pull targets a Hugging Face repository (prefixed with 'hf.co/') and reads the HF_TOKEN environment variable for authentication.
  • Bearer Token Propagation: The HF_TOKEN is now passed from the CLI through the ModelCreateRequest to the backend, ensuring secure transmission for authentication.
  • Registry Authentication with Bearer Tokens: The backend's distribution client has been enhanced to utilize the provided bearer token for authn.Bearer authentication when interacting with model registries, enabling access to private or restricted models.
  • Flexible Registry Client Configuration: New utility functions (WithAuth, FromClient) have been added to the registry client, allowing for the creation of temporary registry clients with specific authentication configurations without modifying the base client.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey there - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds support for bearer token authentication when pulling models from Hugging Face, using the HF_TOKEN environment variable. The changes are well-structured, introducing a new BearerToken field in the ModelCreateRequest and propagating it through the layers to the distribution client. The use of functional options and a temporary client for authentication is a clean approach. I've made one suggestion to simplify the code in pkg/inference/models/manager.go for better maintainability. Overall, the implementation is solid and effectively addresses the feature requirement.

Comment on lines +988 to +994
var err error
if bearerToken != "" {
m.log.Infoln("Using provided bearer token for authentication")
err = m.distributionClient.PullModel(r.Context(), model, progressWriter, bearerToken)
} else {
err = m.distributionClient.PullModel(r.Context(), model, progressWriter)
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This if/else block can be simplified. The distribution.Client.PullModel function takes a variadic bearerToken ...string argument. Calling it with an empty string for bearerToken is handled correctly by the receiver and has the same effect as calling it without the variadic argument. You can remove the else block and always pass the bearerToken.

        if bearerToken != "" {
			m.log.Infoln("Using provided bearer token for authentication")
		}
		err = m.distributionClient.PullModel(r.Context(), model, progressWriter, bearerToken)

…tion header on redirect

Co-authored-by: Ignasi <[email protected]>
Signed-off-by: Dorin Geman <[email protected]>
@doringeman doringeman merged commit a9491b1 into docker:main Nov 25, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docker model pull does not appear to use HF_TOKEN environment variable

3 participants