131–140 of 597 posts
If Docker wants to grow up, maybe they could start with replying to support tickets from paying customers. I have a 10 day old open ticket with no reply.
Hey sorry about that, can you send me the ticket details justin @ docker.com and I can look into it.
I've been using Minikube's docker-engine and haven't missed DockerForMac for some time now. Minikube sets up a Linux VM using MacOS Hypervisor. It even has a convenience command to configure docker-cli/docker-client. $ minikube docker-env export DOCKER_TLS_VERIFY="1" export DOCKER_HOST="tcp://192.168.65.11:2376" export DOCKER_CERT_PATH="/Users/wibble/.minikube/certs" export MINIKUBE_ACTIVE_DOCKERD="minikube" For corp…
Docker have never done the one obvious thing to monetise - an upsell and enterprise support for the engine. Trying to be a poor mans pivotal was a stupid strategy, and developer tools is awkward too. I’m convinced if they charged $10 per engine per month they would have kept all of the goodwill and momentum and been the next VMWare.
https://www.docker.com/blog/docker-enterprise-edition/
https://web.archive.org/web/20171118161452/https://www.docke...
So many people in this thread don’t understand how enterprise decisions get made. The business license costs $21/month, probably less in reality. Do you really think that businesses are going to jeopardize the workflows of their $250k/year assets over a very core piece of software for $250/year? Any alternative has switching costs and risks. Companies will just pay this. I see so many people saying “just do these 10…
USD 21 per user/month + bulk discount is nothing.
If companies want to roll their own they can, but most won't. Docker Desktop adds a lot of value if only by removing the hassle for quick os-agnostic development.
Earlier quoted context omitted.
It’s not the users who will be paying for it. Enterprises will bend over and take this 100% Good move by Docker, financially speaking. They have little to lose.
It's a short sited move that will kill D.Desktop. It's not that these large corps don't have the money for this, it's how money is allocated in companies. Instead, now all hobby projects in large corp get killed fast and early because the hobbyist knows their project is doomed if the company isn't going to go for a new bill. A whole bunch of scenarios die now.
Earlier quoted context omitted.
If you're doing $10M in ARR, how much engineering time are you going to spend to switch compared to paying Docker a few thousand dollars a month? Your spend on cloud and Slack (or other comms) is likely far higher. You're probably spending more on mobile/cell business service. "Docker attempting to monetize users of its product who can easily afford the cost." I mean, the terms seems reasonable, and wouldn't you rath…
My tiny part of a division of my last company made $40 million USD per year in revenue. We had ~40 employees. Getting the funding for using something like this came from a few levels up and would be in no way guaranteed.
Earlier quoted context omitted.
Docker Engine only runs on Linux. Docker for Mac/Windows sets up a Linux VM using macOS/Windows native virtualization via the open-source HyperKit/VPNKit abstractions maintained by Docker-the-Company and the community. That VM runs Docker Enginer (dockerd) and all interaction (docker CLI commands, shared volumes, networking, etc.) are proxied into that VM.
So unless I'm missing something important, why not just use docker engine directly on a wsl2 instance?
It'll be interesting to see how well this works out for Docker, I have a feeling they'll lose quite a bit of custom but convert some to this model. I'd guess a lot of people will just use Docker engine on a Linux VM with the CLI on Windows/Mac as that'll work just fine and is open source. This was kind of inevitable though, ultimately Docker had to find a revenue stream somewhere. Docker Hub must be massively expensi…
There has been a huge push in the community to switch away from docker anyway. The warning signs from the company have been there for awhile and there are several container engine's, systems, UI's and other management tools not built on docker. This will accelerate those programs
Earlier quoted context omitted.
You’re going to spend scarce engineering resources reimplementing a Docker for Mac alternative, then roll out your immature alternative to 50+ engineers, instead of paying a few hundred dollars a month for a good product and moving on? It seems to me you would be the one cutting off your nose to spite your face in this scenario.
The reason this move isn't popular is because it seemed like local docker development (for any size corporation) was always going to be free. If I personally had known this was in the cards I would have invested (time, money and effort) into alternatives earlier on. Instead they killed all the competition and are now demanding money. So yeah, this is the first move by Docker that has made me kind of mad at the compan…
Which alternatives did they kill? The Podman tool ecosystem is doing fine and is closing in on being a complete replacement, and Docker Swarm hasn't exactly killed k{number}s.
This appears to be cutting of their nose to spite their face. We have a team of 50+ engineers that all use Docker for Mac for daily development tasks, but I suspect that will no longer be true in a rather short amount of time. Frankly, I don’t really know if anybody actually uses the UI components for it outside of starting and stopping the engine and for basic configuration of the VM. Everything else that comes with…
For the Mac, just get Canonical’s Multipass ( http://multipass.run ) and do an apt-get to install Docker into a VM and use VS Code to “remote” to it. It will automatically install the Docker extension inside the Linux VM and you’re set. For Windows, use WSL2 and do the same. Both can mount “local” folders, although the setup is obviously different. You now have a better way to manage containers than ever before.
Multipass, Qemu, and Parallels can all provide a solid VM on Mac host. All you need after that is your dev environment VM guest image to deploy to the team.