Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR [internal] load metadata for docker.io/laradock/workspace:latest-7.0 #2961

Closed
pizsd opened this issue Apr 26, 2021 · 3 comments
Closed

Comments

@pizsd
Copy link

pizsd commented Apr 26, 2021

Description:

Expected Behavior:

Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
Successfully built 20cf958a363a6bed7415b8626c61c20ef3d20530e3e99ca1e9f256d130cb5469
Building workspace
[+] Building 3.2s (3/3) FINISHED
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 38B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> ERROR [internal] load metadata for docker.io/laradock/workspace:latest-7.0 3.0s

[internal] load metadata for docker.io/laradock/workspace:latest-7.0:


failed to solve with frontend dockerfile.v0: failed to create LLB definition: failed commit on ref "unknown-sha256:6a5855c8e1ad4113358b80782d08188872cbdbf60b7e5288addec921b1155683": unexpected commit digest sha256:40e2f13a4c7de4ccecb965b3ad1e383bfb868f684cca761eb1d8b76dc3a359fc, expected sha256:6a5855c8e1ad4113358b80782d08188872cbdbf60b7e5288addec921b1155683: failed precondition
ERROR: Service 'workspace' failed to build

Docker version 20.10.5, build 55c4c88

@bestlong
Copy link
Member

try again docker-compose build --no-cache --pull workspace

@stale
Copy link

stale bot commented Jul 25, 2021

Hi 👋 this issue has been automatically marked as stale 📌 because it has not had recent activity 😴. It will be closed if no further activity occurs. Thank you for your contributions ❤️.

@stale stale bot added the Stale label Jul 25, 2021
@stale
Copy link

stale bot commented Aug 15, 2021

Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period. We really really appreciate your contributions, and looking forward for more in the future 🎈.

@stale stale bot closed this as completed Aug 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants