| ▲ | gregoryl 8 hours ago |
| 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 8 hours ago | parent | next [-] |
| 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 8 hours ago | parent | next [-] | | 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. | | |
| ▲ | bonesss 7 hours ago | parent | next [-] | | Docker on Windows issues, back before WSL had matured enough, gave a pretty compelling argument for doing windows development on OSX inside a VM. | |
| ▲ | tuananh 8 hours ago | parent | prev [-] | | at work, i opted for remote development workspace because of this problem. Windows & Docker ain't meant to be together :( |
| |
| ▲ | throw20251220 8 hours ago | parent | prev [-] | | Windows is the problem, not Docker. Just try wsl2 and you’ll see… | | |
| ▲ | breakingcups 8 hours ago | parent [-] | | 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. |
|
|
|
| ▲ | FireBeyond 5 hours ago | parent | prev [-] |
| Yup. How many years did I go where the most frequently pushed button in the Docker Desktop UI was "reset my installation"? |
