setup: build the spads image instead of pulling it - #58
Open
keithharvey wants to merge 1 commit into
Open
Conversation
450fc5a moved spads to a from-scratch local image but left setup.sh pulling bar-devtools-spads:dev from the registry, which fails fresh setups with an opaque "access denied". Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
450fc5a moved spads from
badosu/spads:latestto a from-scratch local image (bar-devtools-spads:dev), and updatedservices.justtobuild spads— butsetup.shstill runs--profile spads pull spadsin two places. Docker Hub has no such image, so every freshsetup::initwith teiserver selected dies at step 4/8 with the opaquedenied: requested access to the resource is denied.Fix:
pull→buildat both call sites, matching whatservices.justalready does.🤖 Generated with Claude Code