shykes

38 ms·

391.
by shykes 10y ago
I would categorize that under 5: competition . Kubernetes started out as an extension/modification of Docker, and over time Docker has evolved some of the same features as its kub-based competitors. The result is an uncomfortable inte
392.
by shykes 10y ago
Docker founder here. > What is the motivation and benefit for running containers without docker? I regularly hear from people who want to run containers without Docker. There are several motivations, all of which are perfectly valid: 1
393.
InfraKit: what you need to know(medium.com)
7 points by shykes 10y ago|0 comments
394.
by shykes 10y ago
They are quite different. - Ansible is a standalone tool with a very broad scope ("automation for everyone"). - InfraKit is an embeddable component with a very narrow scope ("create and manage declarative, self-healin
395.
by shykes 10y ago
> In theory could one build a plugin to run k8s on top of this? Then you could easily switch between swarm and k8s? Yes, absolutely, you could use Infrakit to provision any kind of infrastructure using a custom "flavor".
396.
by shykes 10y ago
Thanks :) I am a cfengine fan myself, it inspired me to start working on what would eventually become Dotcloud then Docker. There was also Radmind and ISconf, which did not enjoy the same success. I still remember reading the "infrastr
397.
by shykes 10y ago
Docker founder here. InfraKit is a higher-level component, it focuses on production deployment and "self-healing" state reconciliation. You can actually use terraform as a backend for infrakit. Another difference is that Infrakit
398.
by shykes 10y ago
Sorry, that wasn't the intention. I tried to clarify with an edit in the original post. It looks like now is not a good time for me to participate in this discussion. Instead I'll make a list of things we can improve so that the n
399.
by shykes 10y ago
Docker founder here. It makes me sad that you believe that. We're not perfect but we try very hard to keep our users happy. Are there specific issues that you could point out, so that I can get a sense of what you saw that you didn&#x2
400.
by shykes 10y ago
Docker founder here. > "Secure by default" is a great philosophy to have. I hope Docker continues to push into this direction. Thank you. We will absolutely keep pushing. > However, where is image signing? Docker support
401.
by shykes 10y ago
Off the top of my head: git can only use sha1 which makes it unsuitable for any use case where you need to cryptographically verify the origin of data (so far nobody was able to tell me definitely how secure git signed commits and tags real
402.
by shykes 10y ago
Two answers: 1) Modern hardware is getting much better at multiplexing resources (aka "making the things play nice with each other"). See for example sr-iov. 2) More and more applications are distributed across many machines, with
403.
by shykes 10y ago
I do too, but I didn't choose it :) It was an internal codename picked by one of the early engineers on the project. In fact I firmly intended to change the name before launch - but we accidentally launched ahead of schedule and people
404.
by shykes 10y ago
What about "macly"? :)
405.
by shykes 10y ago
Yeah... How about "mcl", "A Mac Command-Line tool"?
406.
by shykes 10y ago
Off the top of my head, I think "MacFoo" and "WinBar" are well-accepted conventions for tools built for the mac and windows respectively. Maybe look for something short and sweet in that vein? Or just something short and
407.
by shykes 10y ago
I agree the circumstances are very different, and obviously don't think there was any nefarious intentions. But the underlying fundamental issue - brand recognition and the value of having your work recognized under a name you control
408.
by shykes 10y ago
I don't have any suggestions, but will be happy to send them if I think of anything. The sooner you change, the better. Otherwise that is wasted brand equity for you. If you're going to work hard to build a great tool, the recogni
409.
by shykes 10y ago
I would advise finding another name for the tool. 'mac' is an obvious trademark infringement and it's only a matter of time before Apple lawyers come knocking on your door. Honestly I find it uncool to piggyback on someone el
410.
by shykes 10y ago
It wasn't mentioned because we only launched Docker for AWS and Docker for Azure. We only had the bandwidth to ship 2 versions at the level of quality we wanted, so we picked the most frequently requested providers. I think GCE is a gr
411.
by shykes 10y ago
That's incorrect. You are describing DNS-based load-balancing, which would indeed rely on the container's resolver implementation. But Docker doesn't do that. Instead it always resolves the service name to the same IP, which
412.
by shykes 10y ago
Disclaimer: I work at Docker. You are reading way too much into this. We're introducing orchestration in Docker because it solves a problem for our users. We haven't called your employer or anyone else "evil", and frankl
413.
by shykes 10y ago
> Due to caching implementations which change between OSes, programming languages, and routers, DNS is actually a really terrible discovery mechanism at scale. Only if you rely on the client's resolver caching implementation, whic
414.
by shykes 10y ago
You don't have to use overlay. Docker networking is pluggable and any networking configuration supported by Linux can easily ne expised to Docker via network plugins. The most common configurations (bridge, nat, host networking, no net
415.
by shykes 10y ago
Yes, all of that works seamlessly now. Each container gets an IP and is discoverable via DNS.
416.
by shykes 10y ago
Docker does follow the Unix philosophy: it's just that it's a unix-like collection of tools rather than a single tool. Under the hood Docker is made of many small components which you can use separately if you want: containerd,
417.
by shykes 10y ago
It's the latter. As we build up the Docker platform we're spinning out small individual components (the "plumbing") which other products can use and contribute back to. Here are a few of the components we have open-sourc
418.
SwarmKit by Docker: a toolkit to orchestrate distributed systems at any scale(github.com)
37 points by shykes 10y ago|4 comments
419.
by shykes 10y ago
Part of a healthy community is accepting that people disagree a lot, have different values, and communicate their ideas in very different ways. Where we draw the line is if people are being intimidated, bullied, insulted, or anything that e
420.
by shykes 10y ago
> That said, having ops excluded from the architecture decisions that go into building containers is absolutely antithetical to "doing devops". My point precisely. Just because there is clean separation of concerns doesn't

More ›