Update Docker CI tags to 20251203-1e15fed

[flashinfer-bot]

This PR updates the Docker CI image tags to the latest version: 20251203-1e15fed

Updated images:

• flashinfer/flashinfer-ci-cu126:20251203-1e15fed
• flashinfer/flashinfer-ci-cu128:20251203-1e15fed
• flashinfer/flashinfer-ci-cu129:20251203-1e15fed
• flashinfer/flashinfer-ci-cu130:20251203-1e15fed

Auto-generated by release-ci-docker workflow

Summary by CodeRabbit

• Chores
  • Updated container image configurations used in the build pipeline for improved compatibility and performance across multiple CUDA versions.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Updated four Docker image tag digests in the CI configuration from 4efb7bb to 1e15fed for CUDA versions 12.6, 12.8, 12.9, and 13.0. No structural or behavioral changes; existing configuration keys and control flow remain unaffected.

Changes

Cohort / File(s)	Summary
Docker CI Configuration ci/docker-tags.yml	Updated digest values for four flashinfer CI Docker images (cu126, cu128, cu129, cu130) from 4efb7bb to 1e15fed

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update Docker CI tags to 20251024-0e48aaf #1975: Updates the same ci/docker-tags.yml entries for the four flashinfer CI images with new digests
• Update Docker CI tags to 20251104-d528f0c #2041: Modifies the same ci/docker-tags.yml entries for flashinfer-ci-cu126, cu128, cu129, cu130 image references
• Update Docker CI tags to 20251202-23ff744 #2158: Updates the same ci/docker-tags.yml entries for the four flashinfer CI images with revised digests

Suggested reviewers

• cyx-6
• nvmbreughe
• yzh119

Poem

🐰 Hop hop, the digests dance!
Four CUDA images skip and prance,
From old 4efb to new 1e15fed,
Docker tags freshly spread!
CI pipelines, rebuild and led! 🐳✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description includes the key details about what was changed and why, but lacks formal sections matching the template (Description, Related Issues) and the required checklist items are unchecked.	Structure the description to match the template sections: add a formal Description section at the top, confirm Related Issues (if any), and consider whether pre-commit checks and tests apply to this automated change.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely describes the main change: updating Docker CI tags to the new version 20251203-1e15fed.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update-docker-tags-20251203-1e15fed

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1e15fed and 5480944.

📒 Files selected for processing (1)

• ci/docker-tags.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Deploy Docs

🔇 Additional comments (1)

ci/docker-tags.yml (1)

1-4: ✓ Approved: Consistent Docker tag update across all CUDA versions.

All four Docker image tags have been updated consistently to the same digest (20251203-1e15fed), maintaining the expected format for each CUDA version (12.6, 12.8, 12.9, 13.0). The automated update from the CI workflow appears correct with no formatting issues or inconsistencies.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @flashinfer-bot, I'm Gemini Code Assist¹! 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 aims to keep the project's Continuous Integration (CI) environment current by updating the Docker image tags used for various CUDA versions. By bumping these image versions, the CI system will leverage the latest build environments, ensuring that tests and builds are performed against up-to-date dependencies and configurations, which helps maintain stability and compatibility across the development lifecycle.

Highlights

• Docker CI Image Updates: The pull request updates the Docker CI image tags for flashinfer/flashinfer-ci-cu126, flashinfer/flashinfer-ci-cu128, flashinfer/flashinfer-ci-cu129, and flashinfer/flashinfer-ci-cu130.
• New Image Tag: All specified Docker images are updated to the new version tag: 20251203-1e15fed.
• Automated Generation: This update was automatically generated by the release-ci-docker workflow.

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. ↩

[gemini-code-assist]

Code Review

This pull request updates the Docker CI image tags to a new version. The change itself is straightforward. However, I've identified an opportunity to improve the maintainability of the ci/docker-tags.yml file. The same tag is repeated for each image, which violates the DRY (Don't Repeat Yourself) principle. I have provided a suggestion to use YAML anchors and aliases to define the tag once and reuse it. This will make future updates, whether manual or automated, simpler and less prone to error.

[gemini-code-assist]

To improve maintainability and adhere to the DRY (Don't Repeat Yourself) principle, you can use YAML anchors and aliases. This allows you to define the Docker tag once and reuse it for all the images. This makes future updates easier and less error-prone.

flashinfer/flashinfer-ci-cu126: &ci_tag 20251203-1e15fed
flashinfer/flashinfer-ci-cu128: *ci_tag
flashinfer/flashinfer-ci-cu129: *ci_tag
flashinfer/flashinfer-ci-cu130: *ci_tag

[yzh119]

/bot run

[yzh119]

@bkryu let's see whether this PR can fix the CI issues.

[flashinfer-bot]

GitLab MR !175 has been created, and the CI pipeline #39574513 is currently running. I'll report back once the pipeline job completes.

[flashinfer-bot]

[CANCELING] Pipeline #39574513: canceled

[bkryu]

/bot run

[flashinfer-bot]

GitLab MR !175 has been created, and the CI pipeline #39579402 is currently running. I'll report back once the pipeline job completes.

[bkryu]

Not sure why the pipeline got cancelled. Rerunning. I can at least confirm that cu12 dependencies were not installed in the latest container build step, so that is good. Need to confirm whether it fixes CI faillures.

[bkryu]

/bot stop

[flashinfer-bot]

The GitLab CI pipeline #39579402 has been cancelled.

[bkryu]

/bot run

[flashinfer-bot]

GitLab MR !175 has been created, and the CI pipeline #39586176 is currently running. I'll report back once the pipeline job completes.

[bkryu]

I can confirm that the cuDNN attention tests that were failing due to RuntimeError: Multiple libcudart libraries found: libcudart.so.12 and libcudart.so.13 have been fixed, so I believe this PR is good to be checked in.

However, the issue of cuBLAS failures on the cu13 containers still persist. I am looking into what I need to fix next