I couldn't sign up using Firefox on Windows. I'd enter a username, email and password then the form would just go blank on submission.
I should note that it worked fine on Chrome.
Docker for Mac and Windows Beta
211–220 of 250 posts
Re: Docker for Mac and Windows Beta
#212Earlier quoted context omitted.
It's something new.
Is it related to the work started by Brad Fitzpatrick a few months ago with the goal of implementing client-server gateway between the host and the guest filesystem using FUSE?
The new daemon (dubbed osxfs) is FUSE-based at the moment, but also provides a semantic translation layer between OSX filesystem calls and Linux kernel events. The FUSE layer can be removed in the future in favour of a direct kernel module with this architecture, if it ends up being a bottleneck (its fine right now though)
Re: Docker for Mac and Windows Beta
#213Re: Docker for Mac and Windows Beta
#214Earlier quoted context omitted.
Who downvoted this? This is a real experience report, expressing valid concerns, citing an issue tracker for more information. Is this type of comment discouraged on HN? If so, why?
I didn't downvote, but I'd imagine people don't agree with his criticism of stability because it conflicts with VirtualBox. VirtualBox has to invasively modify your system configuration in order to accomplish virtualization. On the other hand, xhyve is using an OS X sanctioned virtualization technique (hypervisor.framework) that works within sandboxed apps. This is the route going forward that Apple advocates for vir…
> people don't agree with his criticism of stability because it conflicts with VirtualBox
Folks are welcome to disagree, but Docker has a history of shipping software which uses a 3rd party feature which breaks, to which they frequently responded "not our code, talk to someone else": btrfs instability, corrupted volumes due to conflicting devmapper libraries, iptables dropping routes, upgrades orphaning containers, etc.
I realize they don't have control over all of the variables, but constantly releasing unstable 3rd party features was not the greatest behavior, and the "Not My Problem" response to issues is aggravating.
All that said, since they're working against their own fork of xhyve, it is a sign that these kinds of issues will be addressed by the Docker team this time, which is a good thing.
Re: Docker for Mac and Windows Beta
#215The last time I used xhyve, it kernel panic'ed my mac. Researching this on the xhyve github account [1] showed that it was determined that it's due to a bug with Virtualbox. That is, if you've started a virtual machine since your last reboot with Virtualbox, subsequent starts of xhyve panic. So, buyer beware, especially if said buyer also uses tools like Vagrant. [1] https://github.com/mist64/xhyve/issues/5 I've said…
Thanks, this is useful feedback. There are various workarounds in the app to prevent such things, but the purpose of the beta program is to ensure that we catch all the weird permutations that happen when using hardware virt (e.g. the Android emulator). If anyone sees any host panics ever, we'd like to know about it (beta-feedback@docker.com) and fix it in Docker for Mac and Windows. Fixes range from hypervisor patch…
It's good to see that you folks are taking ownership of such a critical portion of this infrastructure. I hope you understand why people can get worried when Docker has a history of integrating with third party software, and responding "Not Our Problem" when problems arise.
Re: Docker for Mac and Windows Beta
#216Earlier quoted context omitted.
I think you just proved my point. We're all of us running around with our pants down because we think Docker is taking care of this stuff but it's merely a bunch of features that look like they should be fit for that purpose but aren't. And this is why I am stuck with a separate build and package phase, because I have to have that separation between the data available at build time and what ends up shipped, but even…
I don't see how that's a compelling argument at all. All that's keeping you from committing your credentials is a .gitignore file. They have the file, it works reliably, don't worry about it.
[deleted]
Re: Docker for Mac and Windows Beta
#217Not-news (support for two new hypervisors implemented, already dodgy package altered) voted up to 718 points. God you people are sheep. I guess what we take from this is docker is getting desperate for newslines.
Re: Docker for Mac and Windows Beta
#218Earlier quoted context omitted.
I think you just proved my point. We're all of us running around with our pants down because we think Docker is taking care of this stuff but it's merely a bunch of features that look like they should be fit for that purpose but aren't. And this is why I am stuck with a separate build and package phase, because I have to have that separation between the data available at build time and what ends up shipped, but even…
I don't see how that's a compelling argument at all. All that's keeping you from committing your credentials is a .gitignore file. They have the file, it works reliably, don't worry about it.
You should know there was a pretty big bug fixed in .dockerignore in just the last release. [edit] That bug was in the logic for white-listing files, which is generally the safest way to keep from accidentally publishing things (that is, if it works).
And it's possible a similar issue still exists in docker-compose but it's still open.
.gitignore keeps me from checking my files into git, but it doesn't keep me from publishing them in a docker image. So now I have a second way to screw up.
Re: Docker for Mac and Windows Beta
#219The last time I used xhyve, it kernel panic'ed my mac. Researching this on the xhyve github account [1] showed that it was determined that it's due to a bug with Virtualbox. That is, if you've started a virtual machine since your last reboot with Virtualbox, subsequent starts of xhyve panic. So, buyer beware, especially if said buyer also uses tools like Vagrant. [1] https://github.com/mist64/xhyve/issues/5 I've said…
Updating to a newer version of VirtualBox solved that issue.
Re: Docker for Mac and Windows Beta
#220This is v.cool, although for the Windows version it'd be great if it became possible to swap out the virtualization back-end so it's not tied to Hyper-V. At the moment VMWare Workstation users will be a bit left out as Windows doesn't like having two hypervisors installed on the same system...
This is the issue I have too, if I want to use the new docker windows, I'd have to move my virtualbox linux vm to hyper-v and stop using vagrant.