Hi, I just started using devkinsta, after being a happy kinsta customer for years, and installing it on my main computer, I run into the error (on DevKinsta startup):
DK0083 Unsupported docker volume path on WSL
The trouble shooting page suggests I reinstall docker. I tried that twice, along with reinstalling DevKinsta. I have tried using Windows containers and Linux containers. I also tried changing the container location. I can create sample containers and they run fine in docker, but DevKinsta produces the same error. I tried updating WSL, and it updated and lists as version 2. The list of containers in WSL shows up as the default docker ones (when using WSL, they are started, stopped when using HyperV).
So, what am I doing wrong? Any ideas would be very much appreciated
Hello @gregadev and welcome to the DevKinsta Community!
Can you please send me a copy of your main.log file via DM? You can find it inside the following folder:
C:\Users\YOURUSERNAME\AppData\Roaming\DevKinsta\logs.
We’d like to give a look at it and help you find the culprit.
I tried to install DevKinsta for all users, thinking I hadn’t tried that - but noticed the certificate was revoked? I re-downloaded the installer, still the same thing…I don’t think that is relevant here, but perhaps I’m getting the wrong file from the site?
Hi @gregadev as I don’t have a Windows machine where to try to replicate the issue, I’ve asked our devs for suggestions on where the issue might be. I’ll get back to you as soon as I have an update
Hello @gregadev, sorry it took so long. Our devs are still investigating the issue but are suggesting performing a temporary downgrade so that you can use DevKinsta while they investigate this further. You can download the previous version from here
Thanks Alessandro! I don’t know what the issue is, but leaving Docker installed and using the previous version you provided worked wonderfully - started up and worked :-). I had tried to find older installers off the site before posting here, but couldn’t, so I’ll be sure to keep this download saved in case I need to reinstall.
While I’m sure there’s lots of possible reasons why the newest version didn’t work for me - the startup time for the installer made me wonder if the newest has a low tolerance for really slow internet speed? My internet is very slow (400kbps)? That’s the only added info I can offer though.
Happy to test the next version when it comes out to see if it works, - if that’s helpful, just message me.
Hi Greg,
our devs believe this might be due to the selection of the kernel type, but are still investigating the matter. I’ll try to keep in mind to update this thread to let you know when the next version is out, but if I fail to do so, please keep an eye on this thread, we usually post there all the updates to a minor version.
Glad the downgrade worked well
I’m glad to hear you were able to resolve the issue on your end. Thanks for sharing what worked for you so that other users in the forum may benefit from your findings.
Hello, I am a new user trying to install devKinsta desktop. When I try to start it up, I am also getting this error code. Anyone have a solution to this issue?
Hello @Vladimir_Milosavljev , thank you for responding. Yes, I am using the latest versions of each:
Docker 4.31.1
Kinsta 2.13.2
I am on Windows 11 Pro.
Anything else that could be going wrong?
Hi @Matthew_Lambert! Thank you for your reply, and thank you for sharing your system information!
I would like to review the main.log file from your DevKinsta installation to see what specifically about this path is causing the problem to occur. If you could please direct/private message me the main.log file that would help provide some more insight into the cause of this issue.
Just want to add to this Issue because i just spent 2hours finding out why devKinsta does not work with newer versions of Docker Desktop
according to the release notes from docker desktop they now no longer use ancillary docker-desktop-data WSL distribution
Since DevKinsta tries to access \wsl.localhost\docker-desktop-data it will not work with Docker Desktop version 4.30.0 or higher
I recommend downgrading to Docker Desktop 4.29.0 to circumvent this issue for now @Adrian_L would be great if you could pass this issue to the Dev Team so that they can create a solution for new Docker Desktop versions ^^