Skip to content

Check out blacksmith#256

Open
blacksmith-sh[bot] wants to merge 3 commits into
developfrom
blacksmith-migration-efed0dc
Open

Check out blacksmith#256
blacksmith-sh[bot] wants to merge 3 commits into
developfrom
blacksmith-migration-efed0dc

Conversation

@blacksmith-sh

@blacksmith-sh blacksmith-sh Bot commented Jul 10, 2026

Copy link
Copy Markdown

This PR has been automatically generated by a team member in your GitHub organization using Blacksmith's Migration Wizard. This PR changes the following:

  1. Your selected workflows will now run on Blacksmith's 2x faster hardware (e.g., runs-on: blacksmith-4vcpu-ubuntu-2204). Learn more about the different instances available to choose from.
  2. Your jobs running on Blacksmith will now have all official GitHub and popular third-party cache actions automatically interact with our 4x faster, colocated cache. Learn more about Blacksmith's actions cache.
  3. Your GitHub Actions will now actually be observable. Learn more about Blacksmith's logging and other observability features.
  4. Your Docker builds will now automatically share their Docker layer cache, resulting in up to 40x faster builds. Learn more about Blacksmith's Docker layer caching.

View with Codesmith
Need help on this PR? Tag /codesmith with what you need. Autofix is enabled.

@rakshith-ravi rakshith-ravi changed the title .github/workflows: Migrate workflows to Blacksmith runners Checkout blacksmith Jul 10, 2026
@rakshith-ravi rakshith-ravi changed the title Checkout blacksmith Check out blacksmith Jul 10, 2026
@blacksmith-sh

This comment has been minimized.

rakshith-ravi and others added 2 commits July 10, 2026 20:01
The @docker e2e suite runs the docker runner's production topology (Docker
Swarm + overlay + routing-mesh published ports + VIP service discovery)
inside privileged DinD. The swarm routing mesh needs the kernel IPVS
modules, which Blacksmith's Firecracker microVM guest kernel doesn't
provide, so published ports never route and every deployment test times
out waiting on the faux edge. Every other job migrates to Blacksmith
cleanly; this one stays on ubuntu-latest.

Co-authored-by: Codesmith <[email protected]>
The docker runner binary bakes its config path from CARGO_MANIFEST_DIR at compile time in debug builds. Building it on Blacksmith (/home/runner/_work/...) and then downloading it into the github-hosted docker-tests job (/home/runner/work/...) left the baked path unresolvable, so the runner died with a missing-config error. Build it on the same runner OS that runs the @docker suite so the compile-time and run-time repo paths match.

Co-authored-by: Codesmith <[email protected]>
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.

1 participant