Live data from Hacker News

Docker for Mac and Windows Is Now Generally Available and Ready for Production

blog.docker.com

131–140 of 169 posts

Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production

#131

Basically echoing senex's comment, but this announcement seems bizarre in light of https://forums.docker.com/t/file-access-in-mounted-volumes-e... . In particular, a Docker employee responds with a status update in https://forums.docker.com/t/file-access-in-mounted-volumes-e... , saying this isn't resolved for stable Docker for Mac. It's totally unusable for Rails development right now.

The 'convox start' dev environment enables Rails dev on Docker for Mac with a custom file sync strategy.

This is another case of simple solutions win... You can effectively rsync code changes without all the low level file system madness.

https://convox.com/blog/bidirectional-sync/

Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production

#132

My biggest issue with it is that there seems to be no easy way to provide more space to the VM docker runs inside. While it seems trivial it can be useful if you happen to have really large images (yes, for valid reasons). If you run too many containers you just run out of space.

I ran into this too when fooling around with SyntaxNet. It hink the default size of the VM is 16GB. I kept running out of swap space even after bumping the ram on the VM up to 16GB.

Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production

#133

Last time I checked it didn't support 32 bits but could be tested on Windows 7. Now I see it requires `Microsoft Windows 10 Professional or Enterprise 64-bit For previous versions get Docker Toolbox`.

Yeah, that's part of why this release baffles me. From 1.11 to 1.12 they dumped VirtualBox in favor of the latest version of Hyper-V which why it only supports Windows 10.

That's a pretty significant change in my mind but it didn't seem to extend their testing/validation timeline at all.

Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production

#135

Earlier quoted context omitted.

So why call it "production ready"?

I agree that it is confusing. Production ready in the sense that it is stable for the targeted use-case: local development environments. Not for "production". Damn now i'm confused...

GA would probably be a more appropriate description.

Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production

#137

If you have issues with the Docker for Mac on Sierra, turn off ntp: sudo launchctl unload /System/Library/LaunchDaemons/org.ntp.ntpd.plist If I see that "We are whaly happy to have you" welcome screen one more time though...

Can you actually live without NTP though? Isn't that a pretty critical service?

Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production

#138

Earlier quoted context omitted.

Docker 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.

I don't think so. That's what Jeffery Snover is working on in Server 2016 with Windows nano server. Unless something has changed since the last time I checked, The WindowsServerCore docker image was not generally available yet and requires server2016 (I think it was TP6 the last time I checked) Docker, to my knowledge, is still exclusively Linux flavors. (Though I'm happy to be corrected if someone knows more than me…

Docker images still aren't generally available, but you can now run Windows Container Images based on the NanoServer docker image (and WindowsServerCore image if you replace nanoserver with windowsservercore in their image URL in the docs below) on Windows 10 (insiders build)[0].

[0]: https://msdn.microsoft.com/en-us/virtualization/windowsconta...

Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production

#139
post #5
post #2

I've been tracking the beta for a while. I'm confused about this announcement. These issues still seem unresolved? (1) docker can peg the CPU until it's restarted https://forums.docker.com/t/com-docker-xhyve-and-com-docker-... (2) pinata was removed, so it can't be configured from CLI scripts https://forums.docker.com/t/pinata-missing-in-latest-mac-bet... (3) it's not possible to establish an ip-level route from the…

Sadly, the state of things, be it the Docker ecosystem or others, "ready for production" means something much different than it did years ago. For me, the definition of ready for production, Debian is a good example of the opposite end of Docker.

I think many view "ready for production" as a sign of what they do have in place is stable enough and support options are available so that it ticks all the CTO/CEO boxes in business plans.

Which basicly gets down to when your CTO/CEO or some manager comes in preaching docker - we should be doing that, why arn't we has one less argument to dismiss it now than before.

Yes many aspects need improving but case of what is there is deemed to of gained enough run-time in environments to be deemed stable enough to say, we can support this in production for off the shelf usage without you needing lots of grey-bearded wizards to glue it all in place and keep it that way.

Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production

#140

If you have issues with the Docker for Mac on Sierra, turn off ntp: sudo launchctl unload /System/Library/LaunchDaemons/org.ntp.ntpd.plist If I see that "We are whaly happy to have you" welcome screen one more time though...

Can you actually live without NTP though? Isn't that a pretty critical service?

One of the issues is that if your laptop goes to sleep your linux container becomes out of sync on the time. To fix this you have to restart docker.
Post reply on HN