5 ms·

For a while, Docker seemed to focus on developer experience. ahh yes, docker desktop, where the error messages are "something went wrong", and the primary debu

For a while, Docker seemed to focus on developer experience. ahh yes, docker desktop, where the error messages are "something went wrong", and the primary debugging step is to wipe it, uninstall, and reinstall.

reedf1 9mo ago
It is honestly incredible that such an important part of the Windows dev process is nearly unusable. It is easily the most fickle and opaque bit of software that I am required to depend upon.
- hu3 9mo ago
  Yep. I used to have a ton of problems with Docker in Windows. It has been a year without problems since I enabled WSL2 engine for Docker. Honestly they should make the WSL2 Docker engine mandatory because otherwise things barely work.
  - tuananh 9mo ago
    at work, i opted for remote development workspace because of this problem. Windows & Docker ain't meant to be together :(
  - bonesss 9mo ago
    Docker on Windows issues, back before WSL had matured enough, gave a pretty compelling argument for doing windows development on OSX inside a VM.
- throw20251220 9mo ago
  Windows is the problem, not Docker. Just try wsl2 and you’ll see…
  - breakingcups 9mo ago
    That's a very naive take. The issue is Docker Desktop, a buggy mess. I have plenty of well-functioning, complex Windows applications with detailed troubleshooting utilities.
    - throw20251220 8mo ago
      Yeah, it's all naive when it doesn't work for you. It's naive using Windows.
FireBeyond 9mo ago
Yup. How many years did I go where the most frequently pushed button in the Docker Desktop UI was "reset my installation"?