docker engine fails to start with error `Kyperkit: exit status 1`

[heidimhurst]

Description

I am unable to start docker engine from time to time on a Mac Intel chip with warning Something went wrong: Kyperkit: Exit Status 1.

Prior to this issue, I had configured docker to use gRPC Fuse and disabled the virtualization framework per the following threads for other bugs:

• https://github.com/docker/for-mac/issues/6824#issuecomment-1781819905
• https://github.com/microsoft/vscode-remote-release/issues/8967#issuecomment-1873199481
• https://github.com/microsoft/vscode/issues/194458#issuecomment-1912849373

This has happened a number of times, and seems to occur when I exit docker whilst a container is still running.

To get things working again, I have typically resorted to re-installing docker (obviously a clunky and time consuming workaround).

Selecting the option on the above popup to reset to factory settings does not resolve the problem. Once reset to factory settings, a different error occurs:

Something went wrong.  
Invalid virtual machine configuration.
The storage device attachment is invalid.

Reproduce

1. On Mac intel chip, change virtualization settings to gRPC fuse & disable virtualization framework
2. Spin up a container and leave it running
3. Log out of your computer, leaving the operating system to close docker
4. Log back in and try to open docker without it crashing

Expected behavior

One should be able to restart docker.

docker version

Client:
 Cloud integration: v1.0.35+desktop.10
 Version:           25.0.3
 API version:       1.44
 Go version:        go1.21.6
 Git commit:        4debf41
 Built:             Tue Feb  6 21:13:26 2024
 OS/Arch:           darwin/amd64
 Context:           desktop-linux

docker info

Client:
 Version:    25.0.3
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.12.1-desktop.4
  compose: Docker Compose (Docker Inc.)
    Version:  v2.24.5-desktop.1
  debug: Get a shell into any image or container. (Docker Inc.)
    Version:  0.0.24
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.21
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.4
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.0.0
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
  scout: Docker Scout (Docker Inc.)
    Version:  v1.4.1

Diagnostics ID

6CB8FADA-1156-478D-9A12-E4BE999DC6F4/20240228091339

Additional Info

No response

[dgageot]

cc @doringeman

[heidimhurst]

Just wanted to bump this as it's still a pain point cc: @dgageot @doringeman

[PeterParker]

I am also seeing this issue as described above. Please let us know if we can offer up any further information to help debug.

[heidimhurst]

This also occurs on 4.28, see diagnostics ID A08BB3CB-9B28-4956-8512-0C18B6AD717D/20240404101203

[gauravsinghaec]

Issue persist even with 4.31.0 It happens suddenly, during docker build.. The root cause is still not found. I tried restarting the docker desktop but no luck. But Docker Desktop does give below error: A Painful Workaround: It starts working once I restart my system. But again after couple of builds, it gives same error.

and if you restore factory and restart docker, then below comes.

[ruscon]

4.31.0 and 4.32.0 I came across the same problem. Restarting, reseting and cleaning docker doesn't help.