Skip to content

Conversation

@olupton
Copy link
Collaborator

@olupton olupton commented Jul 30, 2025

This helps CUDA forward compatibility work when spawning processes over SSH, as those processes do not see environment variables set by the container entrypoint that handles forward compatibility.
/usr/local/cuda/compat/lib will only exist if the entrypoint detects that forward compatibility mode is enabled.

This helps CUDA forward compatibility work when spawning processes over
SSH, as those processes do not see environment variables set by the
container entrypoint that handles forward compatibility.
/usr/local/cuda/compat/lib will only exist if the entrypoint detects
that forward compatibility mode is enabled.
@olupton olupton merged commit b4bf8c0 into main Jul 30, 2025
80 of 93 checks passed
@olupton olupton deleted the olupton/fix-k8s-nccl branch July 30, 2025 13:12
olupton added a commit that referenced this pull request Jul 30, 2025
This helps CUDA forward compatibility work when spawning processes over
SSH, as those processes do not see environment variables set by the
container entrypoint that handles forward compatibility.
`/usr/local/cuda/compat/lib` will only exist if the entrypoint detects
that forward compatibility mode is enabled.
olupton added a commit that referenced this pull request Jul 30, 2025
This helps CUDA forward compatibility work when spawning processes over
SSH, as those processes do not see environment variables set by the
container entrypoint that handles forward compatibility.
`/usr/local/cuda/compat/lib` will only exist if the entrypoint detects
that forward compatibility mode is enabled.
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