[09:08] <JamesTait> Good morning all; happy Friday, and happy Siblings Day! :-D
[10:58] <sergiusens> mvo: it's frameworks (list versus string)
[10:58] <sergiusens> mvo: I was going to fix last night but got distracted fixing other things
[10:58] <mvo> sergiusens: yeah, fixed
[10:58] <mvo> sergiusens: no worries
[10:58] <sergiusens> mvo: just removed the line a suppose
[11:11] <sergiusens> mvo: btw, mind looking at my latest u-d-f mps?
[11:11] <mvo> sergiusens: yeah, just removed it
[11:11] <mvo> sergiusens: sure, do you have a url?
[11:11] <mvo> sergiusens: I will need lunch first though
[11:13] <sergiusens> pitti: fwiw, was just trying to know the status on ntp, not sure you were on top of it or who was
[11:14] <sergiusens> mvo: https://code.launchpad.net/goget-ubuntu-touch/+activereviews
[11:14] <pitti> sergiusens: we have timesyncd enabled by default now, AFAIK that was the intended ntp client for snappy?
[11:14] <sergiusens> mvo: the ones from les that 24hrs ago :-)
[11:14] <sergiusens> pitti: oh, it is, great!
[12:58] <lool> sergiusens: how do I use your new beaglebone snap straight from the store?
[13:03] <sergiusens> lool: call it by name
[13:03] <sergiusens> lool: e.g.; beagleboneblack.sergiusens
[13:03] <sergiusens> --oem beagleboneblack.sergiusens
[13:08] <lool> sergiusens: sudo ubuntu-device-flash core \ --platform am335x-boneblack \ --size 4 \ --oem beagleboneblack.sergiusens --developer-mode --channel=ubuntu-core/devel-proposed -o bbb.img
[13:09] <sergiusens> lool: --size is 4 by default
[13:10] <sergiusens> lool: just sudo ubuntu-device-flash core --output bbb.img --channel edge --oem beagleboneblack.sergiusens is enough
[13:10] <sergiusens> lool: I tried to apply sane defaults everywhere to type less
[13:22] <lool> sergiusens: what defines "edge" as a channel?
[13:24] <lool> sergiusens: and how does it figure --platform am335x-boneblack?
[13:25] <lool> (I'd like to do the same for pi)
[13:25] <lool> ok, found channel maps
[13:26] <sergiusens> lool: platform is in the oem snap
[13:26] <sergiusens> lool: the channel maps is a shorthand, (and some form of consistency with the snappy tool)
[13:27] <lool> it kind of feels bad to have this in the tool rather than as server side aliases, but I can see why it's handier for now
[13:29] <beuno> lool, sergiusens, started working on a spec: https://docs.google.com/document/d/1-BFwOcM7yq3feowdAL9SVW5UZkNHiE0q3duXBMUkkyY/edit
[13:30] <sergiusens> lool: I was waiting for the system image rename to happen to make this easier
[13:31] <lool> beuno: I guess you've already seen the naming of the chrome release channels
[13:31] <lool> https://www.chromium.org/getting-involved/dev-channel
[13:31] <lool> it seems we have the same number of channels, but with different names
[13:31] <lool> (that's fine of course)
[13:33] <beuno> lool, we have 1 more!  :)
[13:33] <beuno> anyway, its subject to change, it captures the discussions we've had so far
[13:35] <lool> (RaspberryPi2)ubuntu@localhost:~$ sudo snappy install docker_1.5.0.001_multi.snap
[13:35] <lool> Installing docker_1.5.0.001_multi.snap
[13:35] <lool> 2015/04/10 13:34:53 Signature check failed, but installing anyway as requested
[13:35] <lool> mkdir /apps/docker/1.5.0.001/meta/framework-policy: permission denied
[13:35] <lool> unpack docker_1.5.0.001_multi.snap to /apps/docker/1.5.0.001 failed with exit status 1
[13:35] <lool> kickinz1: ^
[13:35] <lool> mvo: ^ does the above sound familiar (snappy go version on image 220 on rpi2)
[13:36] <fionnan> I'm trying to get docker to load a dockerfile on snappy but get the error `2015/04/10 13:32:38 open dockerfile.tar: permission denied` when I try to do it as the ubuntu user and get `sudo: docker: command not found` when I do it with sudo, anyone have any ideas what I could be doing wrong?
[13:37] <kickinz1> fionnan, you need to have your Dockerfile in /home/ubuntu/apps/docker/1.3.xxx/
[13:37] <fionnan> if anyone knows of any docs about using docker on snappy would be great too, I can't seem to find anything :(
[13:38] <fionnan> kickinz1: cool, thanks!
[13:38] <kickinz1> then in this dir you run docker buid...
[13:38] <sergiusens> lool: I think Chipaca is dealing with this
[13:38] <Chipaca> sergiusens: with what?
[13:39] <lool> Chipaca: see above error when installing docker
[13:39] <kickinz1> lool, hdstrand had this yesterday evening, but it was related to a bad docker-daemon.apparmor.
[13:39] <lool> 15:35 < lool> mkdir /apps/docker/1.5.0.001/meta/framework-policy: permission denied
[13:39] <lool> 15:35 < lool> unpack docker_1.5.0.001_multi.snap to /apps/docker/1.5.0.001 failed with exit status 1
[13:39] <fionnan> kickinz1: that fixed it!
[13:39] <lool> kickinz1: I've built the rootfs minutes ago against devel-proposed; how do I get the fix?
[13:39] <Chipaca> lool: that does not look like something i'm doing, no
[13:39] <Chipaca> lool: why did you get permission denied on mkdir?
[13:40] <kickinz1> lool: I will upload a more recent one for you to test, but the one I sent to you was supposed to work
[13:40] <Chipaca> ooh, wait, that might be me
[13:40]  * Chipaca looks a bit deeper
[13:40] <sergiusens> mvo: jodh I got this weird problem when upgrading from d-p to devel-proposed http://paste.ubuntu.com/10791611/
[13:41] <lool> kickinz1: I have beagle up too
[13:41] <Chipaca> lool: so, that error itself is not me afaict, but i'd be interested in knowing how you got there
[13:41] <lool> ubuntu-core     2015-04-10 220
[13:41] <Chipaca> lool: are the permissions in the docker tar wrong?
[13:41] <lool> Chipaca: I dont know, I can check
[13:42] <Chipaca> lool: please
[13:42] <lool> Chipaca: look alright to me
[13:42] <lool> Chipaca: http://paste.ubuntu.com/10791622/
[13:43] <Chipaca> yep, those lok alright
[13:43] <Chipaca> look*
[13:45] <Chipaca> lool: do you have anything in dmesg?
[13:45] <sergiusens> Chipaca: remember that snappy calls unpack with reduced privs
[13:46] <Chipaca> sergiusens: but i don't see any reason for a mkdir at random to fail on unpack, which is what's reported here
[13:48] <jodh> sergiusens: it's an upgrader bug resulting from the recent rework. Fixing...
[13:50] <Chipaca> lool: so, i don't know where/how you're trying to make that work, but i just tested the docker thing locally and it installed without a hitch
[13:50] <Chipaca> lool: so i'd really like to know more :)
[13:50] <lool> [   64.460170] audit: type=1400 audit(1428673111.960:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="system-status.victor_system-status_1.0.3" pid=805 comm="apparmor_parser"
[13:50] <lool> [   66.848594] audit: type=1400 audit(1428673114.348:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="pastebinit.mvo_pastebinit_1.4.0.0.1" pid=805 comm="apparmor_parser"
[13:51] <lool> [   86.906565] audit: type=1400 audit(1428673134.408:8): apparmor="DENIED" operation="capable" profile="system-status.victor_system-status_1.0.3" pid=884 comm="system-status" capability=12  capname="net_admin"
[13:51] <lool> are the only dmesg bits
[13:51] <Chipaca> lool: dmesg -T will give you saner timestamps, for next time :)
[13:51] <Chipaca> none of those seem relevant to docker
[13:51] <lool> good to know
[13:51] <lool> Chipaca: no
[13:52] <lool> Chipaca: would also be surprized that snappy install would run confined
[13:52] <lool> so mkdir failing is weird
[13:52] <lool> Chipaca: I'll test on BBB in a few, with an updated snap
[13:53] <Chipaca> lool: what are you testing on, here?
[13:53] <lool> Chipaca: oh sorry, dmesg is from wrong board
[13:53] <Chipaca> lool: is this the same vm that was saying "no space left on device"?
[13:53] <lool> I actually reinstalled since
[13:54] <lool> Chipaca: so yes, it is from same vm
[13:54] <lool> Chipaca: and I think the issue is missing modules
[13:54] <lool> [Fri Apr 10 13:00:10 2015] systemd-journald[458]: Failed to create new runtime journal: No space left on device
[13:54] <lool> probably lack of tmpfs
[13:54] <lool> right, lsmod is empty
[13:54] <lool> the modules are there in rootfs, but not initrd
[13:54]  * lool goes updating
[13:55] <Chipaca> lool: so it looks like that vm is otherwise fubar'ed
[13:56] <lool> yeah
[13:56] <Chipaca> lool: if you can reproduce the issue with a vm that is not already broken let me know :)
[13:56] <Chipaca> i really think we need a "sanity check" command in snappy
[13:56] <Chipaca> ... but there's so much more stuff we need :)
[14:02] <lool> bah I foobarded the initrd
[14:06] <lool> /sbin/udevadm: line 2: ��HL�F�k���@�������
[14:06] <lool> somehow not good
[14:06] <lool> /sbin/udevadm: line 1: ELF: not found
[14:08] <lool> ppisati: sorry, mind reminding me how to properly repack initrd? I gunzip-ed | cpio -i, and am repacking with find . | cpio --quiet --dereference -o -H newc | lzma -7 > ../new-initrd.lz
[14:08] <lool> well, I'll start with gzip
[14:08] <eltigre> is it possible to develop/tinker on snappy core on raspberry pi without a second raspberry pi running ubuntu?
[14:12] <ogra_> lool, abootimg-unpack-initrd ... abootimg-pack-initrd
[14:12] <ogra_> we have helpers for this ;)
[14:15] <lool> ok, managed to repack initrd
[14:15] <lool> ogra_: thanks
[14:15] <lool> it was actually my unpacking which was incorrect
[14:15] <lool> (forgot -d to cpio)
[14:15] <lool> I still get [   50.591157] systemd-journald[399]: Failed to create new runtime journal: No space left on device
[14:17] <lool> ppisati: so for some reason the modules dep were out of date
[14:22] <lool> I still get the dreaded [   50.525271] systemd-journald[332]: Failed to create new runtime journal: No space left on device
[14:22] <eltigre> I don't see any information about "cross compiling" or porting applications to raspi/snappy, so maybe it isn't that easy
[14:23] <lool> eltigre: http://hypernephelist.com/2015/03/09/cross-compilation-made-easy-on-ubuntu-with-sbuild.html
[14:23] <lool> eltigre: it depends *what* you're cross-compiling though
[14:23] <lool> eltigre: I typically did all the MWC snaps with cross-compilation
[14:24] <lool> go / C / C++ ones mainly
[14:24] <lool> but sometimes it can be a pain
[14:24] <eltigre> I would be using python
[14:24] <lool> eltigre: are there native bits?
[14:24] <eltigre> I think I will go the raspbian route for the foreseeable future
[14:24] <eltigre> maybe
[14:25] <lool> eltigre: I'm not sure why it would be any easier with raspian
[14:25] <eltigre> it's pretty easy to run into C extensions you didn't expect in Python nowadays
[14:25] <lool> *raspbian
[14:25] <eltigre> it compiles stuff
[14:25] <eltigre> slowly, but it does
[14:25] <eltigre> and it has a package manager, unlike snappy
[14:25] <lool> we do have a package manage, it's snappy!  :-)
[14:26] <eltigre> no, that's an application manager
[14:26] <lool> eltigre: right, we dont have snaps for a build environment
[14:26] <eltigre> the difference being that you have to somehow get your dependencies in the app itself, as far as I understand it
[14:26] <lool> that's right
[14:27] <lool> kickinz1: ok, I managed to install docker on rpi2 now
[14:27] <eltigre> which is on one hand a very good idea, but on the other... well... unfamiliar and currently much more work
[14:27] <lool> eltigre: I think that's about right
[14:28] <lool> it's less familiar and more work right now
[14:28] <lool> but it pays off in the end
[14:28] <lool> eltigre: you can have an Ubuntu chroot on a snappy install where you do the builds
[14:28] <kickinz1> lool: ok, I have a new package for you then.
[14:28] <lool> or a qemu-arm schroot on your desktop (above blog post) or cross-build stuff
[14:28] <eltigre> problem is, I'm not that familiar with the chrooting stuff... I hardly even grokked docker
[14:28] <lool> eltigre: now specifically for python, you'd want to grab barry who's worked exactly on this topic
[14:29] <lool> eltigre: https://lists.ubuntu.com/archives/snappy-devel/2015-April/000428.html
[14:29] <eltigre> thanks
[14:30] <lool> kickinz1: does it intentionally have the exact same name as the previous one?
[14:31] <lool> 2015/04/10 14:31:01 Signature check failed, but installing anyway as requested
[14:31] <lool> open /apps/docker/1.5.0.001/meta/docker-daemon.seccomp: permission denied
[14:31] <lool> unpack docker_1.5.0.001_multi (1).snap to /apps/docker/1.5.0.001 failed with exit status 1
[14:31] <jdstrand> that's weird
[14:31] <lool> kickinz1, jdstrand: The older snap installs fine though
[14:32] <jdstrand> lool: this might be because you are installing the same version over other?
[14:32] <kickinz1> lool: on bbb?
[14:32] <lool> kickinz1: both on rpi2
[14:32] <lool> jdstrand: maybe
[14:32] <lool> jdstrand: I had snappy removed though
[14:32] <jdstrand> lool: what is ls -l /apps/docker/1.5.0.001/meta/
[14:33] <lool> right now after successful install of old snap: http://paste.ubuntu.com/10791980/
[14:33]  * lool removes
[14:33] <jdstrand> that looks fine
[14:33] <lool> now /apps/docker exists but is empty
[14:33] <jdstrand> lool: do ls -l after removal too
[14:34] <jdstrand> ok, that is what I've seen
[14:34] <lool> now installing again the new one
[14:34] <lool> I've renamed it to drop the " (1)" in the filename
[14:34] <lool> ah that worked
[14:34] <lool> jdstrand: was just a filename issue
[14:34] <jdstrand> ok cool
[14:35] <lool> now I got http://paste.ubuntu.com/10791992/
[14:35] <kickinz1> jdstrand seems ok on bb for me
[14:35] <lool> kickinz1: ok, installed latest snap on pi2; what do I confirm?
[14:36] <kickinz1> lool: docker run -it armbuild/ubuntu
[14:36] <kickinz1> on the container just try some things like: "apt-get update && apt-get upgrade"
[14:36] <lool> FATA[0000] Post http:///var/run/docker.sock/v1.17/containers/create: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS?
[14:36] <kickinz1> then docker stop "id of the container"
[14:37]  * lool removes docker, and grabs latest package
[14:37] <kickinz1> lool, sudo systemctl status docker_docker-daemon_1.5.0.001.service
[14:38] <lool> kickinz1: switching to your latest snap first
[14:38] <kickinz1> lool ok
[14:39] <lool> installing
[14:40] <lool>   Process: 1347 ExecStop=/apps/docker/1.5.0.001/bin/docker.stop (code=exited, status=0/SUCCESS)
[14:40] <lool>   Process: 1319 ExecStart=/apps/docker/1.5.0.001/bin/docker.start (code=exited, status=1/FAILURE)
[14:41] <kickinz1> lool, can you paste the tailed output of "sudo journalctl -l"
[14:41] <jdstrand> lool: you may have a stray docker running from before
[14:42] <lool> kickinz1: cloud-init stuff only
[14:42] <lool> jdstrand: yeah, that's what I think too
[14:43] <lool> I dont see it in ps though
[14:43]  * lool reboots
[14:45] <lool> uh -bash: docker: command not found
[14:46] <lool>    Loaded: not-found (Reason: No such file or directory)
[14:47] <lool> I dont see the systemd service file under /etc/systemd/system
[14:51] <lool> ok. trying BBB now
[14:51] <lool> ok, docker is running
[14:51] <lool> $ docker run -it armbuild/ubuntu
[14:51] <lool> Unable to find image 'armbuild/ubuntu:latest' locally
[14:51] <lool> Pulling repository armbuild/ubuntu
[14:52] <lool> it's doign stuff
[14:52] <lool> kickinz1: So not tested in full on BBB, but seems mostly working
[14:52] <kickinz1> lool, ok, thanks!
[14:53] <lool> would love some help debugging the isuse on rpi2
[14:53] <lool> I'm removing docker snap, will search for stray files, and reboot
[15:01] <lool>    Active: failed (Result: exit-code) since Fri 2015-04-10 15:01:17 UTC; 13s ago
[15:01] <lool>   Process: 1033 ExecStopPost=/apps/docker/1.5.0.001/bin/docker.poststop (code=exited, status=0/SUCCESS)
[15:01] <lool>   Process: 1003 ExecStart=/apps/docker/1.5.0.001/bin/docker.start (code=exited, status=1/FAILURE)
[15:02] <lool> /apps/docker/1.5.0.001/bin/docker.start: line 14: /home/ubuntu/etc/docker.conf: No such file or directory
[15:02] <lool> /apps/docker/1.5.0.001/bin/docker.start: line 32: docker: command not found
[15:03] <lool> FATA[0000] open /var/run/docker.pid: permission denied
[15:05] <lool> jdstrand: what's the magic to force regenerating the profiles? probably because I installed multiple snaps with same version
[15:05] <lool> [Fri Apr 10 15:04:36 2015] audit: type=1400 audit(1428678276.674:17): apparmor="DENIED" operation="mknod" profile="docker_docker_1.5.0.001" name="/run/docker.pid" pid=1185 comm="docker.armhf" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
[15:05] <jdstrand> lool: sudo aa-clickhook -f ; sudo aa-profile-hook -f
[15:05] <lool> thanks
[15:06] <lool> jdstrand: I still get: [Fri Apr 10 15:05:58 2015] audit: type=1400 audit(1428678358.915:21): apparmor="DENIED" operation="mknod" profile="docker_docker_1.5.0.001" name="/run/docker.pid" pid=1209 comm="docker.armhf" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
[15:06] <jdstrand> kickinz1: ah-- ^
[15:06] <lool> that's only on pi2 though
[15:06] <jdstrand> we have this rule:
[15:06] <jdstrand> /run/@{APP_PKGNAME}.pid rw,
[15:07] <lool> jdstrand: note that I'm running this by hand because the job fails to start
[15:07] <jdstrand> but APP_PKGNAME is 'docker-daemon'
[15:07] <lool> aha
[15:07] <kickinz1> jdstrand, I don't understand how it works on bbb as it is also running docker.armhf.
[15:08] <jdstrand> that isn't the part
[15:08] <jdstrand> name="/run/docker.pid"
[15:08] <jdstrand> we have:
[15:08] <jdstrand> @{APP_APPNAME}="docker-daemon"
[15:08] <jdstrand> /run/@{APP_PKGNAME}.pid rw,
[15:08] <jdstrand> oh wait
[15:08] <jdstrand> no, that is right, I misread it
[15:09] <lool> [Fri Apr 10 15:07:34 2015] device-mapper: table: 254:0: thin-pool: unknown target type
[15:09] <lool> [Fri Apr 10 15:07:34 2015] device-mapper: ioctl: error adding target to table
[15:09] <lool> that seems to be the actual error from the job
[15:09] <lool> ppisati: ^
[15:09] <jdstrand> oh this is the docker command
[15:09] <jdstrand> kickinz1: hold on
[15:10] <lool> jdstrand: I suspect it's non-fatal
[15:10] <jdstrand> yes
[15:10] <jdstrand> it is
[15:10] <lool> so annoying, but systemd cleans things up
[15:10] <ppisati> it refers to this: drivers/md/dm-thin.c:
[15:10] <jdstrand> interesting that amd64 didn't need it
[15:11] <lool> ppisati: is it built in your rpi2 kernel?
[15:11] <ppisati> lool: do you have that module?
[15:11] <ppisati> no idea
[15:11] <lool> ppisati: what's the module name?
[15:12] <lool> DM_THIN_PROVISIONING
[15:12] <lool> ppisati: # CONFIG_DM_THIN_PROVISIONING is not set
[15:12] <lool> ppisati: I blame it all on you!
[15:12] <ppisati> obj-$(CONFIG_DM_THIN_PROVISIONING)      += dm-thin-pool.o
[15:12] <ppisati> :)
[15:12] <lool> ppisati: could you make sure this is part of our "Ubuntu standard options that always turned on"?
[15:12] <ppisati> YES YES WHIP ME WHIPE!!! :D
[15:13] <ppisati> yeppa
[15:13] <ppisati> i can kick a new build
[15:13] <ppisati> right now
[15:13] <lool> ppisati: and coud you rebuild a rpi2 kernel with all interesting options we usually want turned on?
[15:13] <lool> thanks
[15:13] <ppisati> lool: we already have all the interesting options turned on
[15:13] <ppisati> lool: this one wasn't part of it
[15:13] <lool> kickinz1: so I think we wont hit the time for the pi2 demo, but we at least know how to get there and we seem close enough that we would have one, say, monday
[15:13]  * ppisati goes and kick a new build
[15:13] <jdstrand> lool: when did you see that? when the service was correctly running or when it wasn't?
[15:13] <lool> jdstrand: that was on the rpi2
[15:14] <jdstrand> was docker-daemon running?
[15:14] <lool> jdstrand: trying to run the service by hand to trigger
[15:14] <lool> jdstrand: no
[15:14] <jdstrand> ah
[15:14] <jdstrand> right, then that is correctly denied
[15:14] <lool> jdstrand: actually on BBB I see *nothing*
[15:14] <lool> jdstrand: so I guess it's not something you'd want to worry about
[15:15] <lool> I guess side effect of me launching teh job by hand somehow
[15:15] <jdstrand> lool: to start by hand, do sudo aa-exec -p docker_docker-daemon_1.5.0.001 -- /apps/docker/current/bin/docker.armhf ...
[15:15] <lool> thanks
[15:16] <jdstrand> lool: if you use 'docker' by hand, you get the 'docker cli command' and policy from /apps/bin
[15:16] <lool> thanks
[15:16] <jdstrand> lool: but you want to run docker as a daemon, so you need to start it under that profile
[15:16] <jdstrand> kickinz1: nothing to be done
[15:16] <jdstrand> at least policy wise
[15:16] <lool> ppisati: poke when you have a new PPA kernel, I'll update my device tarball with it
[15:16] <ppisati> lool: yep
[15:17] <lool> ppisati: I can update the initrd too; not quite sure how to generate the modules dep without booting a pi2 and running depmod -a though
[15:17] <ppisati> lool: but do you actually need the modules during boot? i don't think so
[15:18] <lool> ppisati: I dont think so, but I'm trying to keep them up-to-date nevertheless
[15:18] <lool> ppisati: besides, I'm including the deps in the device tarball rootfs part
[15:25] <mvo> jdstrand: thanks again for the pointer to the unconfined profile, I created http://paste.ubuntu.com/10792277/ now, but it seems it does not like the last line I added "change_profile" - is the syntax here different?
[15:27] <mvo> jdstrand: aha, it seems like "change_profile -> *" is the right one (?)
[15:27] <jdstrand> change_profile -> *,
[15:27] <mvo> thanks! that helped me a lot
[15:27]  * mvo hugs jdstrand
[15:27] <jdstrand> but, if you did want to confine this, you can do stuff like
[15:27] <jdstrand> change_profile -> docker_*,
[15:27]  * jdstrand hugs mvo back :)
[15:28] <asac> ogra_: around?
[15:28] <ogra_> asac, in a meeting, but around, yeah
[15:28] <asac> ogra_: can you check in on #snappy-internal ?
[15:28] <asac> for a moment
[15:32] <kirkland> ogra_: hi, I'm here
[15:32] <ogra_> hey kirkland
[15:33] <kirkland> ogra_: okay, we're getting started
[15:41] <ppisati> lool: it's baking - https://launchpad.net/~p-pisati/+archive/ubuntu/embedded/+packages
[15:49] <jdstrand> beuno: hey, so in the store, you can upload a snap but there is no way to choose an architecture any more?
[15:49] <jdstrand> beuno: kickinz1 is uploading docker and in the yaml it has: architecture: [amd64, armhf]
[15:50] <jdstrand> beuno: that's fine. but then it comes up as arch all in the store, but it isn't 'all', it is 'multi' and only 'multi' for two archs, not all of them
[15:52] <ppisati> jdstrand: same error i had for wget
[15:52] <jdstrand> interesting
[15:53] <jdstrand> maybe the store needs a little tweaking
[16:22] <jdstrand> beuno (and kickinz1 and ppisati): I adjusted the review tools to match what the store is currently doing so this shouldn't happen again
[16:23] <jdstrand> well, once the store is updated
[16:23] <kickinz1> jdstrand, ok thanks
[16:25] <ppisati> jdstrand: what are these tools?
[16:26] <jdstrand> ppisati: they are the things that run during snappy build and what runs on the server
[16:26] <jdstrand> lp:click-reviewers-tools
[16:27] <ppisati> jdstrand: jdstrand that means i shall rebuild and resubmit? or do i still need for a store update? i guess the latter
[16:27] <ppisati> *need to wait
[16:29] <jdstrand> ppisati: no, you don't need to do anything
[16:29] <jdstrand> the next time you upload, if the store has pulled in my change, you won't have that review tool error
[16:34] <kirkland> ubuntu@localhost:~$ sudo snappy update
[16:34] <kirkland> ubuntu-core    124 MB     [[16:34] <kirkland> I've been stuck after that for 10+ minutes now
[16:34] <kirkland> help?
[16:35] <kickinz1> kirkland on which board?
[16:35] <kirkland> kickinz1: rpi2
[16:35] <kickinz1> channel is devel-proposed?
[16:35] <kirkland> kickinz1: how can I tell?
[16:36] <kickinz1> kirkland: I don't have rpi2, sorry
[16:36] <kirkland> kickinz1: how can I tell what channel?
[16:36] <kickinz1> kirkland: cat/etc/syste-image/channel.ini
[16:36] <kirkland> okay, it's applying now
[16:36] <kickinz1> kirkland: if channel is ubuntu-core/devel
[16:37] <kickinz1> kirkland, you will need to 'sudo mount -o remount rw /'
[16:37] <kickinz1> kirkland, change channel to ubuntu-core/devel-proposed, then reboot, then update
[16:38] <kickinz1> kirkland, but from me it is theory (as done on bbb), better have an anwer from an rpi2 owner
[16:39] <kirkland> kickinz1: okay
[16:39] <kirkland> kickinz1: can I just snappy install docker now?
[16:39] <kickinz1> kirkland, if on new image : yes
[16:40] <kirkland> kickinz1: okay, i'm updated now, rebooting
[16:40] <kirkland> kickinz1: where can I just download the latest rpi2 image now?
[16:40] <kickinz1> kirkland, but I don't know the status of docker on rpi2, I didn't get updates on that
[16:42] <kickinz1> kirkland, what 'snappy list' looks like?
[16:42] <kirkland> snappy: error: invalid choice: 'list' (choose from 'info', 'versions', 'search', 'update-versions', 'update', 'rollback', 'install', 'uninstall', 'tags', 'config', 'build', 'booted', 'chroot', 'framework', 'fake-version', 'nap')
[16:42] <kickinz1> kirkland, ok old image
[16:43] <kirkland> kickinz1: where can I get the new image?
[16:43] <kirkland> kickinz1: why didn't snappy update get me the new image?
[16:43] <kickinz1> kirkland, cause latest image is not yet promoted
[16:43] <kickinz1> kirkland, I would go for channel change/ or backup solution is to use a docker-1.5.0-armhf for old image
[16:44] <kirkland> kickinz1: channel: ubuntu-core/devel
[16:44] <kickinz1> jdstrand, asac, ^
[16:45] <kickinz1> kirkland, try this package:  https://mifamofi.net/owncloud/public.php?service=files&t=c2d37c5711ef8b323ac3da519142e21d
[16:45] <sergiusens> kickinz1: kirkland rpi has no upgrade path until we have a proper kernel in our repos
[16:45] <jdstrand> kirkland: someone said earlier it took 20 minutes
[16:45] <kirkland> kickinz1: okay, I'm on devel-proposed now
[16:45] <jdstrand> ok good
[16:45] <jdstrand> if on devel-proposed, use the store
[16:45] <asac> kirkland: lool has made an image prebuilt for you
[16:46] <kirkland> asac: link?
[16:46] <asac> in your inbox ;)
[16:46]  * asac looks it up
[16:46] <sergiusens> he sent an email
[16:46] <kirkland> got it
[16:46] <asac> kirkland: you cnanot update on the pi2 from alpha2 or even after because its nota  certified enablement
[16:46] <asac> so just install the one you have
[16:47] <asac> new builds at least dont try to update
[16:48] <kirkland> 	custom.img	09-Apr-2015 16:01	3.6G
[16:48] <asac> kirkland: wget http://people.canonical.com/~lool/pi2-device-and-oem/custom.img
[16:48] <asac> dd it
[16:48] <asac> yeah
[16:48] <kirkland> asac: I don't have enough bandwidth to pull that here
[16:48] <asac> kirkland: ok i can xz it
[16:48] <asac> one moment
[16:49] <asac> lool: i have to wget that because you are not on lillypitty?
[16:50] <asac> weird
[16:50] <asac> or you have weird permissions
[16:50] <asac> lool: could you .xz this ... assuing it will be popular for the moment?
[16:50] <asac> and put checksums ni place
[16:52] <asac> kirkland: i am xz'ing here rifght now: http://people.canonical.com/~asac/tmp/pi2/
[16:52] <asac> takes a it
[16:52] <asac> bit
[16:55] <jdstrand> asac: you don't have to wget it
[16:55] <asac> i couldnt copy it from ~lool
[16:55] <jdstrand> I logged into lillypilly and can see it
[16:56] <asac> lool has always special permissions
[16:56] <asac> hehe
[16:56] <asac> ok
[16:56] <jdstrand> I didn't try copying
[16:56] <asac> maybe i mistyped
[16:56] <asac> but i have it now anyway
[16:56] <jdstrand> ok
[16:56] <ogra_> "french permissions"
[16:56] <jdstrand> hehe
[16:59] <asac> man xz is so slow
[16:59] <asac> i thinkk my 3.6G wget will finish before it finish packing
[17:02] <kirkland> asac: okay, thanks
[17:02] <kirkland> asac: is ogra_ still around, or gone?
[17:02] <kirkland> asac: we're also trying the node-snapper stuff right now
[17:02] <ogra_> kirkland, i'm here
[17:02] <kirkland> ogra_: alright!!!
[17:03] <ogra_> kirkland, moving to the living room though ... i.e. no internal channels anymore :)
[17:03] <kirkland> ogra_: can you post your metadata.yaml from your node-snapper example?
[17:03] <asac> lool: http://people.canonical.com/~asac/tmp/pi2/custom.img.xz
[17:03] <asac> i think its fine
[17:03] <asac> kirkland: http://people.canonical.com/~asac/tmp/pi2/custom.img.xz
[17:03] <asac> err its finished
[17:03] <asac> i will try too now
[17:04] <asac> guess my bandwidth is faster so i know if it doesntw ork beffore you
[17:04] <asac> kirkland: ogra will be around if you continue to engage him :)
[17:04] <kirkland> asac: awesome, thanks
[17:04] <asac> he is just sometimes falling asleep if he is idling too long :P
[17:04] <kirkland> http://paste.ubuntu.com/10792912/
[17:04] <kirkland> docker failed to install here ^
[17:05] <asac> kirkland: on what machine?
[17:05] <asac> what image?
[17:05] <kirkland> asac: rpi2, devel-proposed, up to date
[17:05] <kirkland> asac: I'm downloading your custom.img now
[17:05] <asac> kirkland: how did you get it up tod date?
[17:05] <asac> i dont think you can have that
[17:05] <kirkland> asac: arg
[17:05] <asac> because update doesnt work on pi2 by design
[17:05] <asac> i think you have it just on the other partition, but still boot in the old one
[17:06] <asac> kirkland: sure it will be better on the lools if its installing on the bbb latest
[17:06] <asac> i am dding that custom one too now... lets see
[17:06] <kirkland> asac: okay, in 7-8 minutes, the download will complete and I can write that image to the sdcard
[17:06] <ogra_> kirkland, sorry, had to re-locate and now i'm missing backlog, you wanted the metadata.yaml ?
[17:07] <kirkland> ogra_: yes, please
[17:07] <asac> yeah i will hopefully be able to confirm by then... though its the first time i put this pi2 in action
[17:07] <sergiusens> beuno: can oem snaps not require "departments" on upload?
[17:07] <kirkland> asac: can you please pastebin it for us?
[17:07] <sergiusens> beuno: and can we have a filter to search for package type?
[17:07] <ogra_> kirkland, hmm, i dont have such a file ... i have a package.yaml though
[17:08] <kirkland> ogra_: yes, that one, please
[17:08] <asac> kirkland: what do you need pastebinit?
[17:08] <kirkland> asac: package.yaml of a nodejs snap
[17:09] <kirkland> asac: sorry, that was for ogra_
[17:09] <asac> right
[17:09] <asac> just wondered :)
[17:09] <asac> ogra_: ^
[17:09] <kirkland> ogra_: can you please pastebin your package.yaml
[17:09] <ogra_> kirkland, http://paste.ubuntu.com/10792959/
[17:10] <ogra_> kirkland, https://code.launchpad.net/~ogra/+junk/chatroom has allteh files btw (linkedfrom the blog)
[17:13] <kirkland> asac: image downloaded
[17:14] <kirkland> ogra_: okay, that branch is missing the arm tarball, right?
[17:14] <kirkland> ogra_: I still need to unzip that?
[17:14] <ogra_> yes, thats only the packaging data
[17:14] <ogra_> the tarballs you crate with node-snapper
[17:14] <ogra_> *create
[17:15] <asac> kirkland: so i dded it
[17:15] <asac> it boots
[17:15] <asac> i am logged in
[17:15] <kirkland> asac: I'm dd'ing now
[17:15] <asac> (RaspberryPi2)ubuntu@localhost:~$
[17:15] <kirkland> asac: can you snappy install docker?
[17:16] <asac> mvo: http://paste.ubuntu.com/10793006/
[17:16] <asac> kirkland: :(
[17:16] <asac> kickinz1: ^^
[17:17] <kirkland> asac: that looks exactly like what I saw before: http://paste.ubuntu.com/10792912/
[17:17] <kickinz1> asac snappy list ?
[17:17] <kickinz1> kirkland, yes but you had a snappy-python image
[17:18] <mvo> asac: uff, let me look
[17:19] <asac> lool: oem snap is also bogus
[17:19] <asac> where is the soruce?
[17:19] <asac> you have the xz data thingy
[17:20] <kickinz1> asac, can you test docker-1.5.0-armhf for old image (https://mifamofi.net/owncloud/public.php?service=files&t=c2d37c5711ef8b323ac3da519142e21d)?
[17:20] <asac> kickinz1: the old image i am not really interested in
[17:20] <asac> many things wont work for folks there
[17:20] <kickinz1> asac, ok sorry...
[17:20] <asac> kickinz1: can you focus on the new one? does the new docker work on the bbb?
[17:21] <asac> the one from store?
[17:21] <kickinz1> asac, yes docker work on bbb from the store
[17:21] <kirkland> asac: dd done
[17:21] <asac> you wont be happy though
[17:21] <kickinz1> asac, and I'm focused on the new image, I was just speaking of a backup on rpi2
[17:21] <asac> i am tewsting now if the bbb works
[17:22] <asac> right, but i think kirkland wont be happy with that because then lots of other issues will pop up
[17:23] <sergiusens> mvo or jdstrand: when you have a minute please https://myapps.developer.ubuntu.com/dev/click-apps/2275
[17:23] <asac> lool: where did you put your oem snap source? that needs to be rebuilt with latest snappy so i can create a new image
[17:24] <asac> mvo: i dont get why docker is in the store as com.ubuntu...
[17:24] <mvo> sergiusens, jdstrand: approved
[17:25] <mvo> asac: me neither
[17:25] <kirkland> asac: that image is not booting for me
[17:25] <sergiusens> asac: I rebuilt lool's pkg here, I can upload it under my namespace for play if you want
[17:25] <asac> kirkland: it does for me thats for sure
[17:25] <asac> kirkland: it takes a while on first boot
[17:25] <asac> because of funky cloud-init
[17:25] <sergiusens> asac: or do it yourself, unpack it (dpkg-deb) and snappy build it again
[17:25] <kirkland> asac: okay, i'll wait a bit
[17:25] <asac> 2-3 minutes
[17:26] <kirkland> asac: hmm, it's been more like 5
[17:26] <asac> sergiusens: i want his .snap on people
[17:26] <asac> sergiusens: not store
[17:26] <asac> or is it in store?
[17:26] <sergiusens> asac: right, but you can dpkg-deb -x it and snappy build it again, it will be very similar if not the same (timestamps differing)
[17:26] <asac> sergiusens: just gimme the new snap
[17:26] <sergiusens> asac: he asked me about that, not sure he uploaded
[17:26] <asac> this one breaks trusty snappy soo i cannot see if a newer image works
[17:27] <asac> its not
[17:27] <asac> at least not as pi2.lool
[17:27] <asac> mvo: well, but why does snappy install docker do the right thing?
[17:27] <asac> do we have an alias there?
[17:27] <asac> kickinz1: how do you upload the docker ?
[17:27] <asac> whats in the metadata>?
[17:27] <asac> you must not use com.ubuntu... anymore
[17:27] <sergiusens> asac: there's the com.ubuntu.snappy hack for the py version in devel
[17:27] <asac> sure
[17:27] <sergiusens> it might be legacy
[17:28] <asac> but it just works here on snappy latest
[17:28] <asac> i type snappy install docker
[17:28] <asac> and it starts downloading com.ubuntu...
[17:28] <asac> so the store must have set an alias
[17:28] <kickinz1> I just went to the store and updated the package from there....
[17:28] <sergiusens> asac: I'm not sure kickinz1 has access to the .canonical part of the store; mvo and I do fwiw
[17:28] <asac> kickinz1: do you have com.ubuntu.... in metadat?
[17:28] <kickinz1> I didn'tknew there was an other way.
[17:28] <kickinz1> asac: packlage.yaml?
[17:28] <asac> yes
[17:29] <asac> anyway
[17:29] <asac> it seems to isntall here on bbb
[17:29] <asac> fwiw
[17:29] <asac> sergiusens: i need the new .snap
[17:29] <asac> it seems that whatever image lool used isnt right
[17:29] <kickinz1> http://paste.ubuntu.com/10793087/
[17:29] <kirkland> asac: unplugged it, and plugged it back in again
[17:29] <asac> kirkland: you have to remember that when dd finishes
[17:29] <asac> you have to wait till IO buffer is done
[17:29] <kirkland> see activity light, but nothing
[17:30] <asac> run sync
[17:30] <kirkland> asac: I ran sync 3 times
[17:30] <asac> ok
[17:30] <asac> thats odd
[17:30] <asac> i had a few time taht a dd didnt work
[17:30] <asac> usually i dded again and then it worked
[17:30] <asac> and i jsut tell yopu that i never used this pi2 and dded it and it booted :)
[17:30] <asac> it took long time before it upped ethernet
[17:31] <asac> then it got network
[17:31] <asac> and then it was there
[17:31] <asac> kirkland: do you have ethernet?
[17:31] <kirkland> yes
[17:31] <asac> ok because until yesterday the image wouldnt boot without network
[17:31] <mvo> fwiw, docker 1.5.0.002 installs fine for me in the latest image
[17:31] <asac> sergiusens: i need snap :)
[17:31] <asac> please!!
[17:31] <asac> lools image is too outdated i am sure :)
[17:32] <sergiusens> asac: uploading, I'm on a slow connection
[17:33] <asac> sergiusens: sorry i rebuilt and now its going
[17:33] <sergiusens> asac: 'dpkg-deb -x pi2*.snap x && snappy build x' might be faster
[17:33] <asac> yeah
[17:33] <asac> that was what i did
[17:33] <sergiusens> ok
[17:33] <sergiusens> I'll brb
[17:33] <asac> sry for moron
[17:33] <sergiusens> got into a coffee shop as rain took me by surprise
[17:33] <sergiusens> asac: lol, no worries
[17:34]  * genii 's ears perk up at the mention of coffee, then he wanders away again
[17:34] <asac> oh coffee ... good idea
[17:34] <asac> :)
[17:34] <sergiusens> asac: I uploaded beagleblack.canonical btw
[17:34] <genii> Heh
[17:34] <asac> but i wait till i know if the new iamge just fixes the docker prob
[17:34] <asac> if dd would just be faster :)
[17:35] <ogra_> we need dd-diff ... that only applies the changed bytes :)
[17:35] <asac> lol
[17:36] <jdstrand> asac: meta/package.yaml is fine
[17:36] <jdstrand> asac: it is that he uploaded to the old namespace in the store
[17:37] <asac> right
[17:37] <asac> jdstrand: what is in package.yaml? just docker>?
[17:37] <jdstrand> name: docker
[17:37] <kickinz1> yes : http://paste.ubuntu.com/10793087/
[17:37] <jdstrand> the packaging is correct
[17:37] <asac> goodie
[17:38] <jdstrand> kickinz1: that is not the packaging you used
[17:38] <jdstrand> kickinz1: that seems to be old
[17:38] <jdstrand> I'm guessing your old armhf package
[17:38] <kickinz1> sorry, wrong place (old docker)
[17:39] <kickinz1> http://paste.ubuntu.com/10793165/
[17:39] <kickinz1> jd strand yes, was on my old armhf package.
[17:40] <jdstrand> well, that has 003, but yes
[17:40] <kirkland> ogra_: hey
[17:40] <kirkland> so can we get some help?
[17:40] <kirkland> ogra_: hangout or something?
[17:40] <jdstrand> this is what is in the store: http://paste.ubuntu.com/10793168/
[17:40] <kickinz1> So I really need to go, kids are alone, I planned to update to new namespace, but not sure it is woth to do it now.
[17:40] <ogra_> kirkland, can we do it here ... i cant really do hangouts from this place atm
[17:40] <kirkland> ogra_: okay
[17:40] <kirkland> ogra_: so we run snappy build .
[17:40] <kirkland> ogra_: and we get a .snap
[17:40] <kirkland> ogra_: we push it to the device
[17:41] <kirkland> ogra_: and snappy installs it
[17:41] <kirkland> ogra_: now what...
[17:41] <kirkland> ogra_: how can we tell if it's running
[17:41] <kirkland> ogra_: I can't telnet to the 6565 port chatroom.ogra_0.1-5_multi.snap
[17:41] <ogra_> kirkland, well, journalctl should have a bunch of messages about it being started
[17:42] <asac> kirkland: do you see the green light on the board blinking when it boots?
[17:42] <ogra_> webdm should aalso have an entry and yu should be able to reach it on http://$ip:6565/
[17:42] <kirkland> ogra_: ubuntu@localhost:~$ journalctl
[17:42] <kirkland> No journal files were found.
[17:42] <kirkland> asac: it blinked for a while, but not anymore
[17:42] <asac> k
[17:42] <ogra_> kirkland, sudo ;)
[17:43] <kirkland> asac: I just re-wrote the image, again, sync sync sync
[17:43] <kirkland> asac: and put it back in the rpi2
[17:43] <ogra_> kirkland, sudo journalctl|grep chatroom
[17:44] <ogra_> that should return some stuff
[17:44] <kirkland> ogra_: okay, good, this helps, I'm debugging now
[17:44] <ogra_> (or just pipe toless)
[17:44] <kirkland> asac: okay, so we're not going to have docker on rpi2 today?
[17:44] <kirkland> asac: if so, that's fine, I'll apologize and we'll cope
[17:44] <ogra_> kirkland, note that the package is pretty old, i didnt update it since a while and snappy changed underneath ... might be there are issues now
[17:44] <kirkland> asac: I'd much rather put all effort into solving one problem (packaging a nodejs app) than 2
[17:45] <kirkland> ogra_: I'm confused a bit about one thing
[17:45] <kirkland> ogra_: so I just untar that armhf tarball at the same level as the the meta/ and site/ dir?
[17:45] <kirkland> ogra_: and snappy build just puts that in there?
[17:46] <ogra_> kirkland, node-snapper generates two tarballs ... you unpack them in the toplevel of your package dir
[17:46] <kirkland> ogra_: okay, we only care about armhf here
[17:46] <ogra_> and should end up with an armhf and amd64 dir
[17:46] <kirkland> ogra_: is that okay?
[17:46] <ogra_> you need to adjust package.yaml
[17:46] <kirkland> ogra_: can I just remove amd64 from the package.yaml
[17:46] <kirkland> ogra_: okay, good done
[17:46] <ogra_> yeah
[17:47] <ogra_> so you unpack the armhf tarball in the toplevel ...
[17:47] <kirkland> ogra_: okay, and then you just point a browser at :6565?
[17:47] <ogra_> start-service.sh then checks for the arch and calls $arch/bin/nodejs site/server.js
[17:47] <ogra_> right
[17:48] <kirkland> ogra_: start-service.sh runs automatically?
[17:48] <ogra_> it used to
[17:48] <ogra_> not sure if the systemd service handling changed recently
[17:48] <asac> kirkland: should do
[17:49] <asac> if not you can try starting the service manually
[17:49] <asac> have to find the right systemd name :)
[17:49] <asac> we love systemd
[17:49] <ogra_> sudo systemctl |grep chatroom
[17:49] <ogra_> that should give you the service name
[17:51] <kirkland> asac: okay, my rpi2 is now up with the new image
[17:51] <asac> kirkland: really?
[17:51] <asac> wow :)
[17:51] <kirkland> asac: yeah, so can I install docker then?
[17:51] <asac> kirkland: reflashed?
[17:51] <kirkland> asac: yeah
[17:52] <asac> no it wont work as i said above
[17:52] <asac> i am trying
[17:52] <asac> i think the image is too old :) ... i tested on bbb and it worked
[17:52] <asac> with todays image
[17:52]  * kirkland has to move downstairs now
[17:52] <asac> yeah gimme a bit
[17:52] <asac> i am confident that it will nto bail as it does with the lool image
[17:53] <asac> just have to get it booting
[17:53] <asac> had the same prob you had
[17:55] <asac> jdstrand: http://paste.ubuntu.com/10792912/
[17:55] <asac> can you think of a reason why that might be buggy with image from yesterday?
[17:56] <asac> e.g. is there hope
[17:56] <asac> it works with bbb from this morning for sure
[17:56] <ogra_> did you check your clock ?
[17:56] <asac> tyeah that was fine here
[17:56] <asac> we have now ntp-like thing
[17:56] <asac> so if network its good
[17:57] <ogra_> ah, k
[17:57]  * ogra_ lost track ... so much stuff on phone going on atm
[17:57] <asac> yeah even more stuff going on here still :/
[17:59] <asac> anyone has a good picture how to connect the serial pins on this pi2?
[17:59] <asac> i would feel better if i could see whats going on
[18:01] <asac> bah!!!
[18:01] <ogra_> bah ?
[18:01] <asac> reboot
[18:01] <asac> udf doesnt work anymore
[18:01] <asac> because i ctrl-c'
[18:01] <asac> ed it
[18:04] <kirkland> ogra_: I've been stuck here for ~10 minutes:
[18:04] <kirkland> > utf-8-validate@1.0.1 install /node_modules/ws/node_modules/utf-8-validate
[18:04] <kirkland> > node-gyp rebuild
[18:04] <ogra_> there should be a spinner underneath
[18:05] <ogra_> that usually takes a while, it compiles the modules
[18:06] <ogra_> if yu dont see the spinner, ctrl-c and run it again ... it uses qemu-user-static for the cross building, thats not 100% reiable
[18:06] <kirkland> ogra_: okay, ctrl-c'd, trying again
[18:06] <ogra_> whats your host arch ?
[18:06] <ogra_> i ran it only on amd64 machines
[18:07] <ogra_> (and on nothing newer than utopic, though that sholdnt matter)
[18:07] <asac> it was all lools fault again :) ... he didnt put --channel edge in his thingy so i tried to use the new device with devel :)
[18:07] <asac> mvo: are we good on promotion?
[18:07] <asac> i think that might help :_)
[18:07] <kirkland> asac: heh
[18:07]  * asac regenerates two images
[18:07] <asac> one pi2
[18:07] <asac> and pi2-docker with docker preinstalled
[18:07] <asac> :P
[18:08] <asac> not that it would help if apparmor falls over on first boot
[18:08] <asac> hence i try the plain one first to see if it works :)
[18:08]  * asac wont figure out how to connect serial
[18:08] <mvo> asac: still on it :( its looking promising though
[18:08] <asac> mvo: good!!
[18:08] <mvo> asac: Chipaca is currently tsting BBB, I did some testing on amd64/kvm
[18:08] <ogra_> asac, i'm not near my rpi ... :/
[18:09] <ogra_> and i cant tell from the top of my head
[18:09] <asac> ogra_: where are you?
[18:09] <ogra_> downstairs ...
[18:09] <asac> haha
[18:09] <ogra_> :)
[18:09] <asac> dont worry
[18:09] <asac> i am confident that this flash run will rock
[18:09] <kirkland> ogra_: okay, we made it past that step now
[18:09] <ogra_> cool
[18:10] <ogra_> asac, susie says: "cut the blue wire, not the yellow one"
[18:10] <ogra_> (she jus asked why i laugh)
[18:11] <asac> lol
[18:13] <asac> mvo: do uyou know if james landed something that touches the initrd?
[18:13] <asac> today?
[18:13] <asac> or yesterday?
[18:14] <mvo> asac: I don't think so but I don't know for sure
[18:14] <mvo> asac: why do you ask?
[18:14] <asac> just wondering if the device tarball of lool still has a chance to boot with an image 2 days later
[18:14] <asac> dont worry
[18:15] <asac> waiting for pi2 to start booting
[18:15] <mvo> asac: so testing results are a bit sparse, should we just promote amd64 and armhf (assuming the test look good)
[18:15] <asac> mvo: i am not sure what that excludes :)
[18:16] <sergiusens> mvo: asac I can continue with testing now or addon to Chipaca if we can speed things up
[18:16] <asac> i386 i dont care much
[18:16] <Chipaca> sergiusens: selftest fails here
[18:17] <Chipaca> sergiusens: http://pastebin.ubuntu.com/10793413/
[18:17] <asac> so this one did never get a green light
[18:17] <asac> me dds again
[18:18] <kirkland> ogra_: http://paste.ubuntu.com/10793417/
[18:18] <asac> i would very much love to be on a machine that doesnt do crazy automounting :)
[18:18] <asac> i feel this induces99% of my bogus flash attempts
[18:18]  * asac looks up this dbus --inhibit magic
[18:18] <sergiusens> Chipaca: oh, that's why I mentioned "remove software" from package.yaml
[18:18] <ogra_> kirkland, you dont have start-service.sh in your package
[18:18] <asac> sergiusens: can udf still work with udisks --inhibit-all ?
[18:18] <sergiusens> Chipaca: mvo I'll run the selftests with the beagleblack.canonical oem package
[18:19] <kirkland> ogra_: oh, I thought you had everything in that branch
[18:19] <ogra_> kirkland, did you actually follow the blog ... technically just copy/pasting the terminal commands should be enough
[18:19] <sergiusens> asac: it should, there's no udisk involvement here
[18:19] <kirkland> ogra_: I did the first time around;  the second time around, I just bzr branched your +junk branch
[18:19] <ogra_> yeah, that should be enough ...
[18:20] <ogra_> you should just need to unpack the tarball in the toplevel
[18:20] <asac> kirkland: what do uyou have in /apps/ ?
[18:20] <asac> ls /apps/
[18:21] <jdstrand> asac: so, that paste is weird-- a number of things seem wrong. aa-clickhook failed gracefully, but systemd-snappyhook had some issues
[18:22] <jdstrand> asac: is it still an issue? let me try from the store on an updated image
[18:22] <asac> right i wanted to file it in the "snappy doesnt like namespaces, but that got fixed today" category
[18:22] <asac> jdstrand: no its only on the lool pi2 image
[18:22] <asac> i just want to know if its something underlying
[18:22] <asac> or just outdated image
[18:23] <asac> i totally get that anything can be possible because we rushed so many things in last few days
[18:23] <asac> just wanted to feel better while i fiddle with stupid dd
[18:23] <jdstrand> seems like maybe a filesystem issue?
[18:24] <asac> really?
[18:24] <asac> i dont have the paste anymore
[18:24] <asac> rebooted
[18:24] <jdstrand> cause that error from aa-clickhook is just about taking the json and outputting a text file
[18:24] <jdstrand> asac: I'm guessing since I don't have access to the device
[18:25] <jdstrand> maybe it was still read only?
[18:25] <jdstrand> again, guessing
[18:25] <asac> no clue
[18:25] <asac> letse wawit
[18:25] <asac> my latest dd seems to be at least truying to boot
[18:25] <jdstrand> that's a good start :)
[18:26] <asac> and it got an ip
[18:26] <asac> also good news
[18:26]  * asac waits for cloud-init do the groundwork to get me to ssh
[18:26] <asac> ok so i am in the latest and greatest snappy userspace
[18:26] <asac> on the amazing lool device tarball
[18:26] <jdstrand> woo!
[18:27] <kirkland> ogra_: okay, this looks good:
[18:27] <kirkland> Feb 16 21:04:03 localhost.localdomain sudo[1062]: ubuntu : TTY=pts/1 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/snappy install chatroom.ogra_0.1-5_multi.snap
[18:27] <kirkland> Feb 16 21:04:32 localhost.localdomain systemd[1]: Started A simple WebRTC videochat.
[18:27] <kirkland> Feb 16 21:04:32 localhost.localdomain systemd[1]: Starting A simple WebRTC videochat...
[18:27] <kirkland> not getting anything though, if I point my browser at 192.168.1.115:6565
[18:27] <asac> open /apps/docker/1.5.0.002/meta/package.yaml: permission denied
[18:28] <jdstrand> that's less 'woo'
[18:28] <asac> wtf
[18:28] <asac> something is odd there
[18:29] <asac> hmm
[18:29] <asac> second time it worked :)
[18:29] <jdstrand> ehh..
[18:29] <asac> kirkland: what was the command that kickinz1|away said we should use?
[18:29] <jdstrand> good?
[18:29] <asac> for armhf docker?
[18:29] <asac> the docker command is there :)
[18:29] <kirkland> asac: you need an armhf docker image
[18:30] <asac> yes he gave us a command
[18:30] <asac> you have that?
[18:30] <kirkland> asac: I'll have to look in scrollback here
[18:30] <asac> i dont have it :(
[18:30] <ogra_> kirkland, hmm, anything else in the logs ?
[18:30] <ogra_> it should just work ...
[18:31] <jdstrand> asac, kirkland: docker run -it armbuild/ubuntu
[18:33] <jdstrand> asac: you might be interested in http://paste.ubuntu.com/10791782/
[18:33] <kirkland> ogra_: netstat -an | grep 6565
[18:33] <kirkland> ogra_: shows nothing
[18:33] <jdstrand> asac: I guess if following that paste, you would change any of the 'ubuntu:' to be 'armbuild/ubuntu:'
[18:33] <ogra_> kirkland, ps ax|grep node
[18:34] <ogra_> does the nodejs process run ?
[18:34] <jdstrand> asac: but I've never done that
[18:36] <kirkland> ogra_: no node processes running
[18:36] <ogra_> kirkland, hmm, but no errors in journalctl ?
[18:37] <ogra_> that werid
[18:37] <kirkland> ogra_: right, not anymore
[18:37] <ogra_> *that's
[18:37] <kirkland> ogra_: http://paste.ubuntu.com/10793547/
[18:37] <kirkland> ogra_: there's a few snappy installs in there
[18:37] <kirkland> ogra_: note the timestamps
[18:37] <ogra_> Feb 16 21:02:40 localhost.localdomain systemd[995]: Failed at step EXEC spawning /apps/chatroom.ogra/0.1-5/start-service.sh: Exec format error
[18:37] <asac> jdstrand: do those commands work for you on bbb?
[18:38] <ogra_> are you sure you ship the armhf tarball ?
[18:38] <kirkland> ogra_: how can I check?
[18:38] <asac> jdstrand: i always get stuff olike:
[18:38] <asac> FATA[0000] Get http:///var/run/docker.sock/v1.17/version: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS?
[18:38] <kirkland> ogra_: fyi, I have to switch networks every time I move from IRC to the rpi, and back, so sorry for the long turnaround
[18:39] <asac> jdstrand: when docker images
[18:39] <asac> for instance
[18:39] <ogra_> kirkland, does /apps/chatroom-test.ogra/0.1-5/armhf/bin/nodejs exist ?
[18:39] <jdstrand> that's weird
[18:39] <jdstrand> I've never seen that before
[18:39] <jdstrand> http:///var/run/docker.sock/v1.17/version makes no sense
[18:40] <asac> yeah something bad happened
[18:40] <asac> jdstrand: do uyou have a beagle?
[18:40] <asac> just try installing docker and see if docker images works
[18:40] <jdstrand> is docker daemon running?
[18:40] <asac> no
[18:40] <jdstrand> not yet
[18:40] <jdstrand> I just ordered one yesterday
[18:40] <asac> hmm
[18:40] <kirkland> ogra_: http://paste.ubuntu.com/10793573/
[18:41] <jdstrand> I can say kickinz1|away tested bbb and amd64 and I tested various versions of amd64
[18:41] <ogra_> kirkland, looks all fine to me ... hmm, perhap some env vars have changed, start-service,sh uses $SNAPP_  everywhere
[18:42] <jdstrand> asac: what is the output of 'grep DEN /var/log/syslog'
[18:42] <asac> doont have it anymore
[18:42] <asac> something odd happend on first install
[18:42] <asac> the rest might be cruft
[18:42] <jdstrand> ok
[18:42] <asac> so its not valid
[18:42] <asac> i will now check on bbb
[18:42] <asac> while installing my image that has docker preinstalled
[18:42] <jdstrand> I think you are right to invalidate that test
[18:42] <asac> i have the feeling my sdcard has problems
[18:43] <jdstrand> that would possibly explain things
[18:43]  * asac prepares to find a new one
[18:43] <asac> i have that one in the pi2 since MWC
[18:44] <asac> should be pretty good
[18:44] <asac> pretty high quality
[18:44] <jdstrand> sergiusens: hey, this is not important at all, but with udf, it might be nice to output the revision that was downloaded. eg: sudo ubuntu-device-flash  core --output ubuntu-core.img --channel ubuntu-core/devel-proposed -s 8 --enable-ssh
[18:44] <jdstrand> sergiusens: ... New image complete (rNNN)
[18:44] <asac> jdstrand: so same same
[18:44] <asac> BeagleBoneBlack)ubuntu@localhost:~$ docker images
[18:44] <asac> FATA[0000] Get http:///var/run/docker.sock/v1.17/images/json: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS?
[18:44] <jdstrand> that's no good
[18:45] <jdstrand> I'm going to try in kvm
[18:45] <asac> jdstrand: who is supposed to start docker?
[18:45] <jdstrand> systemd
[18:45] <asac> jdstrand: there is no docker job in /etc
[18:45] <asac> find /etc/systemd/ | grep docker
[18:45] <asac> (BeagleBoneBlack)ubuntu@localhost:~$
[18:45] <jdstrand> asac: what does /var/log/syslog say about the install?
[18:46] <asac> dunno  installed it before i rebooted
[18:46] <jdstrand> syslog is persistent
[18:46] <asac> Apr 10 18:42:55 localhost click[586]: ERROR:root:Failed to create system unit for docker_docker-daemon_1.5.0.002: expected string
[18:46] <sergiusens> jdstrand: I can get that in in a bit, sure
[18:47]  * jdstrand taps fingers waiting for image to come up
[18:47] <asac> http://paste.ubuntu.com/10793654/
[18:47] <asac> jdstrand: ^
[18:47] <asac> thats a grep
[18:47] <kirkland> ogra_: alrighty, I'm up and running
[18:47] <kirkland> ogra_: thanks for your help
[18:48] <kirkland> ogra_: have a good evening, sir
[18:48] <ogra_> kirkland, yay, what was it ?
[18:48] <kirkland> ogra_: a bunch of little things
[18:48] <kirkland> ogra_: I'll try to write them up
[18:48] <ogra_> heh, k
[18:48] <kirkland> ogra_: mostly, I didn't do the right things with start-service.sh
[18:48] <jdstrand> asac: so, lool did mention earlier he was trying to start it manually... I wonder if he had the same issue
[18:48] <jdstrand> sigh
[18:48]  * jdstrand -> reboot
[18:48]  * davmor2 shows jdstrand and image quickly
[18:48] <ogra_> kirkland, well, theoretically you shouldnt need to do anything .... so i'l like to merge any needed changes
[18:48] <asac> mvo: http://paste.ubuntu.com/10793654/
[18:49] <kirkland> asac: poke me if docker on rpi2 comes around :-)
[18:49] <asac> does that mean anything to you?
[18:49] <kirkland> ogra_: honestly, if start-service.sh were part of your bzr branch, that would be great :-)
[18:49] <ogra_> it is, no ?
[18:49]  * ogra_ checks
[18:49] <kirkland> ogra_: no, it's generated by your node-snapper script
[18:49] <kirkland> ogra_: and then it has to be copied over
[18:49] <kirkland> ogra_: and then manually edited
[18:49] <ogra_> oh, right
[18:50] <kirkland> ogra_: i did something wrong, somewhere in there
[18:50] <kirkland> ogra_: finally, I just went back over all of your instructions again, from scratch, and it worked well enough
[18:50] <ogra_> yeah, because it needs to create the LD_LIBRARY_PATH and friends
[18:50] <kirkland> ogra_: so the instructions are good :-)  Just a little new/confusing the first time through
[18:50] <mvo> asac: hm, that looks like something in docker, no? the click error comes after the unit fails to start
[18:50] <ogra_> ok
[18:51] <asac> mvo: why would click fail to create the unit ?
[18:51] <asac> that should never fail imo
[18:51] <mvo> asac: click should not generate it at all anymore :) its snappy-go that does that nowdays
[18:51] <asac> so what is click doing here?
[18:52] <asac> is that because he has com.ubuntu.snappy ?
[18:52]  * asac still doesnt get why that just installs
[18:52] <asac> if i run snappy install docker
[18:52] <mvo> asac: its because the build still produces snappy compatiblity code
[18:52] <asac> in which cases?
[18:52] <asac> is that the problem?
[18:52] <mvo> asac: when snappy build is called and yes, I think that is the problem
[18:52] <asac> so his package is click still?
[18:52] <asac> damn
[18:52] <asac> :)
[18:52] <asac> jdstrand: can you dpkg -x his docker
[18:53] <asac> and snappy build . it fresh?
[18:53] <asac> i dont have that .snap :(
[18:53] <mvo> asac: nothing I can do against that yet, sorry, soon it will not be anymore
[18:53] <asac> mvo: well, so i hear that he used an old snappy build ?
[18:54] <asac> ok
[18:54] <mvo> asac: not nesessarily, the current snappy still generates compatiblity code for the older images
[18:54] <asac> so you think if we upload it as .canonical it might work?
[18:54] <asac> odd thing is that on amd64 jdstrand says it works
[18:54] <mvo> it works on my amd64 as well
[18:54] <mvo> well, it installs and I can run docker and it prints stuff
[18:54] <asac> i can do that too
[18:55] <asac> run "docker images"
[18:55] <asac> that bails out
[18:55] <asac> the service is not running
[18:55] <asac> the docker command is there
[18:55] <asac> i really need the .snap :_)
[18:55] <asac> jdstrand: can you get me the .sanp from store?
[18:55] <asac> i want to try sideloading it
[18:55] <asac> i am sure he sideloaded it during development
[18:55] <asac> and it worked ;)
[18:56] <asac> beuno: can yiou check if we have an alias set in store
[18:56] <asac> for docker to com.ubuntu... ?
[18:57] <mvo> http://paste.ubuntu.com/10793735/
[18:57] <mvo> asac: -^ works on my amd64 install
[18:57] <mvo> asac: do you run that on the BBB?
[18:59] <jdstrand> man that was painful
[18:59] <jdstrand> ok, I'm back
[19:00] <asac> mvo: yeah its buggy there
[19:00] <asac> mvo: can you give me the raw snap?
[19:00] <asac> i have zero clue how to get that
[19:01] <mvo> asac: sergiusens wrote a store-get command for this, I think we should have a hidden snappy download command for this
[19:01] <jdstrand> meh, I lost my review copy cause I rebooted
[19:01] <jdstrand> I can get it
[19:01] <jdstrand> hold on
[19:02] <asac> thx so much :)
[19:02] <mvo> asac: go get github.com/sergiusens/store-get
[19:02] <mvo> asac: $GOPATH/bin/store-get docker
[19:02] <mvo> asac: that should work
[19:02] <asac> i am not set up for go stuff :/
[19:03] <asac> lets no solve that for now
[19:03] <mvo> meh, ok
[19:03] <asac> so seems snappy update is running ;) ... cant do more
[19:03] <mvo> sorry
[19:04] <mvo> but its really just sudo apt-get install golang-go and export GOPATH=~/go
[19:04] <kickinz1|away> asac, did you try on bbb?
[19:04] <asac> yeah
[19:04] <asac> kickinz1|away: same problem
[19:04] <kickinz1|away> it was working ok for me and for lool on bbb
[19:04] <asac> kickinz1|away: http://paste.ubuntu.com/10793783/
[19:04] <kickinz1|away> which image on bbb?
[19:04] <asac> the one from this morning
[19:05] <kickinz1|away> snappy list gives you what?
[19:05] <asac> kickinz1|away: http://paste.ubuntu.com/10793787/
[19:05] <asac> 221
[19:05] <kickinz1|away> I'm on 220...
[19:05] <kickinz1|away> Name        Date       Version   Developer
[19:05] <kickinz1|away> ubuntu-core 2015-04-10 220
[19:05] <kickinz1|away> docker      2015-04-10 1.5.0.002
[19:05] <asac> kickinz1|away: did you install from store?
[19:05] <asac> or sideload?
[19:05] <kickinz1|away> install from store
[19:06] <kickinz1|away> I did sudo snappy remove docker (that one was sideloaded)
[19:06] <asac> yeah
[19:06] <kickinz1|away> then sudo snappy install docker (that on came from store)
[19:06] <asac> maybe that left over the parts that dont work from store
[19:06] <kickinz1|away> then I tested
[19:06] <asac> kickinz1|away: do you have the .snap still?
[19:06] <kickinz1|away> yes
[19:06] <asac> would like too try side loading
[19:07] <kickinz1|away> https://mifamofi.net/owncloud/public.php?service=files&t=f837f7bc6787466c54c1467f43715987
[19:07] <asac> mvo: how can i manually remove the docker?
[19:07] <asac> it doesnt uninstall because the service is still running
[19:07] <asac> err is not running
[19:09] <asac> kickinz1|away: can you put that as a file up somewhere?
[19:09] <asac> nevermind
[19:09] <asac> i jsut dont like using browser download
[19:09] <asac> have it now
[19:09] <kickinz1|away> asac yes I just qhared the link before ^ : https://mifamofi.net/owncloud/public.php?service=files&t=f837f7bc6787466c54c1467f43715987
[19:09] <kickinz1|away> ok
[19:12] <jdstrand> asac: http://people.canonical.com/~jamie/docker_1.5.0.002_all.snap
[19:13] <asac> ok so sideloading does the trick
[19:13] <asac> i think its the com.ubuntu... fun thing
[19:14] <asac> ok /me goes all in and preinstall the sideloaded docker :)
[19:14] <asac> for pi2
[19:14] <asac> jdstrand: you can upload for .canonical?
[19:14] <jdstrand> fyi, I just did 'sudo snappy install docker' from the store and it is working
[19:15] <jdstrand> on amd64
[19:15] <asac> yeah i dont know why that is the case
[19:15] <jdstrand> r377
[19:15] <asac> i know that i just sideloaded it and it works on bbb
[19:15] <asac> like our theory
[19:15] <kickinz1|away> I'll update my bbb to 221 and check install from store
[19:15] <asac> it didnt work on pi2 from store nor on bbb when i didnt have it instaleld before
[19:15] <jdstrand> give me a minute
[19:15] <asac> kickinz1|away: so be sure that you remove all stuff of docker
[19:16] <asac> kickinz1|away: rm -rf /apps/docker/
[19:16] <asac> kickinz1|away: rm -rf /apps/bin/docker*
[19:16] <asac> kickinz1|away: rm -rf /var/lib/apps/docker/
[19:16] <jdstrand> kickinz1|away: have you updated the docker branch?
[19:16] <asac> kickinz1|away: and also the docker stuff in /etc/systemd/
[19:16] <asac> kickinz1|away: so rm /etc/systemd/system/multi-user.target.wants/docker_docker-daemon_1.5.0.002.service
[19:16] <asac> and rm /etc/systemd/system/docker_docker-daemon_1.5.0.002.service
[19:16] <asac> then installing from store will explode
[19:16] <asac> our theory because of the namespace\
[19:17] <asac> i think our snappy remove does not clean the systemd jobs
[19:17] <asac> is what i suspect
[19:17] <jdstrand> remove seems to have some bugs
[19:18] <asac> yeah
[19:18] <jdstrand> I haven't had a chance to dig in and file them
[19:18] <asac> the data is still there
[19:18] <asac> not the systemd stuff
[19:18] <asac> odd
[19:18] <asac> guess next week is bug fix mode :)
[19:18] <asac> and not that many features :)
[19:20] <asac> wtf now from store worked too
[19:20] <asac> sigh
[19:20] <kickinz1|away> on bbb ?
[19:21] <asac> yeah
[19:21] <asac> very very odd
[19:21] <kickinz1|away> after a sideload?
[19:21] <asac> i installed 2 hours ago
[19:21] <asac> no systemd jobs
[19:21] <asac> (from store)
[19:22] <asac> i manually cleaned all things and sideloaded -> worked
[19:22] <asac> i manually cleaned and install from stored -> worked
[19:22] <kickinz1|away> did you removed /var/lib/apparmor/docker related stuff?
[19:22] <asac> oh no
[19:22] <asac> that one i didnt
[19:22] <asac> good point
[19:22] <asac> i only did /var/lib/apps/docker
[19:23] <asac> so that might be it
[19:23] <jdstrand> there is also framework policy in /var/lib/snappy
[19:23] <kickinz1|away> jdstrand still uploading, very slow bandwith...
[19:24] <kickinz1|away> jdstrand just uploaded
[19:24] <jdstrand> ok
[19:24] <asac> jdstrand: can we maybe reupload kickinz1|away's snapp as .canonical ?
[19:24] <jdstrand> there it goes
[19:24] <asac> can you do that?
[19:24] <asac> i think its worth a shot :P
[19:24] <jdstrand> asac: that is what I am working on
[19:24] <asac> we certainly prefer to not have com....
[19:24] <asac> ah thanks
[19:24] <asac> we need to find the store folks
[19:24] <asac> a) shut down the smoser account
[19:24] <asac> b) clean the docker :)
[19:26] <asac> omg
[19:26] <asac> there is so much stuff of docker in the FS
[19:26] <asac> even in click directories taht shouldnt exist in my world view
[19:26] <asac> spread everywhere
[19:26] <asac> jdstrand: we really need to clean up the world where appamore spreads stuff :)
[19:26] <asac> its everywhere
[19:27] <asac> needs to be nicely in one place :P
[19:27] <asac> know its not you
[19:27] <asac> but just saying
[19:27] <asac> its hooked in everywhere
[19:27] <asac> kinda makes sense that we dont clean it nicely on remove
[19:28] <asac> kickinz1|away: so i cant say that its really the sideloading
[19:28] <asac> because my bbb was certainly not docker free when it suddenly started working
[19:28] <asac> guess we have to find | grep docker and rm -rf manually
[19:28] <asac> or on fresh flash which is awful
[19:28] <asac> ok flashing fresh pi2 again
[19:30] <asac> jdstrand: http://paste.ubuntu.com/10793979/
[19:30] <jdstrand> asac: re apparmor, yes, that is part of what /var/lib/snappy is about. that is the new world. the old world still exists
[19:31] <jdstrand> so we have click and snappy locations, so its weird
[19:32] <asac> s i think i removed all fiels that had name docker
[19:32] <asac> and sideloading still worked
[19:32] <asac> so there is hope
[19:32] <asac> but maybe i oversaw something
[19:34] <jdstrand> there is also the issue that things are garbage collected when install fails, but not completely
[19:35] <asac> yeah for sure
[19:36] <jdstrand> ok, lp:~snappy-dev/snappy-hub/docker updated to what is in the store now
[19:36] <jdstrand> now preparing 1.5.0.003 with .canonical
[19:40] <jdstrand> ok, the snap looks good
[19:41] <jdstrand> actually, I'm not sure what account is used for .canonical. is that on the mailing list?
[19:41] <jdstrand> sergiusens: ^
[19:42] <asac> INFO[0000] Listening for HTTP on unix (/var/run/docker.sock)
[19:42] <asac> WARN[0000] WARNING: Udev sync is not supported. This will lead to unexpected behavior, data loss and errors
[19:42] <asac> FATA[0000] Error running DeviceCreate (CreatePool) dm_task_run failed
[19:42] <asac> kickinz1|away: ^^
[19:42] <asac> so i think thats the problem
[19:42] <sergiusens> jdstrand: I have creds and so does mvo
[19:42] <jdstrand> I've got it now
[19:42] <sergiusens> jdstrand: want it
[19:42] <sergiusens> ah you got it
[19:42] <jdstrand> thanks
[19:42] <asac> root@localhost:/apps/docker/1.5.0.002# /apps/docker/1.5.0.002/bin/docker.start
[19:42] <asac> INFO[0000] +job serveapi(unix:///var/run/docker.sock)
[19:42] <asac> INFO[0000] Listening for HTTP on unix (/var/run/docker.sock)
[19:42] <asac> WARN[0000] WARNING: Udev sync is not supported. This will lead to unexpected behavior, data loss and errors
[19:42] <asac> FATA[0000] Error running DeviceCreate (CreatePool) dm_task_run failed
[19:42]  * asac bets its kernel option missing
[19:42]  * sergiusens watches the flood of asac
[19:43] <asac> 21:42 < asac> FATA[0000] Error running DeviceCreate (CreatePool) dm_task_run failed
[19:43] <asac> really would like to know what that tries to do
[19:43] <asac> http://paste.ubuntu.com/10794076/
[19:43] <asac> that looks suspicious
[19:44] <asac> yeah this ioctl multiplies when i run docker
[19:45] <asac> https://github.com/docker/docker/blob/dd786eefbbf286ca57b52374a6905c1ac8b8bd60/docs/sources/installation/kernel.rst
[19:45] <crised_> Can I see the available packages for this distro?
[19:47] <mfilipe> anyone here knows how is the progress to Digital Ocean accepts Ubuntu Core?
[19:51] <kickinz1|away> bbb: updating from 3 -> 222 ;) (slow bandwidth used an already downloaded).
[19:53] <jdstrand> sergiusens: "The uploaded package name (docker) does not use your namespace (canonical)"
[19:54] <jdstrand> sergiusens: I thought we said I did not need .canonical in the name?
[19:55] <jdstrand> the store may need an alias
[19:55] <jdstrand> asac: please advise ^
[19:55] <jdstrand> yaml has: name: docker
[19:55] <jdstrand> upload resulted in "The uploaded package name (docker) does not use your namespace (canonical)"
[19:55] <asac> ok found somethign
[19:55] <sergiusens> jdstrand: that's not ready afaik
[19:55] <asac> our kernel doesnt have enough options
[19:55] <asac> CONFIG_BLK_DEV_DM
[19:56] <asac> CONFIG_DM_THIN_PROVISIONING\
[19:56] <asac> jdstrand: you know kernel packaging fu enough to maybe add those options ? and spin a ppa build?
[19:56] <asac> https://launchpad.net/~p-pisati/+archive/ubuntu/misc/+files/linux-bcm2709_3.19.1-4.4.dsc
[19:56] <jdstrand> sergiusens: if that's true, we should hold off on uploading this into the .canonical namespace
[19:56] <jdstrand> tyhicks: can you take a look at that? ^
[19:57] <jdstrand> tyhicks: at what asac mentioned
[19:57] <asac> so i am cross checking https://github.com/docker/docker/blob/dd786eefbbf286ca57b52374a6905c1ac8b8bd60/docs/sources/installation/kernel.rst
[19:57] <asac> with cat boot/config-3.19.1-4-generic-bcm2709  | pastebinit
[19:57] <asac> http://paste.ubuntu.com/10794169/
[19:57] <asac> and CONFIG_BLK_DEV_DM
[19:57] <asac> missing makes lots of sense given the error we see
[19:57] <asac> http://paste.ubuntu.com/10794076/
[19:58] <jdstrand> let me see what snappy does if I do 'name: docker.canonical'
[19:59] <asac> yeah
[19:59] <asac> but the optioons are missing for sure
[19:59] <asac> so missing from what i see is:
[19:59] <asac> CONFIG_MEMCG_SWAP
[19:59] <asac> CONFIG_DM_THIN_PROVISIONING
[19:59] <jdstrand> I'm quite sure snappy is going to not dtrt with docker.canonical
[19:59] <asac> CONFIG_BLK_DEV_DM
[19:59] <asac> jdstrand: i think it will
[19:59] <asac> unless we still install apps with .developer :_)
[19:59] <asac> otherwise its tracked
[20:00] <jdstrand> no, I don't think so
[20:00] <jdstrand> it is going to install the framework policy incorrectly
[20:00] <jdstrand> because frameworks are expected to be toplevel
[20:01] <asac> kirkland: bad news... docker wont run on pi2 because we lack some kernel options... and i wont be able to give you a new kernel with those options
[20:01] <asac> we might have some luck, but best focus on bbb and tell them that pi2 will behave the same
[20:01] <tyhicks> asac: is there a git tree with the bcm2709 kernel source?
[20:01] <asac> tyhicks: no clue
[20:01] <asac> we really just need a one off
[20:01] <asac> to bandaid
[20:01] <asac> tyhicks: you can dget the dsc
[20:02] <tyhicks> I've only ever built ubuntu kernels out of the kernel team's git trees
[20:02] <asac> and dpkg-source -x it :)
[20:02] <tyhicks> I can give the dsc a shot
[20:02] <sergiusens> tyhicks: http://people.canonical.com/~lool/pi2-device-and-oem/
[20:02] <asac> tyhicks: so there probably is one if you give me gitweb
[20:02] <asac> i can search
[20:02] <sergiusens> tyhicks: there's a link to a deb built by paulo
[20:02] <asac> its ppisiati
[20:02] <asac> who did that
[20:02] <sergiusens> in a ppa
[20:02] <asac> tyhicks: but i never can find gitweb
[20:03] <sergiusens> asac: http://kernel.ubuntu.com/git
[20:03]  * asac waits for the resource efficient gitweb app to figure what to display :)
[20:04] <sergiusens> asac: http://kernel.ubuntu.com/git?p=ppisati/ubuntu-vivid.git;a=summary
[20:04] <kirkland> asac: okay, no worries
[20:04] <kirkland> asac: thanks a lot, I'll apologize to the guys here
[20:04] <asac> kirkland: could be... but it makes sense now
[20:04] <kirkland> asac: thanks to ogra, we have a nodejs app :-)
[20:04] <asac> kirkland: so you can sideload it to bbb for sure
[20:04] <kirkland> asac: we're happy enough with that
[20:05] <asac> cool
[20:05] <asac> well, i spend so much time of my friday night that i needed to spend on something else
[20:05] <asac> that i really want this to work :)
[20:05] <tyhicks> sergiusens: I'd need to build a new snappy image to provide an updated kernel?
[20:05] <kirkland> asac: +1, go have a beer or 5
[20:05]  * tyhicks is looking at the pi2-device-and-oem link
[20:05] <asac> kirkland: well, if tyhicks can build a new kernel i might spin a new image for you tomorrow that will work
[20:06] <asac> tyhicks: you cannot do that
[20:06] <asac> tyhicks: if you have the kernel with those new options
[20:06] <asac> talk to me :)
[20:06] <asac> and i wil try to hack it into the device tarball and see if it works
[20:06] <asac> its a bit of a nightmare :)
[20:06] <tyhicks> ok
[20:06] <asac> 21:55 < asac> CONFIG_BLK_DEV_DM
[20:06] <asac> 21:56 < asac> CONFIG_DM_THIN_PROVISIONING\
[20:07] <jdstrand> asac: fyi, https://bugs.launchpad.net/snappy-ubuntu/+bug/1442790
[20:07] <asac> 21:57 < asac> and CONFIG_BLK_DEV_DM
[20:07] <asac> tyhicks: those tree
[20:07]  * tyhicks nods
[20:07] <asac> three!!
[20:07] <jdstrand> asac: (snappy remove doesn't remove everything)
[20:07]  * tyhicks will give it a shot
[20:07] <tyhicks> asac: I'm not going to do it in a ppa - that'll take too long
[20:07] <asac> yeah
[20:07] <asac> tyhicks: i need armhf image and modules deb
[20:07] <asac> the rest i will just fiddle around from there
[20:07]  * tyhicks nods
[20:07] <asac> tyhicks: you migth want to heck if we enable those options as modules
[20:07] <asac> or as y
[20:08] <asac> in our normal kernel
[20:08] <asac> just check on amd64
[20:08] <asac> if its y
[20:08] <tyhicks> right
[20:08] <tyhicks> will do
[20:08] <asac> maybe its just swapping the vmlinuz :)
[20:08] <asac> that would be jackpot
[20:08] <asac> at least i would just try to do that for bandaiding
[20:08] <kirkland> asac: if so, give it to mahmoh
[20:08] <kirkland> asac: he's supporting the hackathon tomorrow
[20:08] <jdstrand> interesting: rm: cannot remove '/var/lib/apps/docker/1.5.0.002/aufs': Device or resource busy
[20:08] <asac> kirkland: is he up to speed?
[20:08] <asac> :)
[20:08] <asac> kirkland: he isnt even online :(
[20:08] <asac> i tried to find him all week
[20:09] <asac> jdstrand: yeah thats all funny
[20:09] <asac> tyhicks: sorry i posrted one config twice... the third i found on docker page is CONFIG_MEMCG_SWAP
[20:09] <jdstrand> hopefully aufs is in said kernel too
[20:10] <asac> but not sure if we needt hat... the first two are surely the ones matching the errors i get in dmesg
[20:10] <asac> let me see
[20:10] <asac> i think it is
[20:10] <asac> cat boot/config-3.19.1-4-generic-bcm2709   | pastebinit
[20:10] <asac> http://paste.ubuntu.com/10794241/
[20:10] <asac> jdstrand: ^
[20:11] <asac> jdstrand: thats odd
[20:11] <asac> https://github.com/docker/docker/blob/dd786eefbbf286ca57b52374a6905c1ac8b8bd60/docs/sources/installation/kernel.rst
[20:11] <asac> its not there
[20:11] <asac> Note: as of 0.7 docker no longer requires aufs. AUFS support is still available as an optional driver.
[20:11] <asac> jdstrand: ^^
[20:11] <asac> read that page :)
[20:11] <jdstrand> erf, I hit the darn useless logging bug and garbage collection on install
[20:11] <asac> not sure why you have docker still using it though
[20:11] <asac> :{
[20:11] <asac> jdstrand: file them and we knock them out next week :)... bug fixing
[20:11] <asac> maybe make a short list
[20:12] <kirkland> asac: probably not, you'll need to send him a note
[20:12] <kirkland> asac: I'm heading home tonight
[20:12] <jdstrand> well, I only mentioned aufs cause that aufs file was not removable
[20:12] <asac> kirkland: is he not around?
[20:12] <jdstrand> asac: I filled them yesterday
[20:12] <jdstrand> filed
[20:12] <jdstrand> that is what kept people up late into the night
[20:14] <mahmoh> asac: hi
[20:14] <asac> hi mahmoh
[20:14] <asac> kirkland: so what kind of stuff are they doing there and mind need support?
[20:14] <asac> kirkland: maybe other channel
[20:20] <kickinz1|away> asac: on my fresh bbb 222: http://paste.ubuntu.com/10794316/
[20:21] <asac> kickinz1|away: yep see above
[20:21] <asac> kickinz1|away: seems some bugs in snappy caused the bbb also to have troubles
[20:21] <asac> kickinz1|away: it all seems to be kernel options missions
[20:21] <asac> missing
[20:21] <kickinz1|away> ok
[20:22] <kickinz1|away> sorry
[20:22] <asac> the basics definitely work on bbb
[20:22] <asac> kickinz1|away: sorry for causing confusion :)
[20:22] <asac> but friday night things go crazy
[20:22] <asac> kickinz1|away: we meet on sunday!
[20:22] <asac> go off
[20:23] <kickinz1|away> asac, ok see you on sunday!
[20:23] <asac> good to know that away is closer than afk :)
[20:25] <crised_> Are the packages from ubuntu available to snappy???
[20:27] <tyhicks> asac: CONFIG_BLK_DEV_DM is already 'y'
[20:28] <tyhicks> asac: CONFIG_DM_THIN_PROVISIONING a module on amd64 - would you rather me build it in for this one-off kernel?
[20:29] <tyhicks> (CONFIG_MEMCG_SWAP is built in on amd64 so I'll build it in for this kernel, too)
[20:29] <asac> tyhicks: yeah if it can be just built in thats better
[20:29] <tyhicks> will do
[20:30] <asac> thin certainly makes sense as well with the dmest
[20:30] <asac> dmesg :)
[20:35] <asac> tyhicks: guess just give me vmlinuz :)
[20:41] <jdstrand> asac: ok, so framework policy is not copied correctly with 'name: docker.canonical_client'. as a result, the docker cli command doesn't work (cause it references this policy). I could make it all work, but by definition frameworks are supposed to be toplevel
[20:41] <asac> yeah
[20:41] <jdstrand> asac: I think we should hold off on docker in the .canonical namespace
[20:41] <asac> jdstrand: so what i dont understand is why the com.... works
[20:41] <asac> jdstrand: i guess the alias?
[20:41] <asac> thats fine
[20:41] <jdstrand> asac: because there is a server side hack iirc
[20:42] <asac> the .canonical will go away if we do switch
[20:42] <asac> its the alias
[20:42] <asac> i think
[20:42] <jdstrand> maybe it is now an alias and not a hack
[20:42] <asac> if i install docker
[20:42] <jdstrand> we had hacks in december
[20:42] <asac> right
[20:42] <asac> its not clear to me how the fact that its an alias propagates
[20:42] <jdstrand> me either
[20:42] <asac> jdstrand: did you use docker.canonical in yaml?
[20:42] <asac> i think dont do that
[20:42] <asac> just use docker
[20:42] <asac> and upload it as .canonical
[20:42] <asac> and then its fine
[20:43] <asac> i think store already implemented it
[20:43] <asac> as origin
[20:43] <asac> so we can kick it out of package.yaml
[20:43] <jdstrand> asac: right, so, with 'name: docker' on upload I had the store tell me I messed up
[20:43] <asac> this is why it works for what we did with com...
[20:43] <asac> odd
[20:43] <jdstrand> with 'name: docker.canonical' I see the policy issue
[20:43] <asac> ok then the store hasnte finished work
[20:43] <asac> lets not bother till they land that origin feature
[20:43] <asac> i thought it was done
[20:43] <asac> but maybe they are stilll doing something
[20:43] <jdstrand> asac: when you say 'upload it as .canonical' what do you mean?
[20:43] <jdstrand> adjust the filename?
[20:44] <asac> jdstrand: its meant to be only something you do in the store
[20:44] <asac> you package it up without namespace
[20:44] <asac> and upload it as .canonical
[20:44] <asac> then its all good
[20:44] <jdstrand> yes, what does that mean?
[20:44] <jdstrand> :)
[20:44] <jdstrand> that is what I attempted to do first
[20:44] <asac> this means you upload it as use that has namespace .canonical
[20:44] <jdstrand> yeah
[20:44] <asac> the store will just track that as "origin"
[20:44] <jdstrand> ok, that didn't work
[20:44] <asac> right
[20:44] <asac> this is the only big thing we are missing
[20:44] <asac> for next week
[20:45] <asac> from what i know :)
[20:45] <asac> besuides your security refinements
[20:45] <jdstrand> I logged to the proper account, the store recognized (as seen through the error message) that I was in the .canonical namespace, but didn't like the package
[20:45] <asac> yeah then they didnt land it ompletely
[20:45] <asac> i know they were super close but had to migrate DB
[20:45] <mvo> jdstrand: do we need a backport of the click-reviewers-tools in the ppa:snappy-dev/tools (and/or beta)?
[20:45] <jdstrand> ok, that's fine
[20:45] <asac> but wanted to do that over weekend or something
[20:46] <jdstrand> mvo: so.. I was working on the review tools and then was asked to put them aside in favor of seccomp
[20:46] <jdstrand> mvo: I have a lot of changes that need to land but they aren't quite ready yet
[20:46] <jdstrand> this is for bugs and security yaml
[20:46] <mvo> jdstrand: no problem, I was just curious
[20:46] <asac> tyhicks: maybe the vmlinuz is already done (while it builds the module lot)?
[20:47] <mvo> jdstrand: I personally think that the seccomp stuff is more important to land
[20:47] <jdstrand> once I get through seccomp I'll pick that up again
[20:47] <asac> crazy times :)
[20:47]  * asac remembers the two weeks before first release for cloud
[20:48] <jdstrand> so, for anyone interested, lp:~snappy-dev/snappy-hub/docker is up to date with what is in the store and tagged
[20:48] <asac> thanks
[20:48] <jdstrand> so if people want to change the packaging, just do: snappy build ./package-dir
[20:49] <jdstrand> mvo: have I mentioned how I do snappy builds?
[20:49] <jdstrand> mvo: I don't use the tools for snappy
[20:50] <jdstrand> mvo: I fire up a snappy image then: scp -P 8022 ubuntu@localhost:/usr/bin/snappy /tmp ; /tmp/snappy build ...' :)
[20:50] <jdstrand> mvo: I guess static linking is good for mething :)
[20:50] <jdstrand> something
[20:56] <mvo> jdstrand: haha, nice.
[20:56] <tyhicks> asac: there were some file permissions related failures that stopped the build - it is running now
[20:57] <mvo> jdstrand: thats good so you tested the snappy go builds already, excellent
[20:57] <jdstrand> tyhicks: thank you for looking at that
[20:57] <jdstrand> mvo: always! :)
[20:57] <tyhicks> np
[20:57] <jdstrand> mvo: I then run them through my review tools branch
[21:03] <asac> tyhicks: local problems?
[21:03]  * asac ignores
[21:04] <tyhicks> asac: here you go: http://people.canonical.com/~tyhicks/bcm/linux-image-3.19.1-4-generic-bcm2709_3.19.1-4.4+kconfig1_armhf.deb
[21:05] <tyhicks> asac: unpack the deb and pull out the vmlinux file
[21:19] <tyhicks> asac: be sure to check your email - paolo was one step ahead of us and will have a more official build ready in a couple hours
[21:19] <mvo> sergiusens: sorry, but any idea what http://paste.ubuntu.com/10794788/ means and how I can get rid of it?
[21:20] <tyhicks> I'm not sure if you want to go through the image generation with my kernel or wait for his
[21:21] <asac> tyhicks: right now i want to try copying it hard to /boot :)
[21:22] <asac> not new image
[21:25] <tyhicks> that makes sense
[21:29] <asac> tyhicks: thanks! http://paste.ubuntu.com/10794885/
[21:29] <asac> it works :)
[21:30] <tyhicks> nice! :)
[21:32] <asac> well they die
[21:32] <asac> not sure whats going on :)
[21:32] <mvo> nice, and really nice to see the raspi2 oem snap from lool
[21:32] <asac> yeah
[21:32] <asac> thats cool
[21:33] <mvo> its comming togehter
[21:51]  * asac waves and goes to semi weekend and then travel :)