Repository navigation
Conversation
… checkout nix.sh started dockerd from the bind-mounted checkout, so dockerd and its children used it as their working directory. If one of them dumps core and the kernel's core_pattern is relative, the dump lands in the user's repo. On macOS with Rancher Desktop (Rosetta), BuildKit's emulator probe crashes at every dockerd start, leaving an empty `core` file in the repo root. Start dockerd from / instead. Its paths are all absolute, and nix still runs from the checkout. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Signed-off-by: Jonathan Ogilvie <jonathan.ogilvie@sumologic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
Description of your changes
nix.shstarteddockerdfrom the bind-mounted checkout, so a crashing child process with a relativecore_patterndumped core into the user's repo. On macOS with Rancher Desktop (Rosetta), BuildKit's emulator probe crashes at everydockerdstart, leaving an emptycorefile in the repo root.This starts
dockerdfrom/instead. All of its paths are absolute, andnixstill runs from the checkout.Verified:
./nix.sh flake checkpasses, and nocorefile appears.I have:
./nix.sh flake checkto ensure this PR is ready for review.Added or updated unit tests.Linked a PR or a docs tracking issue to document this change.Addedbackport release-x.ylabels to auto-backport this PR.Need help with this checklist? See the cheat sheet.
🤖 Generated with Claude Code