Comment on Ditching Docker for Local Development
firelizzard@programming.dev 1 year agoMy point is that Docker Desktop is entirely optional. On Linux you can run Docker Engine natively, on Windows you can run it in WSL, and on macOS you can run it in a VM with Docker Engine, or via something like hyperkit and minikube. And Docker Engine (and the CLI) is FOSS.
LGUG2Z@lemmy.world 1 year ago
I understood your point, and while there are situations where it can be optional, in a context and scale of hundreds of developers, who mostly don’t have any real
dockerknowledge, and who work almost exclusively on macOS, let alone enough to set up and maintain alternatives to Docker Desktop, the only practical option becomes to pay the licensing fees to enable the path of least resistance.mundane@feddit.nu 1 year ago
We are over 1000 developers and use
docker cejust fine. We use a self hosted repository for our images. IT is configuring new computers to use this internal docker repository default. So new employees don’t even have to know about it to do their firstdocker build.We all use Linux on our workstations and laptops. That might make it easier.
LGUG2Z@lemmy.world 1 year ago
You are living my dream!
I think this is the key piece; the experience of Docker on Linux and on macOS is just so wildly difference when it comes to performance, reliability and stability.
Von_Broheim@programming.dev 1 year ago
Op comes off a bit, uninformed. E.g. I use docker engine and docker compose inside WSL2 on windows and performance is fine, then I use Intellij to manage images/containers, the service tab handles the basics. If I need to do anything very involved I use the cli.
Docker is fine, the docker desktop panic really only revealed who never took the time to learn how to use docker and what the alternative UIs are.