Live data from Hacker News

The easiest way to use Docker on your Mac

kitematic.com

51–60 of 62 posts

Re: The easiest way to use Docker on your Mac

#51
post #45

Earlier quoted context omitted.

Why would I restrict myself to Linux if the tooling I prefer is only available on Mac? I guess if my entire workflow was terminal based then Linux would make sense but I'm more productive with Intellij, Kaleidoscope, Tower Git, iTerm, and my iTunes library of music. A vm running centOs and using docker let's me use my favorite tools and still leverage Linux as a deployment environment, how does that not make sense?

Then run Mac in a VM on Linux. IntelliJ, Git, and music-listening developr here. On GNU/Linux. It does not make sense because you stop yourself from knowin the inner workings of what you are targeting in your development efforts - eat your own poison so to say - CentOS - run CentOS. How hard can that be?

A. running Mac in a VM on Linux is illegal

B. Tower, Kaleidoscope. iTerm, and XCode are all Mac only

C. How in Earth do you draw the conclusion that I've stopped myself from knowing anything? I am running CentOS, in the VM. I'm extremely familiar with the inner workings of Linux. If I'm running in a VM or as the main OS has no bearing on how much I know about my deployment target. It's still the same steps to setup a deployment target VM or on my actual laptop. In fact in the case of AWS you could argue that a VM is much closer to my deployment prod servers than laptop hardware would be.

Re: The easiest way to use Docker on your Mac

#52
post #45

Earlier quoted context omitted.

Why would I restrict myself to Linux if the tooling I prefer is only available on Mac? I guess if my entire workflow was terminal based then Linux would make sense but I'm more productive with Intellij, Kaleidoscope, Tower Git, iTerm, and my iTunes library of music. A vm running centOs and using docker let's me use my favorite tools and still leverage Linux as a deployment environment, how does that not make sense?

Then run Mac in a VM on Linux. IntelliJ, Git, and music-listening developr here. On GNU/Linux. It does not make sense because you stop yourself from knowin the inner workings of what you are targeting in your development efforts - eat your own poison so to say - CentOS - run CentOS. How hard can that be?

d00d, I was running Slackware on 0.9 kernels in a business environment when half of HN was trying to figure out how to remove their own diapers. I know Linux quite well enough. I use OSX for my desktop because it's the least awful desktop experience. If I'm coding, it's mostly command line tools, and there is no technical difference between running bash on a Linux desktop and running bash via vagrant ssh on my Mac.

What is different is that my Vagrant instance configuration is 100% programmable and repeatable. There are no surprises. There are no differences between development environment and production environment, in terms of installed software or patches. I'm not hacking away on some snowflake environment and then trying to grok wtf is wrong with my code when it gets deployed to the next environment.

But the original post isn't about this, even... it's about Docker. Dockerized applications are 100% binary-level compatible from environment to environment. I can easily localize from dev to test to production using environment variables - a proper 12 Factor App. Why would I not want to do this in my development environment? Why would I go back to some crude 2003-vintage development model that I know good and well is going to break things later?

And it gets worse. Lots of us have to deal with heterogeneous environments. What if I'm building for both CentOS and Debian? With something that's OS patch-sensitive? Do I test in production to see if it survives? No, I use Vagrant to test every platform I want, and Docker to guarantee consistency whenever I can.

How hard can it be? It can be much, much harder than a proper, modern Vagrant/Docker environment.

Re: The easiest way to use Docker on your Mac

#53

Earlier quoted context omitted.

That's what VMs are for, not containers.

Some of us that use Mac applications don't like to break the law and run OS X in a VM when that is not allowed by the license agreement. You can run it in a VM if your host OS is OS X, but not if it is Linux. I use OS X with VMware fusion and am very happy with it. I can run the commercial apps I need plus Linux, Windows, docker...

I meant use Linux (or Windows or whatever) in a VM on top of OS X - Containers won't help you here.

Re: The easiest way to use Docker on your Mac

#55
post #9

Previous discussion: https://news.ycombinator.com/item?id=8246240

What's your motivation for pointing this out? Just curious. Do you want people to go talk about it on the other thread instead of this one? Or, are you trying to keep duplicate posts or comments off of HN? Or, something else?

When a story has had significant attention in the last year, it counts as a duplicate (otherwise a small number of reposts is OK; see https://news.ycombinator.com/newsfaq.html). It's helpful when users point out the ones we've missed.

Re: The easiest way to use Docker on your Mac

#57
post #28

Earlier quoted context omitted.

> people who want to use Linux-technology, like Docker What defines Docker as 'linux technology'? It has an execution driver API specifically designed to support multiple backends, e.g. BSD jails. I wouldn't use the fact that they started with linux support to declare them 'linux technology', whatever that means.

Docker is a "Linux Technology" because it is based on a particular feature of the Linux kernel ( http://en.m.wikipedia.org/wiki/LXC ) and you need to run a Linux kernel (either in a vm or on bare metal) to run them.

LXC isn't a 'feature of the linux kernel' it's a user land library that uses a set of linux kernel features (e.g. cgroups, namespaces, etc) to expose an api for creating system containers. LXC isn't part of the kernel.

Docker's default driver has been libcontainer, not LXC, for almost a year. libcontainer implements Docker's execution driver api and works with the various linux kernel features needed to implement containers directly, it doesn't use LXC at all.

Docker isn't based on nor reliant on LXC in any way anymore and with the execution driver api is designed to run on various platforms.

Re: The easiest way to use Docker on your Mac

#58
post #57

Earlier quoted context omitted.

Docker is a "Linux Technology" because it is based on a particular feature of the Linux kernel ( http://en.m.wikipedia.org/wiki/LXC ) and you need to run a Linux kernel (either in a vm or on bare metal) to run them.

LXC isn't a 'feature of the linux kernel' it's a user land library that uses a set of linux kernel features (e.g. cgroups, namespaces, etc) to expose an api for creating system containers. LXC isn't part of the kernel. Docker's default driver has been libcontainer, not LXC, for almost a year. libcontainer implements Docker's execution driver api and works with the various linux kernel features needed to implement con…

I stand corrected

Re: The easiest way to use Docker on your Mac

#59
post #9

Previous discussion: https://news.ycombinator.com/item?id=8246240

What's your motivation for pointing this out? Just curious. Do you want people to go talk about it on the other thread instead of this one? Or, are you trying to keep duplicate posts or comments off of HN? Or, something else?

Some of the points raised in this thread were answered in the previous thread.

Re: The easiest way to use Docker on your Mac

#60
post #45

Earlier quoted context omitted.

Then run Mac in a VM on Linux. IntelliJ, Git, and music-listening developr here. On GNU/Linux. It does not make sense because you stop yourself from knowin the inner workings of what you are targeting in your development efforts - eat your own poison so to say - CentOS - run CentOS. How hard can that be?

A. running Mac in a VM on Linux is illegal B. Tower, Kaleidoscope. iTerm, and XCode are all Mac only C. How in Earth do you draw the conclusion that I've stopped myself from knowing anything? I am running CentOS, in the VM. I'm extremely familiar with the inner workings of Linux. If I'm running in a VM or as the main OS has no bearing on how much I know about my deployment target. It's still the same steps to setup a…

> A. running Mac in a VM on Linux is illegal

According to who? Has this been tried in a court of law?

If not, it's legal until proven otherwise. This BS by Mac-appologetics has got to stop.

Post reply on HN