DK0083 Unsupported docker volume path on WSL

Thanks for saving me those 2 hours:D

Hi
Please add this solution to the troubleshooting docs.

Hey @genep! :wave: Welcome to the Kinsta Community! Your request has been passed along to our content team. Hopefully, we can get it added to the page soon. Thanks a bunch!

So, itā€™s been over five months since Docker removed the docker-desktop-data WSL distribution. I see only two options for using DevKinsta, both of which are kinda contrary to what Docker says to do.

  1. Downgrade Docker
  2. Use Hyper-V which Docker documentation says has performance issues, with strong recommendations that WSL2 be used.

Sorry, I am using Docker for other purposes as well, and I am not interested in either downgrading the version, or reinstalling to use a lower-performance alternative.

I note that there is no support offered for DevKinsta other than this community forum.

Is DevKinsta under active development?

I wanted to use it because attempting a WordPress automatic upgrade corrupted the entire site, so I need to debug and fix the problem offline and re-upload to live. But if DevKinsta is no longer a viable tool, Iā€™ll have to use a staging area instead.

Iā€™ll uninstall it for the moment, and wait for the dev team to announce support for Docker 4.30+ and Windows 11.

Hi @IainMcc :wave:

Welcome to the Kinsta Community!

Iā€™m sorry to hear that the two options you mentioned donā€™t work for you. Unfortunately, development for DevKinsta is currently on pause. This means that while our developer team is working to keep DevKinsta SOC-2 compliant and will continue to resolve any critical security bugs, further app improvements are on hold until further notice. Having said that, there is no ETA on when Docker 4.30+ with WSL will be fully compatible with our DevKinsta app.

Hi @Adrian_L

Thanks very much for the rapid and direct reply! I really appreciate it, in an era when so many support people mumble and fail to read the question, or let AI ramble incoherently on their behalf about ā€œsolutionsā€ that have nothing to do with the problem.

I figured that DevKinsta was in maintenance mode or even heading for EOL, when I dug in after posting. The absence of Windows 11 from the docs 3 years after release, and the explicit revocation of the certs in the installer exe were pretty big flags.

Ok, Iā€™ll see if I can create a PHP/nginx/MySQL Docker stack to somewhat imitate your hosting env and snag the site via myPhpAdmin and SFTP, and try to solve the WP-update-corrupts-the-site issue I have.

Thanks again for the good response!