shykes

64 ms·

691.
by shykes 13y ago
Thanks for the solid explanations Benjamin. Docker will soon offer a better solution to service discovery. It will allow taking advantage of the various SD tools out there (zookeeper, etcd, synapse/haproxy, skynet, serf) while keeping
692.
by shykes 13y ago
Hi, Docker is pretty complementary with the configuration management tools you mention. Lots of people use them in combination. One common pattern is to use chef/puppet/salt/ansible to help you build the application stack in
693.
by shykes 13y ago
another thing to watch out for: downstream packages (the one you have installed) are out-of-date. The current version of Docker is 0.10.0, and ships a ton of improvements. For that reason alone you should consider installing from upstream
694.
by shykes 13y ago
There is an ongoing conundrum in the downstream Debian/Ubuntu packaging of Docker. Our friends at Debian and Ubuntu are doing their best to solve it. In the meantime, you should either a) install the latest docker from the official doc
695.
by shykes 13y ago
+1 in doubt, err on the side of trust.
696.
by shykes 13y ago
Well said Steve, we have 500+ issues on Docker and are going through the same process. The most valuable contributors are those who show up day after day and are not afraid of repetitive and unglamorous tasks. Those are worth their weight i
697.
by shykes 13y ago
You make good points in this post. We are working on addressing some of them already. I would love to discuss this directly, you can ping me anytime, shykes on #docker / freenode.
698.
by shykes 13y ago
> why in the world are there so many "slight" variations of a build? That's what happens if you tell all your developers to stop using capistrano, fabric, ftp and heroku, and tell them to create .debs out of EVERYTHING i
699.
by shykes 13y ago
> Those of us long time Debian users can appreciate having a service for those (very rare) situations in which something is not already (very well) packaged. Hi, I created Docker and am also a long-time Debian user. I disagree with you
700.
by shykes 13y ago
It's worth noting that as of yesterday the Docker index ( https://index.docker.io ) now offers github-style paid features. You can host private docker images, tie them to your source repo so that they are automatically rebuil
701.
by shykes 13y ago
Yeah, a full end-to-end explanation of how Docker can help you is one of the things we need to get better at. A full revamp of the documentation is underway :) There's a book being written at http://dockerbook.com/ The
702.
by shykes 13y ago
A few fun anecdotes illustrated by the video: [00m00s] In the first few months you can clearly see that Docker is a small side-project within Dotcloud. There is Andrea Luzzardi, Joffrey Fuhrer and myself toiling away and going door to doo
703.
by shykes 13y ago
That video of the project's activity over time is pretty awesome and almost brought a tear to my eye :) https://www.youtube.com/watch?v=FCiS812oRU8 (link didn't work for me on iOS)
704.
by shykes 13y ago
Kudos to Gabriel and the Deis team for being great Docker citizens. They take the time to make upstream contributions, are the first to try new features and APIs, and when something breaks they take the time to send thoughtful detailed repo
705.
by shykes 13y ago
FYI there is another project like this being discussed on Hacker News in parallel: https://news.ycombinator.com/item?id=7379166
706.
by shykes 13y ago
By the way Mitchell I think we fixed most of your bug reports - thanks and please keep them coming!
707.
by shykes 13y ago
Hi, Docker maintainer here. I'm not aware of any "bad blood", not everything has to be a war or a competition ;) Vagrant has been super useful to help us get a VM up and running with Docker pre-installed. But when boot2docker
708.
by shykes 13y ago
> I don't see a reason that docker needs to support multiple paths to a handful of syscalls, especially at this fairly-immature point in its evolution. Adoption. The priorities of Docker 1.0 are production quality and first clas
709.
by shykes 13y ago
We're on it. Releases are time-based so whatever is merged at the beginning of the month gets released. For bugfixes we maintain a backport branch and can release 0.9.1, 0.9.2 etc. as needed.
710.
by shykes 13y ago
Yes, probably as docker exec . While we're at it we will also fix the "pid 1" problem described in the phusion blog post (I would argue it's the most useful and constructive contribution in that blog post). Specifically
711.
by shykes 13y ago
Yes, it's definitely a first step in that direction :)
712.
by shykes 13y ago
There is a pull request underway which allows injecting new processes into an existing container using the public Docker API. That could be implemented by lxc-attach in the lxc driver, and by calling setns(2) natively in libcontainer. T
713.
by shykes 13y ago
Hi - we are listening :) I agree 0.10 might be confusing to people... But we had a discussion about it on #docker-dev and the conclusion was that in doubt, following the model set by Linux couldn't be that bad. The most important t
714.
by shykes 13y ago
This reminds me of the "10th floor test" in Bootstrapping an infrastructure , a Lisa'98 paper which was pretty influential for me and a whole wave of sysadmins getting excited about this transition from individual machines t
715.
by shykes 13y ago
Docker is evolving towards a generic "container engine" with swappable execution backends. In that architecture, lxc becomes one possible backend. ZeroVM, OpenVZ, kvm/qemu or plain chroot could be used as backends under the s
716.
by shykes 13y ago
Hi, Docker 0.8.1 was released last week, it fixes several old bugs as well as all known regressions spotted in 0.8. Would you mind trying it out, and letting us know in an issue if we missed your bug? Thanks!
717.
by shykes 13y ago
Yes.
718.
by shykes 13y ago
We built on lxc to save time and move faster on the things that differentiate Docker: image management, build from source, a developer-friendly UI, etc. Now that Docker has traction we can go back and invest more time in a cleaner, leaner i
719.
by shykes 13y ago
The release roadmaps of docker and lxc are completely decorelated. lxc reaching 1.0 doesn't mean much for docker - other than perhaps requiring working around yet another reverse-incompatible change. What's more interesting is pro
720.
by shykes 13y ago
Isn't spouse gender-neutral?

More ›