Skip to content

trainer: Add GPU passthrough documentation for local execution mode#4275

Open
muzzlol wants to merge 1 commit intokubeflow:masterfrom
muzzlol:docs/trainer-container-gpu-passthrough
Open

trainer: Add GPU passthrough documentation for local execution mode#4275
muzzlol wants to merge 1 commit intokubeflow:masterfrom
muzzlol:docs/trainer-container-gpu-passthrough

Conversation

@muzzlol
Copy link

@muzzlol muzzlol commented Jan 6, 2026

Description of Changes

Adds GPU passthrough documentation for Docker and Podman local execution backends:

  • docker.md: New "GPU Training" section with prerequisites (NVIDIA Container Toolkit), code example using resources_per_node={"gpu": "1"}, and troubleshooting
  • podman.md: New "GPU Training" section with CDI-specific prerequisites, code example, and troubleshooting (including CDI device issues)
  • overview.md: Added "NVIDIA GPU Support" row to backend comparison table

Documents platform support (Linux, Windows via WSL2) and notes macOS limitation.

Related Issues

Related: kubeflow/sdk#219

Checklist

Signed-off-by: muzzlol <muzxmmilkhxn@gmail.com>
@google-oss-prow google-oss-prow bot added the area/trainer AREA: Kubeflow Trainer / Kubeflow Training Operator label Jan 6, 2026
@google-oss-prow google-oss-prow bot requested review from Jeffwan and gaocegege January 6, 2026 11:24
@google-oss-prow
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign terrytangyuan for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@google-oss-prow
Copy link

Hi @muzzlol. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@github-actions
Copy link

github-actions bot commented Jan 6, 2026

🚫 This command cannot be processed. Only organization members or owners can use the commands.

Copy link
Member

@Arhell Arhell left a comment

Choose a reason for hiding this comment

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

/ok-to-test

@juliusvonkohout
Copy link
Member

@andreyvelich

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/trainer AREA: Kubeflow Trainer / Kubeflow Training Operator ok-to-test size/L

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments