Skip to content

Conversation

@KhalidAlansary
Copy link

Updated Docker cache mount restoration step to use the latest version of the buildkit-cache-dance action and added additional parameters for cache management.

Updated Docker cache mount restoration step to use the latest version of the buildkit-cache-dance action and added additional parameters for cache management.
@netlify
Copy link

netlify bot commented Nov 22, 2025

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit abbde08
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/6921fc1ccabf0700082413b0
😎 Deploy Preview https://deploy-preview-23759--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions github-actions bot added the area/build Relates to Dockerfiles or docker build command label Nov 22, 2025
Comment on lines +222 to +224
- name: Checkout code
uses: actions/checkout@v5
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is checkout needed here? By default build-push action should build with git context.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's for the build-cache-dance action. It needs to read the dockerfile to parse it and extract the paths of the cache mounts used in the dockerfile. Without checkout, I get this error:

No cache map provided. Trying to parse the Dockerfile to find the cache mount instructions...
Error: Failed to parse cache map. Expected JSON, got:
{}
Error: ENOENT: no such file or directory, open 'build/package/Dockerfile'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/build Relates to Dockerfiles or docker build command

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants