-
Notifications
You must be signed in to change notification settings - Fork 345
Bitbucket Pipelines — GPU support #1015
Copy link
Copy link
Open
Labels
ci-bitbucketcml-runnerSubcommandSubcommandenhancementNew feature or requestNew feature or requestexternal-requestYou asked, we didYou asked, we didgpuInexplicably convoluted driversInexplicably convoluted driversp2-nice-to-haveLow priorityLow prioritytechnical-debtRefactoring, linting & tidyingRefactoring, linting & tidying
Metadata
Metadata
Labels
ci-bitbucketcml-runnerSubcommandSubcommandenhancementNew feature or requestNew feature or requestexternal-requestYou asked, we didYou asked, we didgpuInexplicably convoluted driversInexplicably convoluted driversp2-nice-to-haveLow priorityLow prioritytechnical-debtRefactoring, linting & tidyingRefactoring, linting & tidying
Continuation of #798 (review)
As per the official documentation, self-hosted Bitbucket Pipelines runners for Linux don't “provide access to the host file system” although that limitation is “subject to change in the future”
In practice, this means that every single step is containerized, and users don't have any control over container options like
docker run --gpus, even when the NVIDIA runtime is installed.