#docker-dev

tianon: lsb headers should match the script name

so if it's docker, it provides docker

if it's lxc-docker, it provides lxc-docker

but that's an easy patch to make

ok, that's what I was hoping you'd say, and you surprised me because we were talking about different things :)

I'll update with that real fast (so we Provides: docker) :)

updated \o/

jawsome

I added a better Short-Description and Description here, too :)

because they made me sad inside :)

good :)

(as they should)

"Linux container runtime" <- this just doesn't even begin to scratch the surface of Docker :)

yeah :)

so I stole some text from docker.io :D

the one true source of all marketing knowledge :)

vieux: https://gist.github.com/afriggeri/1266756

hahaha

jpetazzo: what do you think of adding namespace and cgroup information in the docker inspect info?

could be a first baby step towards merging pipework

I also have made progress on network plugin api during my vacation :)

that plugin system is finally turning into a reality

tianon: thanks for MC-ing the irc meeting

indeed, glad to help :)

still planning to do it again this week, unless told otherwise :P

jpetazzo: just fyi, i wasn't able to mknod a block device using -lxc-conf (no -privledged)

shykes: any way me or keeb could get access to change the /topic of #docker-meeting (while we're on the subject) ? :)

it's a little dated :)

yeah of course

#docker-meeting is coming shortly, right? :)

ohh, I'm op'd now, I must abuse my power

+m ftw? :)

where is tianon?

haha

must boot

that'd make this channel so quiet and readable, though!

gabrtv: mknod also requires cap_mknod, sorry! forgot to mention that.

tianon: unfortunately #docker-meeting is not registered

and I am no longer op there

oh bollocks

the only way to register it is for everyone to leave

can't a freenode oper do something for us in this case?

I don't know

they can

just ask them, they'll ask if anyone objects, and give you +o

well, if nobody else is on this, I'll go ask in #freenode if shykes can be opered in #docker-meeting :)

[docker] vieux created links_names_generator (+1 new commit): http://git.io/ytxjWQ

docker/links_names_generator 206b081 Victor Vieux: add name generator

[docker] vieux opened pull request #2422: Add name generator (links...links_names_generator) http://git.io/4uVFWw

jpetazzo: fyi, if you close a bug, the original opener can't reopen it, so you may want to just mention that they should ping you if they need it reopened :)

[docker] vieux force-pushed links_names_generator from 206b081 to 08f8f83: http://git.io/iEziZA

docker/links_names_generator 08f8f83 Victor Vieux: add name generator

don't know what the name generator is for, but I fully support it!

agree :) definitely like the idea of making all the names shipping-related, too :)

so I played with links today and they're super fun. I can see that inter-container networking is off by default now... but is there a way to turn that on for a single container to be able to talk to the others?

say, for a hipache container that needs to forward to all the others? is it possible to open up the hipache container but keep links-only networking between the others?

[docker] vieux force-pushed links_names_generator from 08f8f83 to f14bfec: http://git.io/iEziZA

docker/links_names_generator f14bfec Victor Vieux: add name generator

[docker] vieux force-pushed links_names_generator from f14bfec to 971cf56: http://git.io/iEziZA

docker/links_names_generator 971cf56 Victor Vieux: add name generator

xdissent_: no

your saying that every container needs to talk to hipache?

not every one... just many! =)

why do they need to talk to hipache?

i could explicitly link my web app containers to hipache container, but then if i add another web app i'd have to restart hipache right?

hipache needs to forward to them

humm

does that make sense though?

it sounds like hipache needs access to all the others, not the other way around

since it'd be the frontend for all of them

yeah that's what I mean, sorry.

which means I need them running before hipache starts, so they can be linked into the hipache container

and some way to seed their IP/port info into redis for hipache to use

or to make sure it stays consistent

right - I've got that part under control ;-)

[docker] vieux pushed 1 new commit to links: http://git.io/w7D3dg

docker/links c066248 Victor Vieux: Merge pull request #2422 from dotcloud/links_names_generator...

[docker] rogaha opened pull request #2423: - Added volumes documentation (master...volumes_doc) http://git.io/JRt58w

tianon: argh, I didn't know that. thanks for improving my github-fu!

indeed :)

tianon: jpetazzo: note for gordon feature: indicate to gordon to reopen an issue when the requester asks it to

yes! :D

has anyone played with 0.7rc4?

[docker] mzdaniel pushed 1 new commit to docker-ci: http://git.io/cQtG7Q

docker/docker-ci 6b7df1b Daniel Mizyrycki: docker-ci 0.36. Patch hack/dind with latest code for nightly release to work.