Conversation
The OSDC runner is a container and has no Docker daemon, so the build goes to the shared BuildKit pool instead. build.sh gains a REMOTE_BUILDKIT switch for it; without the variable set it behaves exactly as before. That also drops the steps that only made sense on an EC2 host: Clean workspace, setup-ssh, setup-linux and teardown-linux.
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/tutorials/3970
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New FailureAs of commit 0cb9858 with merge base 65e2e1a ( NEW FAILURE - The following job has failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[self-hosted, linux.2xlarge]mt-l-x86iavx512-8-64docker buildon the runner, then pushdocker buildx build --pushagainst the out-of-cluster BuildKit poolThe OSDC runner is a container, so it has no Docker daemon to build with. Builds go to the shared BuildKit pool instead, via
docker-build-remote-buildkit— the same path torchtitan and ExecuTorch use.build.shgains aREMOTE_BUILDKITswitch for it; without the variable set it behaves exactly as before, so local runs are unaffected.That also drops the steps that only made sense on an EC2 host:
Clean workspace,setup-ssh,setup-linux,teardown-linux, andcalculate-docker-image.Pushing to ECR needs
id-token: writeplus an OIDC login asrole/arc. The image already lives in308535385114.dkr.ecr.us-east-1.amazonaws.com/tutorials/, so no new repository is involved — but the role's resource list has not been confirmed to cover it._build-tutorials-base.yml'smanagerjob is still on[self-hosted, linux.2xlarge]and is not part of this change.Authored with Claude Code.