Skip to content

[WIP] Update GPU drivers. - #4505

Open
rasapala wants to merge 9 commits into
mainfrom
update_gpu_drivers1
Open

[WIP] Update GPU drivers.#4505
rasapala wants to merge 9 commits into
mainfrom
update_gpu_drivers1

Conversation

@rasapala

@rasapala rasapala commented Sep 3, 2026

Copy link
Copy Markdown
Collaborator

Testing new drivers.

🛠 Summary

JIRA/Issue if applicable.
Describe the changes.

🧪 Checklist

  • Unit tests added.
  • The documentation updated.
  • Change follows security best practices.
    ``

Copilot AI lite review requested due to automatic review settings September 3, 2026 09:36

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟡 Changes recommended

The Dockerfiles currently mount the secret in a way that makes it mandatory despite being documented as optional, which can break builds that don’t provide the secret.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

This PR introduces optional GitHub token support during Docker image builds to reduce GitHub anonymous-fetch throttling when Bazel git_repository() rules fetch dependencies (via BuildKit secrets and a temporary git credential helper).

Changes:

  • Add GITHUB_TOKEN/--secret wiring in the Makefile for the builder image build.
  • Update Ubuntu/Red Hat Dockerfiles to mount the token as a BuildKit secret and temporarily configure git credentials during the dependency prebuild step.
  • Switch the builder-image build invocation to docker buildx build.
File summaries
File Description
Makefile Adds optional GitHub token secret args and updates the builder image build command.
Dockerfile.ubuntu Mounts github_token secret and configures git credentials for Bazel dependency fetching.
Dockerfile.redhat Same as Ubuntu, plus preserves Konflux gating behavior.
Review details

Suppressed comments (2)

Dockerfile.ubuntu:297

  • RUN --mount=type=secret,id=github_token makes the secret mandatory; builds that don't pass --secret id=github_token,... will fail even though the token is documented as optional. Mark the mount as optional with required=false.
RUN --mount=type=secret,id=github_token \

Dockerfile.redhat:306

  • RUN --mount=type=secret,id=github_token makes the secret mandatory; builds that don't pass --secret id=github_token,... will fail even though the token is documented as optional. Mark the mount as optional with required=false.
RUN --mount=type=secret,id=github_token \
  • Files reviewed: 3/3 changed files
  • Comments generated: 4
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread Dockerfile.redhat
RUN if [ "$KONFLUX" == "0" ] ; then true ; else exit 0 ; fi ; \
bazel build --jobs=$JOBS ${debug_bazel_flags} //:ovms_dependencies @com_google_googletest//:gtest
# GITHUB_TOKEN (optional) avoids GitHub anonymous-fetch throttling for WORKSPACE git_repository() rules.
# Mounted as a BuildKit secret and read only by git's own credential-helper subprocess, so `set -x` below never echoes it.
Comment thread Dockerfile.ubuntu

# prebuild dependencies before copying sources & test dependencies for caching
# GITHUB_TOKEN (optional) avoids GitHub anonymous-fetch throttling for WORKSPACE git_repository() rules.
# Mounted as a BuildKit secret and read only by git's own credential-helper subprocess, so `set -x` below never echoes it.
Comment thread Makefile
Comment on lines +34 to +36
# Optional: avoids GitHub anonymous-fetch throttling during WORKSPACE git_repository() fetches.
# Passed as a BuildKit --secret (never --build-arg) so the token is never written to an image layer or history.
GITHUB_TOKEN ?=
Comment thread Makefile
endif
@cat .workspace/metadata.json
docker $(BUILDX) build $(NO_CACHE_OPTION) -f Dockerfile.$(DIST_OS) . \
docker buildx build $(NO_CACHE_OPTION) -f Dockerfile.$(DIST_OS) . \
@dtrawins dtrawins added the 2026.4 label Sep 7, 2026
@dtrawins dtrawins removed the 2026.4 label Sep 8, 2026
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.

3 participants