Closed tdkt closed 1 year ago
If I understand this crash report correctly, vpnkit is overflowing it's stack, hence the STACK GUARD
.
I was experiencing similar issues, and it turned out that Docker didn't like my hosts file
That is very possible. I had a modified hosts file with spam filter, so it was quite big. Possible that a bug in vpnkit causes a stack overflow when the hosts file is big?
Yes possibly. Have you tried reverting your hosts file to the system default one, and then running docker?
I didn't think that was it and reformat the pc... But I could temporarily make a big hosts file again to test if that was it.
The one I had was 346647 lines, or just under 10MB
Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
comment.
Stale issues will be closed after an additional 30 days of inactivity.
Prevent issues from auto-closing with an /lifecycle frozen
comment.
If this issue is safe to close now please do so.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle stale
/remove-lifecycle stale
There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale
comment.
If not, this issue will be closed in 30 days.
Prevent issues from auto-closing with a /lifecycle frozen
comment.
/lifecycle stale
Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.
If you have found a problem that seems similar to this, please open a new issue.
/lifecycle locked
I can't get docker to start on mac M1 max with macos 12.4. I have filed a support ticket for that, however in the macos console app I can see that vpnkit segfaults, which AFAICT must be a memory error in vpnkit, so I report it here.
Expected behavior
no segfaults
Actual behavior
vpnkit segfaults
Information
Crash report from Console
com.docker.diagnose check