-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker daemon returns an API internal server errror #2475
Comments
Documenting your issue here @leovct More context in this thread: https://discord.com/channels/783719264308953108/1131048810861314169/1247547114343366757 @barnabasbusa suggested using Orbstack instead of Docker Desktop to get around this problem, I haven't tried out Orbstack myself yet. |
I think Orbstack could solve this issue. Unfortunately, it doesn't offer x86 simulation like Docker Desktop does so I can't migrate to Orbstack yet... |
We are trying to build all the images for dual arch. Which image have you failed to find a native arm image for ? |
Sorry, I did not describe the full context. At Polygon, we are also working on our kurtosis package for setting up CDK infra. Unfortunately, there is no arm build for the zkEVM prover yet. |
Unfortunately the only alternative is to run the project on an x86 machine. Docker desktop is just super buggy lately. |
What's your CLI version?
0.89.18
Description & steps to reproduce
When working with two enclaves simultaneously, the Docker daemon sometimes stops functioning and returns an API Internal Server Error. This often occurs when running kurtosis run while using kurtosis service ... on another enclave. The same issue arises when using docker commands to interact with the Docker daemon. This occurs on M1 Mac.
The only solution is then to restart the docker daemon, clean all the enclaves and redeploy the stack with kurtosis run but this is quite time-consuming
Desired behavior
Kurtosis commands execute successfully regardless of another kurtosis enclave being in the process of being run.
What is the severity of this bug?
Painful; this is causing significant friction in my workflow.
What area of the product does this pertain to?
CLI: the Command Line Interface
The text was updated successfully, but these errors were encountered: