201–210 of 250 posts
Tried to sign up, but the enroll form at https://beta.docker.com/form is blank for me - it just says "Great! We just need a little more info:" but has no forms.
The 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…
I've had similar experiences as well as times where xhyve made it so my laptop could not come out of sleep. xhyve is wonderful but still needs some work and it seems like the main dev isn't interested in continuing work on it at this point[1]. Hopefully Docker's usage will spur more work on xhyve. [1] Last commit on xhyve is December 28th, 2015 https://github.com/mist64/xhyve/commits/master
The 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…
I think this was related with a kernel bug which was fixed with the latest release from OSX (released yesterday). I personally discovered this bug while using dlite, which uses xhyve behind the scenes.
Earlier 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…
Yes, any new virtualization projects should strongly consider using it, but that doesn't mean any issues with projects with have a massive investment in tooling and ecosystem should be considered deprecated and dead just because of this.
Earlier quoted context omitted.
What is the filesystem engine? Is it just something fancy on top of NFS, or something completely new?
It's something new.
Earlier quoted context omitted.
They have build args for this in now. Thus, you'd do something like: docker build --build-arg OAUTH_TOKEN=blah -t example .
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…
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.
Why does signing up for the beta require agreeing to a non-disclosure agreement?
Interesting to see that at least one of the Mirage unikernel hackers (avsm) has been working on this. https://news.ycombinator.com/item?id=11352594 I imagine a lot of this work will also be useful for developers wanting to test all sorts of unikernels on their Mac and Windows machines.