shykes

44 ms·

481.
by shykes 11y ago
Hi all. We know the experience of using Docker on OSX is not perfect today. The default virtualbox configuration for file sharing is slow and buggy. You need to use 3 different CLIs (`docker`, `docker-machine`, `docker-compose`) which are n
482.
by shykes 11y ago
Docker machine creates and manages VMs, then you can run any number of containers on those VMs.
483.
by shykes 11y ago
It will happen :) Xhyve is pretty new (and only works on pretty recent OSX installs), but we are also feeling the pain of the default vbox install and really want to fix it.
484.
by shykes 11y ago
You are correct. GAE classic is not a good example since it uses language-specific sandboxing. Hopefully you'll agree that my overall point still stands: when configured and managed properly there is consensus that you can run certain
485.
by shykes 11y ago
You are right, they are not mutually exclusive, and we are working on both in parallel. We are working on specifying a standardized way to 1) hash a container in its runnable form, and 2) attach arbitrary signatures constructed from that ha
486.
by shykes 11y ago
Just to clarify: user namespaces will be a great additional layer in security, but they are still a relatively new feature, with very little actual use in production. You can already use them in runC [1] (Docker's low-level container r
487.
by shykes 11y ago
Another important point: running untrusted code in Linux containers is not considered safe in all configurations, but it is safe in some configurations. So if you know what you're doing, you can already configure Docker to run untr
488.
Roshi: large-scale CRDT set implementation for timestamped events(github.com)
26 points by shykes 11y ago|4 comments
489.
by shykes 11y ago
First off, I would definitely listen to your doctor when they strongly discourage something. In our case for example, folic acid was also a no-no. Here's a book that was very useful to us: "The Cancer-fighting kitchen" by Reb
490.
by shykes 11y ago
Hi Mehr, I registered last year after someone very close to me was diagnosed and treated - now in remission. I added myself to your list, I hope it will help. Here are a few things I learned after being closely involved with someone else&#x
491.
by shykes 11y ago
Those are the same thing :) Everything Docker builds is open-source and built together with the community. The exception is Docker Hub, our cloud service which is built by a separate team. So, Jess is a core maintainer of Docker who happens
492.
by shykes 11y ago
Obviously it's hard to know for sure. But most likely this is the work of "harassment hobbyists" who have no particular agenda other than the moronic thrill of messing with people from the safety of their keyboards. There is
493.
by shykes 11y ago
Noted, thank you!
494.
by shykes 11y ago
Hi, I'm a colleague of Jess. I entirely agree with everything you said about the industry as a whole. My thoughts in this thread: https://news.ycombinator.com/item?id=9836573 But you should know that her colleagues (me
495.
by shykes 11y ago
I meant to upvote you but accidentally downvoted,sorry! I strongly agree that this is a gendered phenomenon.
496.
by shykes 11y ago
I am a colleague of Jess, and have witnessed her dealing with this ordeal. She is a badass and doesn't need anyone to speak on her behalf. But some aspects of her experience are relevant to all of us and we have to talk about it. 1. If
497.
by shykes 11y ago
I just look at the "pulse" section on github. We also have an internal tool which we query for more complex queries (contributor retention across projects, things like that).
498.
by shykes 11y ago
Hi, having started Docker I am of course biased, but I thought I'd bring some data to this conversation. Last 30 days on Docker Compose: 45 PRs merged from 26 people Full time Docker employees on Compose: 1 Last 30 days on Docker Machi
499.
by shykes 11y ago
If you're interested in Docker's opinion on this topic, I recommend that you watch today's keynote. That's where we introduced runC and where we explain why. http://www.ustream.tv/recorded/64499822
500.
by shykes 11y ago
Obviously I am biased (working on Docker), but I thought I would mention a few facts. - Today AWS announced they would support Docker Swarm and Compose natively on ECS. - Last month devops.com surveyed development and ops teams about their
501.
by shykes 11y ago
That's correct, layers are not part of the spec. It's the caller's responsibility to setup the container bundle (manifest + one or more rootfs directories) so that runC can load it. How that is done is not the concern of ru
502.
by shykes 11y ago
To clarify, the Open Container Project was started by Docker with the help of the Linux Foundation. Then other vendors were invited (including AppC maintainers). We did this because there was a clear demand for transforming a de-facto stand
503.
by shykes 11y ago
FWIW we add a lot of new features, but we break very few APIs. API stability is extremely important to us, so you can actually build stable things on Docker and trust that we won't break it down the road.
504.
by shykes 11y ago
We have implemented user namespace support in runC, which we announced today :) https://runc.io Integration of user namespaces into the developer-facing tools is ongoing, but there is an design discussion to finish on how to bes
505.
by shykes 11y ago
Docker's new networking model is exactly what you describe. In fact it was developed with a lot of feedback from the Google team, so if you like Kubernete's networking model you'll be in known territory. It's true that t
506.
by shykes 11y ago
> It's humorous that what you just said goes exactly opposite to the blog post, which talks about how docker is designed to do everything completely differently because current methods "don't scale". I don't th
507.
by shykes 11y ago
As "the Docker guy" I don't want to enter the debate, I will simply try to explain how we approached this problem when designing Docker. Docker was designed explicitly so you don't have to change the architecture or fl
508.
by shykes 11y ago
From my experience, it's not either-or. First you need "bottom-up" adoption by actual practitioners (in the case of Docker, developers and sysadmins). Then you also need to understand the constraints and requirements of peopl
509.
by shykes 11y ago
> First, if CIOs and IT directors are calling, then it's possible they're confused by the website, too. I meant to say that they used to call us , back when our website looked like this: https://web.archive.org&#x
510.
by shykes 11y ago
Thanks for the frank feedback. I agree that we have a lot of "wiggle room", as you so diplomatically put it. Out of curiosity how do you feel about the current README on Docker's repo? https://github.com/docke

More ›