I have no problems building containers on macOS. Can you elaborate?

linkmotif · on Jan 5, 2019

Building containers requires Linux, so I need to run a VM or build on another box/the cloud.

timrichard · on Jan 5, 2019

If you are running Docker for Mac, it should work out of the box :

Docker for Mac uses HyperKit instead of Virtual Box. Hyperkit is a lightweight macOS virtualization solution built on top of Hypervisor.framework in macOS 10.10 Yosemite and higher.

From https://docs.docker.com/docker-for-mac/docker-toolbox/

I build Linux target images on either my Mac or a handy EC2 instance for deployment to AWS using their ECR as a repository. No difference.

perfmode · on Jan 5, 2019

This is somewhat outdated.

Docker for Mac uses a relatively lightweight and largely-invisible virtualization layer now.

linkmotif · on Jan 5, 2019

Thanks. I didn’t know the visualization system changed. I will check this out again.

NickBusey · on Jan 5, 2019

I built a container a few minutes ago on macOS, not sure why you believe this to be the case.

linkmotif · on Jan 5, 2019

Docker containers/lxc require Linux. They are a Linux technology.

aaachilless · on Jan 5, 2019

This is technically true but in practice Docker for Mac hides this from you and does not require a prohibitive amount of memory. 99% of the developers at my company have 16gb MBPs and we all build multiple Docker containers daily.

linkmotif · on Jan 5, 2019

Thanks. I didn’t know the visualization system changed. I will check this out again.

chupasaurus · on Jan 6, 2019

As weird as it sounds, Microsoft had implemented the full namespaces stack in Server 2016 (unavailable in Win10 as the base for native containers is Server where kernel differs a bit), which Docker supports (and k8s in alpha/early beta).

Docker switched from LXC to containerd in 2016.

linkmotif · on Jan 8, 2019

That is very weird. Wow. Thanks for letting me know. I guess it's not a Linux technology then.