fix: bust Docker cache when OPENCLAW_GIT_REF changes#183
Open
kavinbmittal wants to merge 1 commit into
Open
Conversation
Docker caches RUN layers by instruction text. Since ARG default changes don't alter the RUN text, updating OPENCLAW_GIT_REF silently reuses the cached clone of the old version. Inline the ARG into the RUN via echo so that changing the ref value produces a different instruction string and forces a fresh clone.
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
2 participants
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
RUNlayers by instruction text. ChangingARG OPENCLAW_GIT_REFdefault alone doesn't invalidate the cache because theRUN git clone ...instruction string stays identical.RUNviaechoso the resolved instruction changes when the ref changes.Test plan
OPENCLAW_GIT_REFto a new tag and deploy — verify the build clones the correct version🤖 Generated with Claude Code