Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

blog.docker.com

Post reply on HN
Print view View original

21–30 of 169 posts

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

#21

Post by mrmondo »

jmspring wrote: post #5
senex wrote: 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'm not completely disagreeing with you but Debian in recent years has taken massive steps backwards as far as production stability. Jessie for example did not ship with SELinux enabled which was a key deliverable for Jessie to be classed as stable / ready for production, what's worse is it doesn't ship with the require SELinux policies - again another requirement before it was to be marked as stable, it's filled with out of date packages (you know they're old when they're behind RHEL/CentOS!) and they settled on probably the worst 3.x kernel they could have.

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

#22

Post by mrmondo »

slantedview wrote: post #6

I need nested virtualization as well. I don't know if this is possible with the hypervisor being used, but it's hugely important for me.

Absolutely, I too would really like this, especially if you could easily do PCIe / Thunderbolt passthrough for GPUs.

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

#23

Post by qubit23 »

senex wrote: 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…

This is another issue that's been preventing my adoption of Docker for Mac: https://forums.docker.com/t/docker-pull-not-using-correct-dn.... The fact that DNS resolution over a VPN still doesn't work correctly makes me wonder how production-worthy this release is. It's a pretty common thing people want to do in my experience.

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

#24

Post by bashed »

mintplant wrote: post #20
slantedview wrote: post #6

I need nested virtualization as well. I don't know if this is possible with the hypervisor being used, but it's hugely important for me.

Curious, can you share what you need it for?

Looks like you need nested virtualization for running windows xp apps within the new newer windows systems.

I'm also curious about other uses for it. Why is it a must have when you could technically just use a virtual windows xp system. I guess running a legacy application in a more secure and newer OS?

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

#25

Post by Axsuul »

jaequery wrote: post #19

Anyone know if the volume ozone performance have been improved to at least the level of nfs method? This is what keeps me away from using the docket for Mac and just sticking to dinghy until this is fixed

Would like to know this as well. Docker for Mac performance is still horrible.

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

#26

Post by colordrops »

jonesetc wrote: post #14
senex wrote: 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…

I have also yet to see a reasonable solution for connecting out of a container back to the host with Docker.app. On linux and OSX with docker-machine this is easy with: docker run --add-host host:ip.for.docker.interface foo But there is no equivalent to the docker0 interface or the vboxnet interface for Docker.app. EDIT: I don't use this for any production environments, but it is very useful for debugging and testing…

What about getting the gateway address from inside the container:

    HOST_IP=$(/sbin/ip route | awk '/default/ { print $3 }')

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

#27

Post by tszming »

jmspring wrote: post #5
senex wrote: 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.

>> Debian is a good example of the opposite end of Docker.

It is not fair to compare Docker with Debian. Docker Inc (who backed Docker) is a for-profit corporation and is backed by investors. It is understandable why they need to push their products into production the soonest time possible.

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

#29

Post by vbernat »

mrmondo wrote: post #21
jmspring wrote: post #5

Earlier quoted context omitted.

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'm not completely disagreeing with you but Debian in recent years has taken massive steps backwards as far as production stability. Jessie for example did not ship with SELinux enabled which was a key deliverable for Jessie to be classed as stable / ready for production, what's worse is it doesn't ship with the require SELinux policies - again another requirement before it was to be marked as stable, it's filled wit…

Unfortunately, nobody has stepped for SELinux maintainance. If this is important for you, you should help to maintain those policies.

All your remaining points are vague at best.

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

#30

Post by turnip1979 »

qubit23 wrote: post #23
senex wrote: 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…

This is another issue that's been preventing my adoption of Docker for Mac: https://forums.docker.com/t/docker-pull-not-using-correct-dn... . The fact that DNS resolution over a VPN still doesn't work correctly makes me wonder how production-worthy this release is. It's a pretty common thing people want to do in my experience.

Sigh .. I need to disconnect from VPN to use it. I think u can reconnect after creation.
Post reply on HN