Force a fresh image pull on every run - #17
Merged
Merged
Conversation
Self-hosted runners keep a persistent Docker cache, so a bare `docker run image:latest` silently reuses whatever's on disk and never checks the registry. Found live: the API-key auth release never reached sportsid-inc's self-hosted runners because of this.
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.
Summary
Self-hosted runners keep a persistent Docker cache.
docker run image:latestonly pulls when the image is absent locally — an already-cached:latestis reused forever, registry updates or not.Found live: after the API-key auth release (#16),
sportsid-inc's self-hosted runners kept 404ing on upload — turned out they were still running the pre-#16 binary, silently ignoring the new K_API_URL/K_API_KEY/K_PROJECT_ID env vars and falling through to a stale legacy URL. GitHub-hosted runners never hit this (always a fresh VM, always a fresh pull) — only self-hosted ones do, which is most of the fleet.Fix:
docker run --pull always.Test plan