shykes

38 ms·

421.
by shykes 10y ago
I agree with you and we have a similar process at Docker. Part of what went wrong in this particular case is precisely that our infrastructure incident response process did not kick in. I am guessing that one conclusion of the post-mortem w
422.
by shykes 10y ago
Disclaimer: I work at Docker. It's true that Docker helps separate dev concerns from ops concerns. But it doesn't prevent dev and ops teams from collaborating, or the same team to wear both hats - the most common aspects of a &quo
423.
by shykes 10y ago
> You may want to lock that GitHub thread soon, it's getting argumentative and not very helpful. In open-source we call that "thursday" :)
424.
by shykes 10y ago
Hi, I work at Docker. Here is my reply on the github thread: https://github.com/docker/docker/issues/23203#issuecomment-2... I am copying it below: <<< Hi everyone. I work at Docker. First, my apolog
425.
by shykes 10y ago
Disclaimer: I work at Docker. I believe commercial releases are downloaded from a separate infrastructure (to be confirmed). Either way, the availability of Docker packages, free or commercial, is critical infrastructure and we should treat
426.
by shykes 10y ago
Actually it's runc that is the linux container version of OCI. Docker is a higher-level abstraction which calls runc by default but can call any OCI-compliant runtime, including runv. See https://blog.docker.com/2016&
427.
by shykes 10y ago
This is a fantastic use case, we (Docker) would love to help in any way we can to make this usable by all Docker users. Let us know if there's anything more we can to help.
428.
by shykes 11y ago
IMPORTANT: as suggested in another comment, please signup for the beta before responding . Thank you all for investing your time in this thread, it is incredibly rewarding for the team to see their work appreciated and used by our fellow h
429.
by shykes 11y ago
Disclaimer: I work at Docker. Yes, we screwed up on the b2d->machine transition. Sorry for making that experience unnecessarily confusing. We've learned a lot from that mistake and are working hard to avoid repeating it.
430.
by shykes 11y ago
If you're comfortable sharing your Docker ID, feel free to share it here and we'll fast-track you! Generally anyone who cares enough to ask directly, we'll automatically add to the top of the list. EDIT: or, feel free to cont
431.
by shykes 11y ago
Disclaimer: I work at Docker. The reason we are keeping the beta private is because we don't believe the quality is good enough yet to "open the floodgates". We are sending as many invites as the engineers are comfortable wit
432.
by shykes 11y ago
Disclaimer: I work at Docker. Most of your points are a criticism of TUF, of which Notary and Docker Content Trust are an implementation. Based on your comments I believe you're not familiar with TUF and the scope of problems it solves
433.
by shykes 11y ago
When I moved to the Bay area from France, I was very surprised by the complete lack of organized government at the regional level. Decisions, planning an budgeting seem to happen either at the San Francisco level, or at the California level
434.
by shykes 11y ago
Yes that is a common workaround as well. By the way: there is an open request for contributions to help improve this. The core Docker team very much wants to improve squashing in build, but it's a matter of time and resources. If someb
435.
by shykes 11y ago
(I didn't downvote you) Disclaimer: I work at Docker. Your approach is the logical one... But Docker currently has a limitation in how it handles removing files in a build. After each build step, the intermediary state is committed as
436.
by shykes 11y ago
You don't come across as mean spirited, it's a fair point. I didn't mean that Docker is the most widely deployed software in a particular category (that would be hard to measure accurately anyway). But what Docker introduced
437.
by shykes 11y ago
Disclaimer: I work at Docker. Docker has become a de facto standard for executing programs in a portable sandbox (aka "container"). There were increasing demands for making it a "proper" standard, so last year we donated
438.
by shykes 11y ago
We've had to fork xhyve very heavily for Docker to embed it, and are making many changes in a very rapid loop as we improve d4mac. We're still debating whether to contribute back into xhyve or just make it a separate open-source p
439.
by shykes 11y ago
It's something new.
440.
by shykes 11y ago
The NDA is just residue from the alpha teating phase, we'll remove it. We will open-source all the components individually, to make them easier to reuse elsewhere. That requires work to do properly. Lastly, Docker for Mac and Docker fo
441.
by shykes 11y ago
Yes, all the components will be open-sourced.
442.
by shykes 11y ago
We want to open-source the system components separately , so that you can use them separately from docker if you wish. That is different (and more useful) than just dropping a big xcode project on github and letting you dig for the gems. W
443.
by shykes 11y ago
The use of musl on the host, outside the container, has absolutely no impact on the choice of libc inside the container. The team chose alpine because it's lightweight, well-maintained and security-oriented. You are free to use any d
444.
by shykes 11y ago
Yes, the problem is that we would need to change the default behavior of Docker, which many people and scripts expect to be stable. It's a case of interface stability vs. functionality improvement. So far interface stability has won. I
445.
by shykes 11y ago
Hi, I'm the founder of Docker. Sorry that you had an issue on the website. I warned the team of your comment, feel free to email me directly at s@docker.com and I'll put you in touch. Note that the price you mention is yearly. A n
446.
by shykes 11y ago
I haven't looked at this in detail, but does this work with the standard networking features introduced in Docker 1.9 [1] and 1.10 [2]? Can I still use 'docker network create/connect' and the DNS service discovery featur
447.
by shykes 11y ago
Yes. And Docker 1.10 does DNS service discovery out of the box.
448.
by shykes 11y ago
Correct, layers were hashed for verification at upload and download, then stored on a "regular" uuid-addressed storage. Now they are stored in a true content-addressed store end-to-end.
449.
by shykes 11y ago
OCI focuses on the intermediary runnable format (think "ELF for containers") for a simple pragmatic reason: to accomodate pre-existing container packaging systems which were not compatible with each other. A good analogy would be
450.
by shykes 11y ago
You don't have to use docker pull. You can use any system capable of distributing a standard OCI bundle, including (but not limited to) docker.

More ›