DK0083 Unsupported docker volume path on WSL

DevKinsta Installation
1

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 :slight_smile:

Thanks!

2

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.

Regards,
Alessandro

3

Thanks :slight_smile: Dming my latest log. Unfortunately to me it doesn’t provide extra detail, hopefully it does to you, there’s atleast a stacktrace :slight_smile:

Thanks again!
Greg

4

Thank you for providing the log Greg, can you please also share your Windows, DevKinsta and Docker version?

5

Windows 10 pro - 10.0.19041.1806

And the latest of both Docker and DevKinsta:
DevKinsta 2.11.0.7043
Docker 4.20.1.0

7

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?

cert
cert444Ă—585 14 KB

8

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 :+1:

Regards,
Alessandro

9

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

Regards,
Alessandro

10

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.

Thanks!!
Greg

11

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 :tada:

All the best,
Alessandro

12

Hello there,

I had the same error message and I was able to get rid of the problem by simply creating the following directory:

\wsl.localhost\docker-desktop-data\data\docker\volumes\DevKinsta\

I got the idea from this post.

Maybe that will work for you as well!

Kind regards
Toby

13

Hey there @TantalizingToby! :wave:

Welcome to the Kinsta Community!

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.

Best,

14

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?

15

Hello @Matthew_Lambert :wave: Welcome to Kinsta Community :wave:

As per our guide, this happens due to the volume path being different/incorrect. Are you running the latest version of Kinsta and Docker?

16

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?

17

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.

You may find this file located at:

%userprofile%\AppData\Roaming\DevKinsta\logs

We look forward to hearing from you!

Best regards

19

Hey @Matthew_Lambert,

I reviewed your main.log file and found errors related to DK0083:

[2024-06-20 10:38:13.723] [error] watchDocker - Error: connect ENOENT //./pipe/docker_engine
[2024-06-20 10:38:14.608] [error] Error - DK0003: DOCKER_INSTALL_COMMON_ERROR: Docker isn't installed

Could you please try uninstalling Docker Desktop and then reinstalling it? But this time, do not select the “Use WSL 2 instead of Hyper-V” option.

image

Then try running Devkinsta again after.

Let me know how it goes. :pray:

20

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 :slight_smile:
@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 ^^

2 Likes
21

@Adrian_L That worked, thank you!

1 Like
23

@AlexG-LXmedia

We have shared your findings with our developer team. Thank you for posting it on our community forum.