5 ms·
I think by 'production', they mean 'ready for general use on developer laptops'. No one in their right mind is deploying actual production software on Docker, o
by rhinoceraptor 10y ago
I think by 'production', they mean 'ready for general use on developer laptops'. No one in their right mind is deploying actual production software on Docker, on OS X/Windows.
I've been using it on my laptop daily for a month or two now, and it's been great. Certainly much better than the old Virtualbox setup.
- mherrmann 10y agoI'm still using VirtualBox. Could you elaborate why Docker is better?
- numbsafari 10y agoLeaving containers vs VMs aside, docker for Mac leverages a custom hypervisor rather than VirtualBox. My overall experience with it is that it is more performant (generally), plays better with the system clock and power management, and is otherwise less cumbersome than VirtualBox. They are just getting started, but getting rid of VirtualBox is the big winner for me.
- rhinoceraptor 10y agoWhen I used VirtualBox for Docker (using Docker machine/toolbox), I would run out of VM space, have to start and stop the VM, and it was just clunky all around. Docker.app has a very nice tray menu, I don't know or care anything about the VM it's running on, and generally is just better integrated to OS X. For instance, when I run a container, the port mapping will be on localhost rather than on some internal IP that I would always forget.
- cptskippy 10y agoI don't think he was comparing Docker to VirtualBox. In Docker 1.11 they used VirtualBox to host a Linux Docker Image to run containers. In 1.12 they switched to Microsoft's Hyper-V.
- statictype 10y ago>No one in their right mind is deploying actual production software on Docker, on OS X/Windows. Since the whole point of Docker would be to deploy these in production and not just for development, I don't see how the term 'ready for production' can be used. Isn't this just a beta?
- sudhirj 10y agoI doubt the problems mentioned happen on Linux or CoreOS, which is likely what a production environment will run on.
- tazjin 10y ago> Linux or CoreOS Well, now I'm confused
- sudhirj 10y agoSorry, CoreOS is Linux as well, but in my mind it's enough of a hyper-specialised immutable auto-updatable container-specific version of Linux that it warrants a separate category when talking about Docker.
- statictype 10y agoDocker for Windows is to isolate Windows software. It's not a tool to test Linux containers on Windows. The deployment target for Docker containers for Windows will be a Windows OS.
- bboreham 10y agoSadly, no, they're using the name "Docker for Windows" to refer to the Docker-on-Linux-in-a-VM-on-Windows version. Real native Windows containers and a Docker shim to manage them are coming: [1] but not released yet. [1] https://msdn.microsoft.com/en-us/virtualization/windowscontainers/quick_start/quick_start https://msdn.microsoft.com/en-us/virtualization/windowsconta...
- 10y ago
- kakarot 10y agoThe fact that I can have Bash up and running in any distro I feel like within minutes blows my friggin mind. Docker is the stuff of the future. We were considering moving our development environment to Docker for some Fun, but we're still holding off until it is more stable and speedy.
- kccqzy 10y agoOn the other hand I find my old setup with VMware much more reliable and performant. And I can continue to use the great tools to manage the VM instead of being limited to what docker provides. Some advanced network configuration is simply impossible in docker's VM.
- JustSomeNobody 10y agoI'm pretty sure they don't mean that, or they would have said that it was still in Beta.