Dear everyone
,
I am creating a laravel project and to create the various containers I am using Laravel Sail. I’ll attach two screens to give you a better understanding.
Unfortunately I get the following docker error and I am afraid there are problems in my docker configuration since laravel Sail is a well established tool but I am new to docker.
I have already tried many of the solutions tried by other users and checked all the installation steps.
If you could give me any advice or suggestions on the causes of the following error, I would be very grateful.
Best regards,
Tania Migliorini
Hi,
i had the same problem is the following post from github helped me:rm ~/.docker/config.json and then docker login fixed this for me.”
opened 12:19AM - 09 Dec 22 UTC
closed 07:07PM - 15 Feb 23 UTC
lifecycle/locked
version/4.15.0
- [x] I have tried with the latest version of Docker Desktop
- [x] I have tri… ed disabling enabled experimental features
- [x] I have uploaded Diagnostics
- Diagnostics ID: 19F81D66-208B-4961-8B58-224BD03454A4/20221209000906
### Expected behavior
The Dockerfile, since it only contains the line `FROM ubuntu:18.04` should build successfully.
### Actual behavior
I receive the following error:
```
[+] Building 0.7s (2/3)
[+] Building 0.8s (3/3) FINISHED
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 2.86kB 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> ERROR [internal] load metadata for docker.io/library/ubuntu:18.04 0.6s
------
> [internal] load metadata for docker.io/library/ubuntu:18.04:
------
failed to solve with frontend dockerfile.v0: failed to create LLB definition: rpc error: code = Unknown desc = error getting credentials - err: exit status 1, out: ``
```
### Information
The problem is reproducible on my computer, and remains despite cleaning/purging data, restarting docker, resetting docker to factory settings, and restarting my computer.
- macOS Version: 12.4
- Intel chip or Apple chip: Intel chip
- Docker Desktop Version: 4.15.0
### Output of `/Applications/Docker.app/Contents/MacOS/com.docker.diagnose check`
```
Starting diagnostics
[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0014: are the backend processes running?
[PASS] DD0007: is the backend responding?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[PASS] DD0012: is the VM networking working?
[SKIP] DD0030: is the image access management authorized?
[FAIL] DD0019: is the com.docker.vmnetd process responding? failed to ping vmnetd with error: failed to connect to /var/run/com.docker.vmnetd.sock: is vmnetd running?: dial unix /var/run/com.docker.vmnetd.sock: connect: no such file or directory
[PASS] DD0033: does the host have Internet access?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0032: do Docker networks overlap with host IPs?
Please investigate the following 1 issue:
1 : The test: is the com.docker.vmnetd process responding?
Failed with: failed to ping vmnetd with error: failed to connect to /var/run/com.docker.vmnetd.sock: is vmnetd running?: dial unix /var/run/com.docker.vmnetd.sock: connect: no such file or directory
The com.docker.vmnetd process is needed to create symlinks for CLIs in your path.
```
### Steps to reproduce the behavior
1. Create a `Dockerfile` with one line: `FROM ubuntu:18.04`
2. Run `sudo docker build -t test .`
