shykes

53 ms·

541.
by shykes 12y ago
> My ideal setup would be a hypervisor infrastructure with a bunch of VM's running only Docker applications. You should take a look at https://github.com/docker/machine and https://github.com/
542.
by shykes 12y ago
Hi, Docker author. Just wanted to say that we are aware of the problem, understand the underlying mechanics, and plan to fix it. In the meantime application-level fixes like this can definitely help. One slight difficulty is that some appli
543.
by shykes 12y ago
On the vc-backed point, i should have been more specific. There is nothing wrong with being vc-backed. However there has been a deliberate attempt at crafting a narrative of "docker is expanding feature scope because it is vc-backed th
544.
by shykes 12y ago
That's an understandable criticism, even though it makes me want to die inside. Let me try and explain my point of view, and why this whole situation is so frustrating to me. First, my impression is that I do spend most of my days li
545.
by shykes 12y ago
It's mostly an artifact of our initial focus - a great integrated user experience - combined with the fact that Docker became incredibly successful, incredibly fast. Image management is combined with runtime since the very first versio
546.
by shykes 12y ago
We do take security reports very seriously, when they were brought to the project repo: https://github.com/docker/docker/issues/9719 If you are looking to gauge our reaction to legitimate criticism and bug re
547.
by shykes 12y ago
All the issues in this post are already known and being actively discussed on the mailing lists and repo (including with the blog post author). However nobody so far had noted that the "image verified" message is misleading and sh
548.
by shykes 12y ago
I agree. The message should be more clear.
549.
by shykes 12y ago
The business model is the same. We are selling cloud services via Docker Hub, in addition to training and support. All the new features are pure open design, they only exist because users are asking for them and people are sending patches.
550.
by shykes 12y ago
I wish the author had not omitted this crucial paragraph in the announcement he quotes: Note that this feature is still work in progress: for now, if an official image is corrupted or tampered with, Docker will issue a warning
551.
by shykes 12y ago
We're mostly looking at supporting remote volume sync in docker itself, with a pluggable transport - could be smb, nfs, periodic rsync, sftp... bradfitz started an awesome contribution with a full remote-fuse-protocol sync :) pretty aw
552.
by shykes 12y ago
Doesn't excuse my initial knee-jerk reaction... Anyway, let's move on and focus on building cool stuff now :)
553.
by shykes 12y ago
One area of possible improvement is that boot2docker's default mechanism for sharing volumes with the mac is virtualbox guest additions, which are notoriously slow. As for performance, to my knowledge it's simply a matter of the u
554.
by shykes 12y ago
CoreOS got a dedicated meeting the previous week. I pitched all this to them in person and seemed to get a cautiously optimistic response with agreement to follow-up soon. The next day, they announced rocket without warning. I'm happy
555.
by shykes 12y ago
I must say I expected a less elaborate response, so thanks for that. EDIT: I initially left a long response that explained why I think your accusations are unfounded. But, on second thought, I think we should spare everyone else and discus
556.
by shykes 12y ago
Everything you say is true, but it doesn't mean this web ui is not useful, or a bad idea. It just means that it should add authentication :) Since we are developing Docker's identity and authentication primitives separately from t
557.
by shykes 12y ago
That makes no sense whatsoever. By default the Docker daemon listens only on a local unix socket only accessible to root (and in some distros a separate root-equivalent group). The CoreOS model relies on running all containers via another c
558.
by shykes 12y ago
This is a presentation about how we manage contributions and maintenance of the Docker project, which has 700 contributors and receives about 50 pull requests per week. I also talk about governance, and how to manage the balance between the
559.
Open design at large scale (Dockercon presentation)(slideshare.net)
12 points by shykes 12y ago|2 comments
560.
by shykes 12y ago
Take a look at the article, there is detailed comparative data on volume, response time, merge rate, split by Docker inc employees and non-employees.
561.
by shykes 12y ago
FYI today we had a design session on this topic with several members of the ecosystem (Weave, ClusterHQ, Socketplane, Tutum, VMWare) during Dockercon. As soon as there's something worthy of a proposal, we'll open it up for comment
562.
by shykes 12y ago
All of these things have happened. Do you have specific evidence of the contrary? I gave a presentation on this topic at Dockercon today, it talks about how the project is organized, how the company is firewalled, and recent improvements we
563.
by shykes 12y ago
> You state Docker is not monolithic -- but then the next sentence says you want to break Docker down into composable parts. Which is it? It's both. Docker is already quite modular. For example storage and execution backends are s
564.
by shykes 12y ago
The flag is tcp:// for historical reasons. In earlier versions Docker did not use an http api, but a simple custom rpc protocol. Therefore it would have not made sense to use http:// . Then, when we introduced the ht
565.
by shykes 12y ago
Thanks guys. It doesn't look like this will make it to the front page, but I saw it and really appreciate the encouragement. I definitely screwed up on communication around this whole thing. It's a shame since I think I can give a
566.
by shykes 12y ago
It seemed like the same question me. On "stopping for a while to think", I suppose it's subjective. From my point of view we spend insane amounts of time thinking about the right design for all these things. At the same tim
567.
by shykes 12y ago
> (none of these is individually harmful, but I personally find the monolithic architecture a bit of an issue) The architecture is not monolithic. I want to break down Docker into the most discrete and composable parts possible. But I
568.
by shykes 12y ago
I understand, but the problem is that to "just run a container" Docker needs to manage global system state and synchronize with other docker instances. Right now that is done with the daemon. How do I do this without? CoreOS'
569.
by shykes 12y ago
Is there a particular feature you wish Docker had not added? 1.4 RC had 2 months worth of stabilization and basically no new features.
570.
by shykes 12y ago
Yeah we used to call it "standalone mode", it was pretty neat but really confused users (it would auto-detect whether to go daemon mode or not, so behavior became contextual and hard to troubleshoot). Yes, managing communication o

More ›