Is DevKinsta just completely BROKEN?

Q: Date/Time this occurred (Provide your time zone also)
**A:**Dec16 01:25

Q: DevKinsta Version
**A:**Version 2.13.4 (2.13.4.8833)

Q: OS Version
**A:**mac Sequoia 15.2 (24C101)

Q: Docker Desktop Version
**A:**4.31.0 (153195)

Q: Were any error codes or messages observed? If so, what were they?
A: DK0009

Q: Detailed Description of the Problem
**A:**DevKinsta wouldn’t start, so I tried to reinstall. Now it won’t start images and give DK0009…

logs:

at _next (file:///Applications/DevKinsta.app/Contents/Resources/app.asar/dist/renderer.prod.js:8:2024728)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

[2024-12-16 01:19:16.193] [error] Error - DK0009: START_DOCKER_CONTAINER_COMMON: Cannot start docker container
at file:///Applications/DevKinsta.app/Contents/Resources/app.asar/dist/renderer.prod.js:2:3317761
at tryCatch (file:///Applications/DevKinsta.app/Contents/Resources/app.asar/dist/renderer.prod.js:8:2033184)
at Generator. (file:///Applications/DevKinsta.app/Contents/Resources/app.asar/dist/renderer.prod.js:8:2034833)
at Generator.next (file:///Applications/DevKinsta.app/Contents/Resources/app.asar/dist/renderer.prod.js:8:2033733)
at asyncGeneratorStep (file:///Applications/DevKinsta.app/Contents/Resources/app.asar/dist/renderer.prod.js:8:2024429)
at _next (file:///Applications/DevKinsta.app/Contents/Resources/app.asar/dist/renderer.prod.js:8:2024728)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

It’s the MailHog container that doesn’t let it start. It keeps restarting…

I’m so tired of SO MANY ISSUES with DevKinsta. Obviously, it isn’t anywhere near as good as Local. Because of this I may just migrate to WP Engine…

Also noticed that the docker images haven’t been updated in 9 months?! Has there been no development to fix your completely broken application?

Hello Kevin :wave:

I’m sorry to hear that you’re experiencing issues.

I would suggest:

  • quiting DevKinsta (leave the Docker active)
  • select all containers who’s names start with ‘devkinsta_’ and delete them
  • start DevKinsta again (the containers should automatically recreate)
  • check if that resolves the issue

As for the development of DevKinsta, it is currently in maintenance and security updates mode only.

Please let me know if the above resolves the issue.

Kind regards