shykes

57 ms·

571.
by shykes 12y ago
Yes, what I call "embeddable Docker" is a desirable thing. It will help Docker integrate with other centralized daemons that want to own the process tree, like systemd. I've made it very clear in the past that I want this too
572.
by shykes 12y ago
No. There is a question on how to get machine to cleanly change which machine Docker talks to. The current answer is: standard dynamic config system in docker core, which machine plugs into to change values.
573.
by shykes 12y ago
Well, I think that was my limit right there. If the above message got downvoted, I really don't see any constructive way to have a conversation here. I think I tried. Come say hi on irc if you want to talk some more. We (the 200-ish pe
574.
by shykes 12y ago
Thanks for the comments. The advisory board met last month. Here is a writeup http://blog.docker.com/2014/11/docker-governance-advisory-bo... There is also a link to full minutes.
575.
by shykes 12y ago
I am listening. Walk me exactly through how you think we should support alternatives, and why you think we're not. I will work it out right here with you.
576.
by shykes 12y ago
Probably has something to do with this: https://twitter.com/solomonstre/status/540559322070392834
577.
by shykes 12y ago
Jerome don't forget that Django is monolithic. Docker is modular (ie swarm and machine are entirely separate binaries).
578.
by shykes 12y ago
How about sending a pull request on github/docker/swarm or github.com/docker/machine
579.
by shykes 12y ago
Hi all. A few clarifications. - The meme that we are adding more and more features into the docker binary is unfounded. Please, please, I ask that before repeating it you do your homework and ask for actual examples. For example 1.4 is comi
580.
by shykes 12y ago
Don't be unfair, clearly the 2nd list is nested :)
581.
by shykes 12y ago
An article spreading fud on Docker's philosophy is at the top of HN. I added a comment describing the actual Docker philosophy.
582.
by shykes 12y ago
I'm just calling you a troll, and it's for implying that a cabal of Docker employees somehow manipulates and suppresses the public conversation about containers for the profit of their employers.
583.
by shykes 12y ago
I guess I am. PR has never been my thing. I'll get back to hacking, after all it's the reason we do all this: building cool things.
584.
by shykes 12y ago
If you must know, the opposite just happened. Someone who happens to work at Docker just voiced their individual opinion. He was then reminded by "the PR machine" that it is better to take the high road and refrain from answering,
585.
by shykes 12y ago
I guess so - sorry ;) I hope you can understand that it's frustrating when, after hard work pitching an API to dozens of ecosystem players, spending weeks trying to wrangle a working implementation which makes as many of them as happy
586.
by shykes 12y ago
maybe they're busy designing the interface and implementing a proof-of-concept with us as we speak, instead of blogging and twittering.
587.
by shykes 12y ago
Now we're talking. Yes, I agree having a better spec for the underlying image format would be nice. In fact I also agree you should be able to use the Docker runtime without its packaging system, and vice-versa. However I think it mak
588.
by shykes 12y ago
> 1) Don't use Twitter for having long conversations and public fights. Just don't. No good will come out of it. I encourage you to read the twitter exchange I linked to. It predates all of this, and is not at all a fight. On
589.
by shykes 12y ago
All of which will be fully pluggable with a "batteries included but removable" design, just like we did with sandboxing and storage.
590.
by shykes 12y ago
Hi, I created Docker. I have exactly 3 things to say: 1) Competition is always good. Lxc brought competition to openvz and vserver. Docker brought competition to lxc. And now tools like lxd, rocket and nspawn are bringing competition to Doc
591.
by shykes 12y ago
That is an ongoing topic among the maintainers: support for multiple hardware architectures and OS flavors is a defining feature of Docker, and we need to get better at it. Within Linux-land we already deal with a multitude of storage and s
592.
by shykes 12y ago
Awesome, thanks. Anything we can do to help, just let us know. #docker-dev on Freenode. Many thanks for the contribution.
593.
by shykes 12y ago
Note from the Docker guy: I look forward to reviewing this PR, I agree zfs support would be an awesome addition. However, note that this PR is not against the actual Docker repo but against a contributor's fork. I suppose it's bec
594.
by shykes 12y ago
I am a big fan of these nano-images and really want to support them better in Docker's builder. See "nested builds" and "image squashing". Basically, you should be able to define a Dockerfile for the build environ
595.
by shykes 12y ago
Completely agree and we try hard to do just that.
596.
by shykes 12y ago
I can say that there are employees of major silicon companies already working on contributing all of this to upstream Docker. I was shown a real proof of concept already, it's very promising and not at all vaporware :)
597.
by shykes 12y ago
You forgot to quote the part where I said "I won't comment on whether it's good or bad". Canonical doesn't need to justify itself to me, no more than the Docker maintainers need to justify themselves to you. It&#x27
598.
by shykes 12y ago
No, Docker is not build on lxd. It used to be built on lxC, which is now an optional backend. The grand-parent is correct that lxd is a newly introduced competitor to Docker. I won't comment on whether it's good or bad, but it&#x2
599.
by shykes 12y ago
(just my personal opinion below, I'm not affiliated with the grand-parent) The tooling around the JVM is much more mature the Docker ecosystem in a lot of ways. However, one way to justify the "more modern" label is that Dock
600.
Docker Nabs VMware Guru Marianna Tessel as SVP Engineering(gigaom.com)
24 points by shykes 12y ago|1 comments

More ›