3 ms·

Why would one want OSX support for docker anyway? Does anyone actually deploy OSX in a server environment? This is not a criticism, just a curiosity.

kennu 12y ago
Because in the typical Docker workflow, developers (who often use OS X) build container images on their computers. Anyway, boot2docker works really well nowadays. Even individual port forwarding has been eliminated by using a virtual IP address where all exposed ports are available.
- vectorpush 12y ago
  Ah. I just assumed that OSX devops tested their work on a linux VM, I didn't realize it was common to build on OSX then deploy to linux production, I'd have guessed that would be pretty error prone.
andrewflnr 12y ago
Servers aren't the only thing Docker is useful for. I made the plunge to isolate a GUI app and its daemons from my desktop (krita was trying to run KDE daemons on my xfce system, grr). Something like that might be useful. Another possibility is nice development servers, so you can run something in close to the same environment on your work computer as your servers.
- vectorpush 12y ago
  Good point, I suppose docker is pretty ideal for packaging up a system configuration of any type.
magnetikonline 12y ago
It's very handy for development instances of your apps/services too. Often nicer/faster than using Vagrant if that's your bag. Something I plugged together recently - a W3C HTML5 validator instance in a Docker container: https://github.com/magnetikonline/dockerhtml5validator https://github.com/magnetikonline/dockerhtml5validator proving to be really useful vs. my old method of spinning this all up in a VirtualBox instance.
- vectorpush 12y ago
  That makes sense. It appears Docker is in fact especially useful for OSX because it can replace a VM with something more svelte and seamless.
wiml 12y ago
In the past OSX has actually been a pretty decent server OS. I wouldn't recommend it for that today, but there are still plenty of reasons someone might want it (legacy systems, developer familiarity with OSX from desktop use, some Apple technologies that are useful even outside a GUI, and so on).

kennu 12y ago

Because in the typical Docker workflow, developers (who often use OS X) build container images on their computers. Anyway, boot2docker works really well nowadays. Even individual port forwarding has been eliminated by using a virtual IP address where all exposed ports are available.

vectorpush 12y ago
Ah. I just assumed that OSX devops tested their work on a linux VM, I didn't realize it was common to build on OSX then deploy to linux production, I'd have guessed that would be pretty error prone.

andrewflnr 12y ago

Servers aren't the only thing Docker is useful for. I made the plunge to isolate a GUI app and its daemons from my desktop (krita was trying to run KDE daemons on my xfce system, grr). Something like that might be useful. Another possibility is nice development servers, so you can run something in close to the same environment on your work computer as your servers.

vectorpush 12y ago
Good point, I suppose docker is pretty ideal for packaging up a system configuration of any type.

magnetikonline 12y ago

It's very handy for development instances of your apps/services too. Often nicer/faster than using Vagrant if that's your bag. Something I plugged together recently - a W3C HTML5 validator instance in a Docker container: https://github.com/magnetikonline/dockerhtml5validator https://github.com/magnetikonline/dockerhtml5validator proving to be really useful vs. my old method of spinning this all up in a VirtualBox instance.

vectorpush 12y ago
That makes sense. It appears Docker is in fact especially useful for OSX because it can replace a VM with something more svelte and seamless.

wiml 12y ago

In the past OSX has actually been a pretty decent server OS. I wouldn't recommend it for that today, but there are still plenty of reasons someone might want it (legacy systems, developer familiarity with OSX from desktop use, some Apple technologies that are useful even outside a GUI, and so on).