News for hackers. Stuff that matters.
Re:Docker 0.6: Events API, registry improvements, expert mod... by codexon on Friday August 23, 2013 @05:46PM (#6266425)
When is the AUFS requirement going to be removed?

Ubuntu is going to drop it in the near future. So the idea of rebooting all servers to install a custom kernel with AUFS makes me not even want to try it.

Re:Docker 0.6: Events API, registry improvements, expert mod... by nickstinemates on Friday August 23, 2013 @06:05PM (#6266504)
Soon. It's a core use case with a lot of interest around it. There have been experimental branches created to try out other filesystems and no major issues were found. It's a matter of getting the API right, which is what the Docker team and Community are working on together as I type this.
Re:Docker 0.6: Events API, registry improvements, expert mod... by codexon on Friday August 23, 2013 @06:23PM (#6266564)
What would you guess the preferred filesystem would be when this gets implemented? Btrfs?
Re:Docker 0.6: Events API, registry improvements, expert mod... by nickstinemates on Friday August 23, 2013 @06:51PM (#6266670)
If I had a crystal ball, I'd bet it'd depend on the Docker Host and what the canonical union filesystem choice is.

What I've found is that the answer/preferred answer to your question is ultimately quite fragmented across organization and application types.

Re:Docker 0.6: Events API, registry improvements, expert mod... by eikenberry on Friday August 23, 2013 @06:05PM (#6266502)
Any references on why they are dropping it and what they are replacing it with?
Re:Docker 0.6: Events API, registry improvements, expert mod... by WestCoastJustin on Friday August 23, 2013 @06:47PM (#6266658)
I assume they are dropping it to allow much wider adoption. Docker makes use of AUFS for many of its cool features, like quickly spinning up containers, snapshots, diffs, etc. Ubuntu is dropping AUFS support in its stock kernels [1], and RHEL (CentOS, SL, etc) does not have support for AUFS in their stock kernels [2], and it is a major pain to try and add it (i.e. not even a simple recompile, you need custom patches, etc). So, given these two issues, you run the risk of alienating your user base pretty quickly.

[1] http://ubuntu.5.x6.nabble.com/RFC-AUFS-disabled-for-12-04-td...

[2] https://github.com/dotcloud/docker/issues/172

Re:Docker 0.6: Events API, registry improvements, expert mod... by eikenberry on Friday August 23, 2013 @07:53PM (#6266900)
I was talking about why Ubuntu was dropping AUFS, not why docker was. I've been following the UnionFS area in Linux for awhile now and AUFS still seems to be the only viable option. So I was asking to find out if Ubuntu expects one of the alternatives to be ready soon.
Re:Docker 0.6: Events API, registry improvements, expert mod... by shykes on Friday August 23, 2013 @08:18PM (#6266989)
Speaking as a dotCloud employee: yes, it's also our opinion that aufs is still the most viable option in a production setting. Finding a permanent solution to the clusterfuck of union filesystems in linux seems as likely as peace in the middle-east: those with a viable solution are powerless to impose it; those who could change the status quo seem paralyzed by bias, personal feuds or simply having other fish to fry. Meanwhile the rest of the World has thrown their hands up and stopped waiting. Aufs works in production, moving on.

Speaking as a Docker maintainer: we'll add support for whatever our users want most, and makes it easy to run docker everywhere.

Re:Docker 0.6: Events API, registry improvements, expert mod... by tacticus on Saturday August 24, 2013 @01:42AM (#6267793)
Perhaps something like btrfs could work.

By creating your base image in a subvol or individual file you can then snapshot that and mount the snapshot into the container?

additionally it lets you piggy back on the stuff that inktank and openstack are doing with ceph and btrfs

distributed storage with cow images for VMs for your container servers

Re:Docker 0.6: Events API, registry improvements, expert mod... by shykes on Saturday August 24, 2013 @07:14PM (#6270209)
btrfs is one of the alternatives we plan on supporting. In fact there is already an experimental branch with btrfs support.

However, wearing my user / operator hat, if I had to choose I would stick to aufs in production. If I had to switch (and the apparently stupid move by ubuntu to drop it might indeed force me to), I would first try to use more proven code, like lvm or raid/dm.

btrfs and overlayfs are neat, promising technology for the future - that place where our production deployments can't go :)

Re:Docker 0.6: Events API, registry improvements, expert mod... by mh- on Friday August 23, 2013 @08:43PM (#6267066)
I appreciate the candid nature of your post and the pragmatic opinion; thanks for sharing. :)
Re:Docker 0.6: Events API, registry improvements, expert mod... by nickstinemates on Friday August 23, 2013 @06:06PM (#6266505)
Replacing with <insert your choice here> via plugin[1]

1: http://blog.docker.io/2013/08/getting-to-docker-1-0/

Re:Docker 0.6: Events API, registry improvements, expert mod... by shykes on Friday August 23, 2013 @03:44PM (#6265873)
Hi everybody, this is quite a monster of a release: 378 commits by 40 different people :)

Here's the full release pull request if you're interested: https://github.com/dotcloud/docker/pull/1628

Re:Docker 0.6: Events API, registry improvements, expert mod... by golubbe on Friday August 23, 2013 @04:49PM (#6266176)
What makes this especially exciting for me is that >80% of those people are from the community (i.e. not dotCloud employees).
Re:Docker 0.6: Events API, registry improvements, expert mod... by nacs on Friday August 23, 2013 @03:51PM (#6265898)
I've been meaning to try this for a while now but the release of your new Ubuntu repo (as opposed to PPA, details here for other Ubuntu users: http://docs.docker.io/en/latest/installation/ubuntulinux/ ) has convinced me to finally install.

Congrats on the release. Love how fast the docker team is updating.

Re:Docker 0.6: Events API, registry improvements, expert mod... by shykes on Friday August 23, 2013 @04:18PM (#6266024)
Thanks!

Out of curiosity, what's your reasoning for preferring a custom repo instead of a PPA?

Re:Docker 0.6: Events API, registry improvements, expert mod... by timClicks on Friday August 23, 2013 @05:16PM (#6266292)
Can anyone point to an evaluation of the various orchestration/wiring tools mentioned in the post, e.g. "Orchestra, Shipper, Deis, Pipeworks, etc"?
Re:Docker 0.6: Events API, registry improvements, expert mod... by nickstinemates on Friday August 23, 2013 @06:07PM (#6266510)
I haven't seen one, Tim, but I'd love to see it. Will you volunteer? :)
Re:Docker 0.6: Events API, registry improvements, expert mod... by timClicks on Friday August 30, 2013 @06:45PM (#6304672)
Added to weekend projects list. ETA mid-October.
Re:Docker 0.6: Events API, registry improvements, expert mod... by johnpmayer on Friday August 23, 2013 @09:52PM (#6267237)
It's worth pointing out that there's now a digitalocean pre-configured image with Docker.
Re:Docker 0.6: Events API, registry improvements, expert mod... by nickstinemates on Saturday August 24, 2013 @02:48PM (#6269407)
This is so cool. I'll be picking one up.
Re:Docker 0.6: Events API, registry improvements, expert mod... by contingencies on Saturday August 24, 2013 @04:40AM (#6268116)
Given the recent thread I'm interested in what the security updates were given that the word security doesn't occur in the changelog. Can someone closer to the source please explain?
Re:Docker 0.6: Events API, registry improvements, expert mod... by nickstinemates on Saturday August 24, 2013 @02:49PM (#6269413)
From the blog post:

> We have tightened Docker’s default access control configuration, to make it more suitable for use on a host machine shared with untrusted applications. Running docker commands now requires either root privileges, or a user account included in the “docker” group.

> This means that after upgrading to 0.6, you will need sudo to run docker commands.

> Don’t worry, you can revert your configuration with the “-H” flag. Just make sure you understand the security implications!