fix deno cache copy in Docker build - #356
Draft
IsaacThoman wants to merge 1 commit into
Draft
Conversation
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
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.
What changed
cp -a /tmp/deno-cache/. /deno-dirwith a tar pipeline.*-waland*-shmfrom the copied runtime cache.Why
Recent Coolify deployments failed nondeterministically when
cp -atried to copy transient Deno cache SQLite sidecar files after they disappeared:Those files are not required in the runtime image, so excluding them prevents the deployment from failing on a cache race.
Validation
deno task allchecksLocal Docker smoke testing could not run because the local Docker socket was unavailable.