shykes

103 ms·

961.
by shykes 13y ago
FWIW we keep track of community-contributed guides on this wiki page: https://github.com/dotcloud/docker/wiki/Docker-external-reso... (Or we try to, anyway - it's getting a little hard to keep up :)
962.
by shykes 13y ago
There are a lot of really cool tricks in this post for deploying Docker in a "real-life" installation, including disk quota, service orchestration, and dynamically routing traffic to your containers. A great example of how to take
963.
by shykes 13y ago
For those of you wondering what RethinkDB and Docker are: RethinkDB ( http://rethinkdb.com ) is "an open-source distributed database built with love. It lets you enjoy an intuitive query language, automatically parallelized q
964.
by shykes 13y ago
There has been some work around integrating docker iwth Openstack floating IPs already. Check out http://github.com/dotcloud/openstack-docker
965.
by shykes 13y ago
They are not mutually exclusive. An ideal system would honor the Dockerfile when it is present, and attempt to auto-detect the build method when it is not. Buildpacks are great defaults when auto-detecting. That way, you get a nice out-of-b
966.
by shykes 13y ago
Static IPs and private networks are not particularly un-Dockerish. They are just not the default implemented by Docker :) Docker 1.0 will include an API which will make it much easier to customize how you want networking to happen. That inc
967.
by shykes 13y ago
Hi, I'm the founder of dotCloud and author of Docker. Projects like Flynn are the reason we opened Docker in the first place. They are a good thing for the docker ecosystem, and they are definitely good for dotCloud. The dirty little s
968.
by shykes 13y ago
That's why they use docker: it automates the process of building and packaging Graphite, so you don't have to worry about it. $ docker run lopter/collectd-graphite You're done.
969.
by shykes 13y ago
There's also Owncloud: http://dischord.org/blog/2013/07/10/docker-and-owncloud/
970.
by shykes 13y ago
> There's a standard format, OVF, that the relevant players seem to support I'll just point to the elephant in the room: EC2 doesn't support it. Neither do the majority of IAAS players. Even those that are OVF-based unde
971.
by shykes 13y ago
Tags do help. Our problem is the sheer volume of issues - 260 currently open and counting [1]. So prioritizing becomes an issue, as well as the unbarably slow web ui. [1] https://github.com/dotcloud/docker/issues?d
972.
by shykes 13y ago
I'm going to test this right away for Docker. We are completely overwhelmed with github issues, and the bottleneck is not contributors: it's our ability to communicate where we need the most help.
973.
by shykes 13y ago
The problem with VMs is that they're not a practical vehicle for shipping software, because they're not portable. Developers will always have to deal with multiple incompatible VM formats, in addition to deployment targets which s
974.
by shykes 13y ago
And web UIs for docker: https://github.com/crosbymichael/dockerui https://github.com/ehazlett/shipyard
975.
by shykes 13y ago
Docker already includes a registry :) "docker pull borplk/tres.io"? You can search at http://index.docker.io
976.
by shykes 13y ago
We're working on a few things that will make that much easier :)
977.
by shykes 13y ago
Docker does use lxc under the hood. They serve very different purposes. lxc is a tool for sysadmins to deploy and configure virtual servers on their machines. docker is a tool for developers to package their application into a deployable ob
978.
by shykes 13y ago
The website offers install instructions for several OSes: http://docs.docker.io/en/latest/installation/
979.
by shykes 13y ago
We chose Go, even though we're traditionally a Python shop, for a few reasons: 1) It compiles to a static binary, which makes it very easy to drop docker into an existing ops stack with very little hassle and without having to drag a w
980.
by shykes 13y ago
The idea behind Dockerfiles is to allow a source repository to be built and packaged automatically, to the exact specification of the upstream developer, regardless of his/her choice of development tools, distro or language. Source rep
981.
by shykes 13y ago
> What I would love to see is a tool for abstracting this deployment pattern on-top of ezjail. I've been considering doing this myself but my time is stretched too thin :( This is basically what we're doing with Docker. We st
982.
by shykes 13y ago
Overlayfs has a static limit of 1 ro layer, which makes it useless out of the box for docker. It's also less proven in production than aufs. Aufs works great and has no decent alternative. Merging aufs into mainline feels like the logi
983.
by shykes 13y ago
That would be fantastic. Unfortunately I don't have the answer right now.
984.
by shykes 13y ago
That's just our docs being unclear :) You can run docker on debian wheezy, no problem. Docker is currently easier to run on certain distros than others. But it's not because it's distro-specific. It's because it has k
985.
by shykes 13y ago
Yes, that's exactly the goal of docker: "build once, actually run anywhere". Docker is a portable container engine. It gives you, the developer, a way to package your app and all its dependencies into a portable container w
986.
by shykes 13y ago
I do think dtrace is awesome, and would certainly not make an argument against using it. We may very well use it in the future. There was no active decision not to use it at dotCloud, our "visibility toolbox" is simply based on
987.
by shykes 13y ago
Note that I am not complaining or demanding anything. You are right in assuming that I do not miss dtrace and zfs enough on my linux boxes to contribute individually to the porting effort. I am simply observing that porting these tools to L
988.
by shykes 13y ago
Correct, docker is not an implementation of linux containers. The heavy lifting is done by lxc (and alternatives like openvz). What docker brings is a way for backend developers to package and distribute their app into portable, sandboxed c
989.
by shykes 13y ago
SmartOS is a distant relative of Solaris. It's an alternative to Linux for the server with all the Solaris bells and whistles (zfs, zones, dtrace) and great tooling for virtualization. Unfortunately it's not very widely adopted an
990.
by shykes 13y ago
Only through libvirt, which by design only exposes the lowest common denominator among all supported backends. Docker needs its own native backend for the same reason Xen has its own: so it can do more cool stuff. See [1] and [2] for more d

More ›