Docker buildx build image already created don't pull correctly #2418
Unanswered
mamu-reply
asked this question in
Q&A
Replies: 2 comments
-
I encountered a similar error and it was because we had created a layer called "tests" but were mistakenly referring to it as "test" when copying from it. If you try to pull from a non-existent layer called "foobar" for example: |
Beta Was this translation helpful? Give feedback.
0 replies
-
This also affects docker compose (the plugin) for local only images (e.g. in tests): docker/compose#9939 Edit: docker buildx rm --all-inactive
docker buildx create --driver docker --use default # for me this gave an error but still worked
docker buildx inspect # should show Driver: docker |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have this situation, I built a dockerfile, then I created an instance for buildx and subsequently I built another dockerfile with buildx which has as FROM the image I had built previously.
E.g.
Dockefile1:
docker build -t test test1/Dockerfile1
docker buildx create test --use
Dockerfile2
docker buildx build -t test2 test2/Dockerfile2
and i have this error
ERROR: failed to solve: test: failed to resolve source metadata for docker.io/library/test:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
But if i do the same thing without the buildx create command it work fine, but i need this commando to set a driver.
Anyone can help me? Thanks
Beta Was this translation helpful? Give feedback.
All reactions