ERROR resolve image config for docker.io/docker/dockerfile:experimental on widnows about docker-sdk HOT 8 CLOSED

FWIW (for the people who search in the future), I had a similar issue happen in WSL2 and Docker Windows when docker was previously logged in to dockerhub and then had logged out. Logging back in to a dockerhub account with Docker resolved the error.

from docker-sdk.

Ok, thanks for help. Its not demo project, but prepared by another team almost production ready. I'm going to ask them for help ;).
On linux everything works fine anyway. I have to but Apple computer i think ;P

from docker-sdk.

I am having a similar error

Any ideas, do I need to configure something for credentials inside DockerFile or devcontainer.json?

from docker-sdk.

Hi @SchmidtDawid,
googling the error message regarding dbus gives this as possible solution - microsoft/WSL#2016 (comment). Could you please check it?

Best,
Spryker Support Team

from docker-sdk.

It doesn't help. I solve the problem but I don't really know how. I upgrade windows to fast ring, upgrade WSL to v2, reinstall all libs, downgrade to v1 and it works.

but i have another problem:

shutdown  Background docker-sync has been stopped
chmod: cannot access '/data/config/Zed/*.key': No such file or directory

Do i have to install zed sdk?

from docker-sdk.

There is nothing like zed sdk. If you cloned one of our demo-shops correctly, then these keys just should be there.

So far I can say that as per our product team the WSL2 support is coming soon and it might be a solution to all Windows+docker+docker sync related problems.

From my experience the only guaranteed option for Windows is using Vagrant devvm.

Best,
Spryker Support Team

from docker-sdk.

FWIW (for the people who search in the future), I had a similar issue happen in WSL2 and Docker Windows when docker was previously logged in to dockerhub and then had logged out. Logging back in to a dockerhub account with Docker resolved the error.

To add to this answer; closing the Linux (WSL) terminal giving this error, and reopening it may be all you need to solve this issue. This was what worked for me.

Have a look at this answer and the comments below it for more details: https://stackoverflow.com/a/64254775/11838606

from docker-sdk.

docker-compose down
or
docker down
even when the container isn't running anymore.

Although my containers were stopped by using CTRL + C in console this did not cleared all container from docker desktop and so i was unable to apply changes like docker-compose build.

from docker-sdk.