shykes

62 ms·

661.
by shykes 12y ago
Hi all, a quick warning: this is very rough and early, and not yet ready for production use. What we're aiming for is Unix-style composition. Because libswarm services communicate over unidirectional message streams (similarly to how g
662.
by shykes 12y ago
Actually it's Docker :)
663.
by shykes 12y ago
Homebrew is not an officially supported target. We build an official Darwin client as part of every release, on a Linux server using go cross-compile. Build failure of that target (or any target) would atomically roll back the entire releas
664.
by shykes 12y ago
Just in case you missed it: you can "docker commit" the state of a container at any time (and "docker diff" to see what has changed on disk since creation). Would that solve your problem?
665.
by shykes 12y ago
> I see with the launch of Docker Hub that they have some flagged as "official" now, but for example the Postgres one is a black box (no Dockerfile source available - not a "trusted build") so I can't trust it.[
666.
by shykes 12y ago
Docker and lmctfy have largely joined forces - Rohit and Victor are now core maintainers of Docker and kicking ass contributing all sorts of low-level system awesomeness :) https://github.com/dotcloud/docker/blob&#
667.
by shykes 12y ago
Yes, user namespaces are coming soon.
668.
by shykes 12y ago
This is a huge undertaking and we are determined to get it right. Thanks again to Brad Fitzpatrick and everyone else contributing this building block!
669.
by shykes 12y ago
Yeah, we spent some time with logging providers to get feedback on the design, and had to go back to the drawing board a little bit. We're going to show the result of that tomorrow :) We decided to ship 1.0 anyway just for the sheer vo
670.
by shykes 12y ago
I should clarify that I am not part of the Deis project, although I know Gabriel and follow their roadmap closely.. Sorry if I wasn't clear.
671.
by shykes 12y ago
I understand. But from the point of view of Deis, CoreOS is not a platform. It is a Linux distro with a loose collection of tools pre-installed, some of which Deis happens to use. One such tool is Fleet. Another is the systemd log journal.
672.
by shykes 12y ago
That's assuming Docker doesn't expand its interface to allow for more parts of the platform to be interoperable :) The whole point of Docker is to introduce simple interfaces to important components of distributed systems, and get
673.
by shykes 12y ago
My understanding of Deis's design goals is that they will pick and choose their favorite components from any number of sources (including but not limited to CoreOS), but don't plan on locking themselves into any particular distro.
674.
by shykes 12y ago
Google deserves a shout-out for embracing Docker in a really constructive way. In addition to building cool tools on top of it (like the one linked here), they are also contributing real engineering effort into the upstream Docker project i
675.
by shykes 12y ago
There's a lot of discussion about that on #docker-dev. I think we (Docker maintainers) might pick a default format + plugin system to swap in your own. Of course the plugin would itself be a container :)
676.
by shykes 12y ago
For what it's worth we (Docker maintainers) are working on adding this feature :) In the meantime you can use something like supervisord or runit inside your container.
677.
by shykes 12y ago
Yes, there are a few things we are very impatient to show at Dockercon :) I hope some of you can make it to the hackfest!
678.
by shykes 12y ago
Thanks, unfortunately too late to correct...
679.
by shykes 12y ago
The "official" Docker workflow looks like this: * Install Docker on your dev machine (remember, there is a Mac version too) * Add a Dockerfile to your source repo, specifying how to assemble a container image from source. * Use a
680.
by shykes 12y ago
What would you expect it to do exactly? Remove all untagged images?
681.
by shykes 12y ago
The focus for 1.0 is to offer the APIs necessary to customize Docker in every way you need - including custom sandboxing backends (like for example BSD Jails). There is now an execution driver API (which was indeed planned for 1.0), and now
682.
by shykes 12y ago
+1 on that, anyone who takes the time to tell us about their issues with Docker is automatically making a valuable contribution to the project. And it's appreciated, so yes, thank you :)
683.
by shykes 12y ago
Most of the discussion has been on irc: #docker and #docker-dev on Freenode. There are several contributions underway under the general "theme" I described, but if it helps I could write a summary of how the experience will change
684.
by shykes 12y ago
You're right, the logging subsystem still needs work before 1.0. We're using the RC label to indicate that we don't plan on breaking APIs and file formats in any major way between now and 1.0, so toolmakers and integrators ca
685.
by shykes 12y ago
Hey, I'm a Docker maintainer. We don't plan on "keeping it that way". Disk clutter after lots of builds is a problem which we're very much addressing. It's specifically a top-level docker clean command that I
686.
by shykes 13y ago
You can "docker push" any binary image to index.docker.io. However if you don't use a Dockerfile, you won't be able to use the Trusted Build feature, and other users won't be ae to verify which source the image was
687.
by shykes 13y ago
Dockerfiles are designed to give you all the primitives you need to compose arbitrarily complex build processes, and no more. A Dockerfile is not a replacement for your favorite build script: it's a reliable foundation for defining, un
688.
by shykes 13y ago
Just make sure you still use Dockerfiles. Otherwise you'll be missing a big part of Docker's features.
689.
by shykes 13y ago
Of course I'm biased but I consider it a significant regression in your usage of Docker to build images from a vagrantfile instead of a Dockerfile. I'm curious why you feel Docker doesn't offer separation of respinsibilities?
690.
by shykes 13y ago
You don't have to choose between what's inside and what's mounted in. You can mark persistent directories (directories that should live longer than any given instance) as volumes with "dockercrun -v". Docker will ar

More ›