21–30 of 367 posts
I've been using the following docker-machine plugin and found it to be great: https://github.com/zchee/docker-machine-driver-xhyve
This "review" is the technical equivalent of a YouTube unboxing video. Screenshot, screenshot, something I already knew from reading the press release, screenshot, platitude, one big technical error in the conclusion, and done. If it really worked (especially on Windows) Docker would post the binaries instead of treating this like Wonka Golden Tickets. Love Docker, am actually waiting to be approved so I can get to b…
That's why it's a beta.
This "review" is the technical equivalent of a YouTube unboxing video. Screenshot, screenshot, something I already knew from reading the press release, screenshot, platitude, one big technical error in the conclusion, and done. If it really worked (especially on Windows) Docker would post the binaries instead of treating this like Wonka Golden Tickets. Love Docker, am actually waiting to be approved so I can get to b…
Earlier quoted context omitted.
Running a VM means you have to allocate X amount of RAM regardless if how much is actually needed by the containerized processes.
You're still running a VM with Docker for Mac/Windows. It's just beautifully integrated and focused on the use case.
Earlier quoted context omitted.
Running a VM means you have to allocate X amount of RAM regardless if how much is actually needed by the containerized processes.
You're still running a VM with this, just via xhyve and the OSX Hypervisor framework, rather than via Virtualbox or VMWare. Which actually makes me wonder how they're managing memory for the VM hosting Docker here. Are they specifying a set fixed allocation? Is memory usage configurable somewhere?
This "review" is the technical equivalent of a YouTube unboxing video. Screenshot, screenshot, something I already knew from reading the press release, screenshot, platitude, one big technical error in the conclusion, and done. If it really worked (especially on Windows) Docker would post the binaries instead of treating this like Wonka Golden Tickets. Love Docker, am actually waiting to be approved so I can get to b…
The reason we are keeping the beta private is because we don't believe the quality is good enough yet to "open the floodgates". We are sending as many invites as the engineers are comfortable with - currently that's several thousands per day. As we hit more and more edge cases (performance, stability, support for unusual configurations...) we are expanding the pool as fast as we can.
Why do people value that so much? I really don't care if a tiny VMis running in the background. Also, running that VM gives me more confidence that it will also run on the production machine (since they use the same kernel and the same docker version). The only problem I had with docker was that I did not use to support shared volumes that are outside the home folder on Mac (I think they changed that now, but I'm not…
Running a VM means you have to allocate X amount of RAM regardless if how much is actually needed by the containerized processes.
This "review" is the technical equivalent of a YouTube unboxing video. Screenshot, screenshot, something I already knew from reading the press release, screenshot, platitude, one big technical error in the conclusion, and done. If it really worked (especially on Windows) Docker would post the binaries instead of treating this like Wonka Golden Tickets. Love Docker, am actually waiting to be approved so I can get to b…
I'm deep in the weeds with Docker, LXC, containers, hypervisors all the time. Content about those layers very few people care about... These are tools that are supposed to mostly stay out of the way after all.
Interest in Docker packaging their app as a nice mac app, and people understanding how the install process works is not a problem, it's a sign that these tools are finally becoming digestable by all.
What's the technical error?