#docker-dev

/

      • rjhunter joined the channel
      • rjhunter has quit
      • rjhunter joined the channel
      • rogaha has quit
      • rjhunter has quit
      • titanous joined the channel
      • rjhunter joined the channel
      • rjhunter has quit
      • zz_crosbymichael is now known as crosbymichael
      • tianon
        paultag: here's my WIP: https://github.com/tianon/debian-docker (still working on some changes locally, like getting a Dockerfile that actually works correctly)
      • once I've got a Dockerfile that works properly, I'll update the building bit :)
      • crosbymichael
        tianon: did you know sshd crashes in the stackbrew/ubuntu:13.10 image ?
      • tianon
        wat!
      • tianon goes to go test that
      • crosbymichael
        you calling me a liar! ;)
      • tianon
        hah, no
      • of course not :)
      • just want to reproduce locally so I can investigate :)
      • unless you already have a fix for me ;)
      • remember, you can't open tickets without also including a PR to fix them! :)
      • crosbymichael
        no, I rebuilt the image using debbootstrap and have the same issue
      • tianon
        and it's just 13.10?
      • crosbymichael
        12.04/12.10 work
      • tianon
        or that's all you tested?
      • ah
      • crosbymichael
        i didn't try 13.04
      • you have to connect and then the daemon crashes on connection
      • i can create a dockerfile to reproduce if you want
      • tianon
        ah ok, thanks for the additional info :)
      • rjhunter joined the channel
      • ooh, kicked right out
      • daemon's still running, though
      • rjhunter has quit
      • rjhunter joined the channel
      • crosbymichael
        launching from bash the daemon was dying on me with debug mode
      • rjhunter has quit
      • tianon
        well that makes sense, since debug mode "will only process one connection."
      • rjhunter joined the channel
      • rjhunter has quit
      • looks like it might be PAM related
      • lsm5
        tianon: credit to alexlarsson for 80-docker.rules
      • tianon
        PAM in 13.10 doesn't need udev or something, does it?
      • lsm5: ah :) well then I'll ask him if we can steal it to share with everyone :D
      • alexlarsson: can I push your 80-docker.rules into contrib for all to share and enjoy? :)
      • zz_johncosta is now known as johncosta
      • lsm5
        tianon: sure thing, I don't think he'll object :)
      • tianon
        haha ok :)
      • I'm stoked, that was one of the few "user oddness" issues I had left with 0.7, but didn't have any idea where to even start looking to fix it :)
      • now that I see 80-docker.rules, it's bleeding obvious :)
      • johncosta is now known as zz_johncosta
      • crosbymichael
      • tianon
        hahaha
      • rjhunter joined the channel
      • crosbymichael is now known as zz_crosbymichael
      • rjhunter has quit
      • zz_crosbymichael is now known as crosbymichael
      • rhunter joined the channel
      • rhunter has quit
      • titanous has quit
      • lsm5
        tianon: btw, did you get a chance to check if 80-docker.rules works fine on rhel/epel ?
      • crosbymichael is now known as zz_crosbymichael
      • rjhunter joined the channel
      • rjhunter has quit
      • proppy
        paultag: did you reboot the debian packaging?
      • proppy: thanks for getting http://bugs.debian.org/cgi-bin/bugreport.cgi?bu... taken care of
      • plietar joined the channel
      • plietar
        I'm trying to run the tests on an unmodified codebase, but it fails during integration
      • Any ideas ?
      • I get "go build github.com/dotcloud/docker: signal: killed"
      • rjhunter joined the channel
      • rjhunter has quit
      • ldlework
        Anyone familiar with the index code around?
      • Alternatively, anyone familiar with Docker itself, how does docker determine the ordering of images?
      • rjhunter joined the channel
      • rjhunter has quit
      • fkautz
        ldlework: what do you mean by the ordering of images?
      • rogaha joined the channel
      • ldlework
        Like when you push up an image to the index, it just submits a list of images. Are those ordered in terms of ancestry? The index doesn't receive any ordering information about what is the latest image layer. Basically, what I'm asking is, when docker pulls a new image from the index and registry, how does it determine which image is the 'latest'?
      • tianon
        lsm5: I tested it on Gentoo with udisks1 - you've got to change the name of the ENV variable with udisks1, but it works fabulously, so I'm going to add both versions to contrib labelled appropriately
      • ldlework
        fkautz: if you docker-inspect an image, it'll tell you the parent. the registry has an endpoint, get ancestry. I'm just wondering where the parent association is first made.
      • And whether that information is sent to the index, or just the registry.
      • rjhunter joined the channel
      • Ah it looks like docker sends the parent id when it pushes up an image.
      • It'd be really useful to know if docker sends that information to the index as well.
      • rjhunter has quit
      • scottstamp is now known as zz_scottstamp
      • rogaha has quit
      • zz_crosbymichael is now known as crosbymichael
      • fkautz
        ldlework: that information is sent as metadata, basically, the repository info is sent up which includes the repo name, tag and image name
      • crosbymichael
        how can something be sent to the index and not registry. the index is just a ui and user management over the registry
      • fkautz: you going to be at docker on Tuesday ?
      • ldlework
        crosbymichael: the other way around, I'm wondering if the parent ids are sent to the registry but not the index. I'm not actually insinuating that the parent ids are not sent to the index, just wondering if they are.
      • The index does not handle the parent ID of an image at all, so I was just wondering of that information is sent to it.
      • ldlework doesn't quite know his way around the docker codebase yet
      • crosbymichael
        if you need help just ask, i know all
      • ldlework
        crosbymichael: sure; when docker sends the list of images to push up to a repository, does it send the parent ID along with every image (allowing the index to assemble the correct ancestry ordering of the images)
      • Does it send the parent ids of each image, when pushing initially to the index, I mean.
      • crosbymichael
        look in registry/registry.go
      • ldlework
        crosbymichael: is the idea that the index simply implements a subset of the registry api, and at some point, the index returns actual registry endpoints in the X-Docker-Endpoints header?
      • rogaha joined the channel
      • In other words, is there no distinction between index and registry from Docker's perspective?
      • crosbymichael
        its the same
      • ldlework
        crosbymichael: I have another question. When you tag an image foo/bar, are you really tagging it foo/bar:latest?
      • crosbymichael
        if you dont specify a tag, yes
      • rogaha has quit
      • fkautz
        crosbymichael: not sure yet
      • my schedule has been quite hectic recently
      • rjhunter joined the channel
      • rjhunter has quit
      • zz_scottstamp is now known as scottstamp
      • rjhunter joined the channel
      • rjhunter has quit
      • vpavlin joined the channel
      • rogaha joined the channel
      • rogaha has quit
      • rogaha joined the channel
      • rjhunter joined the channel
      • rjhunter has quit
      • rogaha_ joined the channel
      • rogaha has quit
      • scottstamp is now known as zz_scottstamp
      • rogaha_ has quit
      • rogaha joined the channel
      • jpetazzo is now known as zz_jpetazzo
      • vpavlin has quit
      • vpavlin joined the channel
      • rogaha_ joined the channel
      • rogaha has quit
      • dockerbot joined the channel
      • dockerbot
        [docker] chilicat opened pull request #2976: Fixes: Building docker in Virtualbox fails (master...patch-2) http://git.io/xkAQQw
      • dockerbot has left the channel
      • rjhunter joined the channel
      • rogaha_ has quit
      • rogaha joined the channel
      • rogaha has quit
      • backjlack joined the channel
      • backjlack has quit
      • lucapette joined the channel
      • backjlack joined the channel
      • gigetoo has quit
      • gigetoo joined the channel
      • crosbymichael is now known as zz_crosbymichael
      • rjhunter has quit
      • zz_crosbymichael is now known as crosbymichael
      • zz_johncosta is now known as johncosta
      • crosbymichael is now known as zz_crosbymichael
      • rjhunter joined the channel
      • rjhunter has quit
      • lucapette has quit
      • zz_crosbymichael is now known as crosbymichael