[01:39] <ses__> I am getting “cannot communicate with server” issue when trying to install. Anyone knows how to resolve this issue? snapd seems to be running
[01:39] <ses__> sudo snap install --dangerous cwr_0.1_amd64.snap
[01:39] <ses__> error: cannot communicate with server: Post http://localhost/v2/snaps: dial unix /run/snapd.socket: connect: connection refused
[01:54] <thomi> ses__: what does "sudo systemctl status snapd.service" show?
[01:55] <ses__> thomi: http://pastebin.ubuntu.com/23855366/
[01:56] <thomi> https://wompwompwomp.com/ :(
[01:57] <thomi> hmmm
[01:57] <ses__> thomi: seems missing some text http://pastebin.ubuntu.com/23855373/
[01:57] <thomi> in any case, "Active: inactive (dead) (Result: exit-code) since Mon 2017-01-23 17:31:11 PST; 24min ago" doesn't sound healthy
[01:58] <thomi> I'm trying to recall where the logs are
[02:01] <thomi> ses__: I don't suppose you recently ran snapd from source, and now are trying to run the system version?
[02:04] <ses__> thomi: no
[02:04] <ses__> thomi: I restarted the machine but still having the issue
[02:04] <thomi> hmmm -  I'm not a snapd dev, and I'm not sure how to help you any more. I've encountered a similar issue once myself after running snapd from source. Since that doesn't match the situation you're in, I'm not sure what else to suggest
[02:05] <thomi> This timezone isn't great for catching the snapd devs - you might want to consider mailing the snapcraft mailing list
[02:05] <ses__> thomi: thanks
[02:05] <ses__> thomi: what time are they usually here? Timezone?
[02:07] <thomi> I believe they're mostly Europe/US - vague, I realise, sorry :D
[02:24] <azubieta> Hello, I'm traying to setup a snap store based on https://github.com/noise/snapstore but i'm getting this error: error: cannot communicate with server: Post http://localhost/v2/snaps/foobar25: EOF when I try to install a package. Any ideas ?
[02:31] <noise][> azubieta_: there a few things to be aware of… first, there's a branch "metadata_tests" that I have yet to merge that updates support for the newer API endpoints
[02:32] <azubieta_> noise: oh! so i must use the code from that branch instead ?
[02:33] <noise][> however, even with that, newer snapd versions will not install local snaps from that store because they will lack the assertions to verify their authenticity. snapd allows you to snap install foo.snap —dangerous from a local file (sideloading) but does not allow it for a remote store install
[02:34] <noise][> we have started discussing how to allow for different trust chains so your own store deployment can be trusted but we don't have firm plans or timeline for that currently
[02:34] <azubieta_> noise: i would like to create a fulle functional, snapd compatible and opensource snap store, but according to what you say they don't allow it
[02:35] <azubieta_> noise: besides your work is there another opensource project that i could check ?
[02:36] <noise][> that's correct for right now - we will allow that but at the moment you would need to work around the assertions check by doing a download and install separately
[02:36] <azubieta_> ok
[02:38] <noise][> i.e nothing is stopping a solution that fetches the snap files from a server and then does "snap install <snap file> —dangerous", but we aim to support alternate stores directly in snapd
[08:05] <mup> PR snapd#2666 closed: interfaces: add ability to set system time zone to timeserver_control interface <Created by justincan> <Closed by justincan> <https://github.com/snapcore/snapd/pull/2666>
[08:05] <mup> PR snapd#2679 opened: Ubuntu/14.04 <Created by vosst> <https://github.com/snapcore/snapd/pull/2679>
[08:05] <mup> PR snapd#2585 closed: debian: move systemd files out of ./debian and into ./data/systemd <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/2585>
[08:14] <zyga> good morning
[10:33] <niemeyer> Mornings
[10:38] <mup> PR snapd#2666 closed: interfaces: add ability to set system time zone to timeserver_control interface <Created by justincan> <Closed by justincan> <https://github.com/snapcore/snapd/pull/2666>
[10:38] <mup> PR snapd#2679 opened: Ubuntu/14.04 <Created by vosst> <https://github.com/snapcore/snapd/pull/2679>
[10:38] <mup> PR snapd#2585 closed: debian: move systemd files out of ./debian and into ./data/systemd <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/2585>
[11:36] <om26er> Hi! What endpoint does snap info call ?
[12:32] <zyga> om26er: hey
[12:32] <zyga> om26er: I think that's a question for chipaca
[12:32] <zyga> om26er: I bet it also depends on the version of snapd as that area saw some development
[12:34] <om26er> zyga: Ok, will ask him, I needed information about available revisions of snaps from different channel, I could use grep for that but was looking if there was cleaner way I could achieve that
[12:37] <Chipaca> you called?
[12:38] <zyga> Chipaca: hey
[12:38] <zyga> 12:36 < om26er> Hi! What endpoint does snap info call ?
[12:38] <zyga> :-)
[12:38] <jibel> om26er, if you want info directly from the store you can always use something like : curl -s https://search.apps.ubuntu.com/api/v1/snaps/details/<SNAP>?channel=<CHANNEL> -H 'X-Ubuntu-Series: 16' -H 'X-Ubuntu-Architecture: <ARCH>'
[12:38] <Chipaca> om26er, why do you ask?
[12:39] <om26er> Chipaca: I need to get available revisions for a snap in different channels
[12:40] <Chipaca> om26er, what for?
[12:41] <om26er> Chipaca: for CI purpose whenever something is merged in snapweb master, it gets pushed to edge channel automatically, I need to check if the newly pushed snap is published before trying to install it and run tests on top of that.
[12:41] <Chipaca> om26er, doesn't snapcraft already give you that info?
[12:42] <Chipaca> or are these things disconnected? the pushing and the checking i mean
[12:42] <Chipaca> om26er, the store is still working on exposing this information, so right now for 'snap info' i'm doing a separate (rather arcane) query just for that
[12:43] <Chipaca> om26er, hitting /v2/find?name=foo on snapd will get you the channel map, if that's what you need
[12:43] <om26er> Chipaca: I haven't looked at the output of snapcraft push, if it returns that result, we can probably use that as well.
[12:43] <Chipaca> yes, snapcraft push returns the channel map
[12:44] <Chipaca> from SCA
[12:44] <Chipaca> snapd talks to CPI
[12:44] <Chipaca> if you've already got snapcraft talking to SCA, that's better for this than having snapd talk to CPI for it
[12:45] <Chipaca> om26er, let me kknow if that's covered what you need please
[12:46] <Chipaca> om26er, please ACK so I can move on from this
[12:47] <om26er> Chipaca: yes, one of our script uploads to the store through snapcraft, so will get the output from there.
[12:47] <om26er> Chipaca: thanks for the info
[12:47] <Chipaca> np
[12:50] <om26er> jibel: yeah, just tried, that endpoint seems to work as well.
[13:57] <stokachu> so ive got my snap working on 16.04 with a systemd script, 14.04 is throwing this error at me though http://paste.ubuntu.com/23857838/
[13:57] <stokachu> do i have to define anything differently to get my systemd scripts working for 14.04 in a snap env?
[14:29] <mhall119> sergiusens: what's the proper way for a snapcraft test case to handle downloading a source file?
[14:43] <elopio> mhall119: unit test or integration test?
[15:00] <mhall119> elopio: integration I would think?
[15:04] <elopio> mhall119: for integration, you can probably put your source in people.ubuntu.com, write a real snapcraft.yaml that uses it, and call the pull command in the test.
[15:04] <mhall119> ok, cool, thanks elopio
[15:06] <elopio> mhall119: there is an ftp you can use as a guide in snapcraft/integration_tests/snaps
[15:06] <mhall119> elopio: just found that one
[15:12] <sergiusens> mhall119, for the unit test we create files on the fly
[16:51] <ryebot> Is there a way to prevent the snap name prefix from being added to a snap command? For example, I have a snap with the name "cni-loopback" and the command "loopback". The generated command is "cni-loopback.loopback". Is there a way to make the command name simply "loopback"? (without renaming my snap to loopback)
[16:53] <kyrofa> ryebot, support was recently added for command aliases
[16:53] <kyrofa> ryebot, which essentially allows you to promote prefixed commands into the non-prefixed domain
[16:53] <ryebot> kyrofa: excellent, I can google now, thank you :)
[16:54] <ogra_> ryebot, https://github.com/snapcore/snapcraft/blob/master/integration_tests/snaps/alias/snapcraft.yaml
[16:54] <ogra_> there is an example
[16:54] <kyrofa> ryebot, note that it requires snapd v2.20 or later
[16:54] <ryebot> ogra_ kyrofa: you guys rock, thanks for the help!
[16:55] <kyrofa> Any time :)
[16:56] <ogra_> (sometimes we also roll ;) )
[16:56] <kyrofa> When we eat too much
[16:56] <ogra_> haha
[16:57] <ryebot> XD
[17:01] <cachio> niemeyer, hey, I was trying to import spread tests in our grafana instance, and I was wondering if should be make spread to export test results in a well know format so it is easy to import from anywhere?
[17:01] <cachio> niemeyer, I can add a mp if you think it would be a good idea
[17:02] <niemeyer> cachio: Yeah, that sounds nice for sure
[17:02] <niemeyer> cachio: I suggest doing that as a small function which is run at the very end of the runner's life cycle
[17:03] <niemeyer> cachio: We already have a stats type and value at hand, so it should be super easy to just take that as an argument and generate a file in a well known format based on an option which the runner already has easy access to
[17:04] <cachio> niemeyer, ok, make sense, any preference with the output format?
[17:05] <niemeyer> cachio: Are there a few options which grafana can already interpret, or is that manual anyway?
[17:05] <cachio> niemeyer, the we run a tranlator to export it to grafana
[17:06] <cachio> we already have for pyunit for example
[17:07] <cachio> niemeyer, so I need then either to send from travis to grafana the resutls, or to import it from jenkins and send it to grafana
[17:08] <cachio> niemeyer, should be easier if we could send directly from travis to grafana which is a production service hosted in prodstack
[17:10] <niemeyer> cachio: If you need to manually parse and translate into grafana anyway, then I wouldn't worry about changing spread, at least I wouldn't begin there
[17:16] <cachio> niemeyer, I already have the translation from xunit pyunit into grafana schema
[17:16] <niemeyer> cachio: Yeah, xunit is probably a good choice
[17:17] <cachio> niemeyer, ok, i'll implement that
[17:24] <cachio> niemeyer, are you already sending spred results to any canonical service?
[17:24] <niemeyer> cachio: Nope..
[17:45] <AlbertA> ogra_: alecu: following up on the post to the snapcraft ML about GFX on pi3...
[17:46] <AlbertA> it seems the latest snapd is no longer autoconnecting the mir-libs interface? at least that's what I'm seeing with ogra_'s latest image from http://people.canonical.com/~ogra/snappy/all-snaps/daily/current/
[17:46] <ogra_> AlbertA, it does for me
[17:47] <ogra_> i have to manually connect the mir interface, but mir-libs is autoconnected
[17:47] <AlbertA> ogra_: alecu: mir-kiosk:mir-libs is autoconnected for you? and which snap version are you running?
[17:47] <AlbertA> snap list
[17:47] <AlbertA> Name        Version        Rev  Developer  Notes
[17:47] <AlbertA> core        16.04.1        970  canonical  -
[17:47] <AlbertA> mir-kiosk   0.1            20   canonical  -
[17:47] <AlbertA> mir-libs    0.1            20   canonical  -
[17:47] <AlbertA> pi2-kernel  4.4.0-1040-47  26   canonical  -
[17:47] <ogra_> ogra@localhost:~$ snap version
[17:47] <ogra_> snap    2.21+ppa215.5a5f1500-1
[17:47] <AlbertA> pi3         16.04-0.5      14   canonical  -
[17:48] <AlbertA> ogra_: oh but without --devmode ?
[17:48] <ogra_> yep ... worked for me (i dont have any mir stuff on the current image though)
[17:48] <ogra_> gimme a moment
[17:49] <alecu> I found it odd that devmode is gone after disabling and reenabling a snap
[17:49] <alecu> Finishing lunch, I'll try it in a few minutes
[17:49] <ogra_> might be a feature ... not sure ...
[17:50] <AlbertA> alecu: so in an any case, you can connect it manually - snap connect mir-kiosk:mir-libs mir-libs:mir-libs...then have to workaround a snap content i/f bug
[17:50] <ogra_> zyga, niemeyer ^^^ if you dis/enable a snap devmode gets dropped, is that wanted ?
[17:50] <ogra_> AlbertA, hmm, right, not connected here either now
[17:51] <AlbertA> do: snap disable mir-kiosk; sudo /usr/lib/snapd/snap-discard-ns mir-kiosk; snap enable mir-kiosk
[17:52] <AlbertA> ogra_: ok, I'll read the content i/f docs.. maybe something changed now
[17:52] <ogra_> well, the namespace stuff landed and the gadget grew support for gpio interfaces in core
[17:52] <ogra_> neither should have caused an issue though
[17:53] <AlbertA> ogra_: yeah well just thinking maybe I'm missing a field or something when specifying the content i/f plug now
[17:53] <ogra_> ogra@localhost:~$ snap interfaces|grep mir
[17:53] <ogra_> :network                  mir-kiosk-apps,pulseaudio
[17:53] <ogra_> :opengl                   mir-kiosk,mir-kiosk-apps,unity8-session
[17:53] <ogra_> mir-kiosk:mir             mir-kiosk-apps
[17:53] <ogra_> mir-libs:mir-libs         mir-kiosk-apps
[17:53] <ogra_> -                         mir-kiosk:mir-libs
[17:54] <ogra_> so mir-kiosk-apps autoconnect
[17:54] <ogra_> mir-kiosk doesnt
[17:54] <AlbertA> huh.... interesting.
[17:55] <AlbertA> I'll take a look at that, I did change the snapcraft.yaml last time
[17:55] <ogra_> ah
[17:56] <AlbertA> I'll revert that change and republish
[18:03] <Blu2> Will we ever see the promised snapped firefox?
[18:11] <kyrofa> Blu2, I expect so, but it's not being done by us
[18:13] <AlbertA> alecu: ogra_: ok a new revision of mir-kiosk was just pushed (rev 22 for armhf) that autoconnects fine
[18:13] <AlbertA> to mir-libs
[18:13] <alecu> Wonderful
[18:14] <Blu2> kyrofa, I know, I was hoping somebody knew something about it here :)
[18:15] <kyrofa> Blu2, not me anyway. That's all mozilla
[18:15] <ogra_> AlbertA, thanks !
[18:21] <Blu2> kyrofa, I thought they may be here in this chat
[18:21] <kyrofa> Blu2, fair enough, they may be :)
[18:28] <ses__> I am having issue communicating with the server during installation snapd seems to be running okay but have some issue. Anyone knows how to resolve this issue https://pastebin.ubuntu.com/23859088/
[18:29] <ogra_> ses__, that doesnt seem to be running
[18:29] <ogra_> Jan 24 09:02:11 me-vm systemd[1]: snapd.service: Start request repeated too quickly.
[18:29] <ogra_> Jan 24 09:02:11 me-vm systemd[1]: Failed to start Snappy daemon.
[18:30] <ses__> ogra_: https://pastebin.ubuntu.com/23859105/
[18:32] <ogra_> well, systemd disagrees ... and you should also not see two snapd processes ... looks more like something hangs or respawns very fast
[18:32] <ogra_> if you do the ps -A again i bet you see new pids
[18:32] <ogra_> what are you running this on ? is that a native ubuntu install ?
[18:33] <ses__> I see the same pids
[18:33] <ses__> 16.04
[18:33] <ogra_> using a normal ubuntu kernel ? (uname -a ? )
[18:33] <ses__> apt install
[18:33] <ses__> Linux me-vm 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
[18:33] <ogra_> looks ok
[18:34] <ogra_> does snap list work ?
[18:34] <ogra_> (if so, which core snap is installed ? )
[18:35] <ses__> No it doesn’t work
[18:35] <ses__> Cannot communicate with the server
[18:35] <ogra_> right ...
[18:36] <ogra_> ls -l /snap/*core
[18:36] <ogra_> does that return anything ?
[18:36] <ses__> ogra_: yes. I see “1357 current” dirs
[18:37] <ogra_> thats ok too
[18:37] <ogra_> i wonder why it doesnt start ...
[18:37] <ogra_> anything in syslog ?
[18:38] <ses__> ogra_: there is something in syslog. Any key words I search for?
[18:42] <zyga> ogra_: (as for devmode being dropped, probably not but not sure (I wish we would write design down)
[18:42] <zyga> )
[18:42] <zyga> I hate when I drop )
[18:42] <ses__> ogra_: maybe this is relevant https://pastebin.canonical.com/176943/
[18:45] <ogra_> zyga, btw, ses__ is the third person in 4 days that has a non-starting snapd
[18:46] <zyga> ogra_: !!!!
[18:46] <zyga> ogra_: can you tell me more?
[18:46] <ogra_> ses__, hmm, do you have livepatch installed ?
[18:46] <ses__> ogra_: yes, there was other people having the same issue last night in this channel.
[18:48] <ses__> ogra_: I didn’t install livepatch
[18:48] <ogra_> ses__, ah, no, i was confused by the kernel messages in the paste
[18:48] <ogra_> zyga, any idea ? https://pastebin.canonical.com/176943/
[18:49] <ses__> ogra_: but I installed snapd yesterday
[18:49] <ogra_> ses__, and you didnt have snapd installed before ?
[18:49] <ses__> ogra_: first time installing it on a new machine
[18:50] <ogra_> (you seemingly have /snap/ubuntu-core there instead of /snap/core ... that kind of indicates an older install )
[18:50] <ogra_> (new installs should always get the core snap installed, not ubuntu-core anymore)
[18:51] <zyga> looking
[18:51] <zyga> bloody hell 2fa
[18:51] <ogra_> heh
[18:51] <ogra_> yeah
[18:52] <ogra_> snapd[18866]: error: cannot patch system state from level 3 to 4: cannot get snap state    for "cwr": <nil>
[18:52] <ogra_> seems the most relevant bit
[18:52] <alecu> ogra_: AlbertA: with the latest mir-kiosk, I get the black screen and (laggy!) pointer on the raspi2. But, when I try to start the mir-kiosk-apps all of mir freezes on the second frame, just like what I saw yesterday on the raspi3
[18:52] <zyga> ok logged in
[18:52] <ogra_> alecu, disconnect/connect ?
[18:52] <zyga> that bug is fixed in master I think
[18:53] <ogra_> alecu, i usually need to do that once for the -apps
[18:53] <zyga> and I think it was released in 2.21
[18:53] <alecu> ogra_: after a disconnect and connect, yes.
[18:53] <ogra_> zyga, "released"
[18:53] <ogra_> zyga, us normal users all have 2.20 still
[18:53] <zyga> upstream release
[18:53] <zyga> blame the SRU process
[18:53] <ogra_> 2.20.1ubuntu1 to be precise
[18:53] <zyga> what can I do?
[18:53] <ogra_> dunno
[18:53] <alecu> ogra_: sorry, after a disable and enable of the snap package. Will try disconnect
[18:54] <ogra_> zyga, trust your colleagues i was told :P
[18:54] <pedronis> anyway that shows trying to use snapd before upgrading snapd
[18:54] <zyga> ogra_: I trust all of my colleagues
[18:54] <ogra_> alecu, yeah, that needs both ... disable, disconnect, connect, enable
[18:55] <zyga> let's see when we can make it available to everyone
[18:55] <ogra_> alecu, like the mir wiki describes
[18:55] <ogra_> and at some point the content interface will just woork ;)
[18:56] <ogra_> if you have the pointer on black screen mir itself is definitely running fine
[18:57] <ogra_> my kodi snap is sadly currently broken (i tried to build the latest master which has the mir patches but also broken kodi ... ) ... so dont bother with that
[19:01] <ses__> ogra_: is there anything I can now to go around this issue?
[19:01] <ogra_> ses__, do you have many snaps installed already ?
[19:01] <ogra_> i'd try to purge snapd and install it again
[19:01] <ogra_> perhaps that helps ...
[19:02] <ogra_> (but thats just ut of desparation ... )
[19:02] <ses__> ogra_: should I also uninstall snap?
[19:02] <ogra_> i know it works on all my xenial installs over here
[19:02] <ogra_> snap is a commmand shipped by the snapd package
[19:02] <ogra_> so purging snapd should be enough
[19:02] <ogra_> and then just install t again
[19:03] <ogra_> then try something from the store ... like snap install htop ... that should pull in the core snap alongside
[19:03] <ogra_> once you knwo it works, you can start plying with your local snap that you tried to install before
[19:04] <ses__> ogra_: ok, will do “sudo apt-get remove --purge snapd”
[19:04] <ogra_> sudo apt purge snapd ... less typing ;)
[19:04] <ogra_> (same thing though)
[19:07] <AlbertA> alecu: you will need --devmode
[19:07] <AlbertA> alecu: I'm seeing some new syscalls with this driver, so I'll need to update the mir interface
[19:08] <alecu> AlbertA: devmode for mir-libs, mir-kiosk and mir-kiosk-apps ?
[19:08] <AlbertA> alecu: mir-kiosk and mir-kiosk-apps yeah
[19:09] <AlbertA> the interesting part is that ps shows miral-kiosk as defunct but yet it still runs...
[19:11] <ogra_> magic ;)
[19:12] <ogra_> (also known as "the zombie apocalypse is near")
[19:22] <alecu> AlbertA: ogra_: after installing both -kiosk and -kiosk-apps with devmode, it all seems to be working ok on the raspi 2.
[19:22] <alecu> thanks a lot!!!
[19:24] <kyrofa> alecu, "ok" = greater than a single frame?
[19:24] <alecu> kyrofa: I get plenty of frames now :-)
[19:24] <alecu> no end in sight
[19:24] <kyrofa> alecu, I really wanted to reply to your email and say "stop moving the mouse!"
[19:24] <alecu> lol :-)
[19:25] <kyrofa> alecu, nice to see you around by the way!
[19:40] <ogra_> alecu, awesome ... sorry that you had such a bumpy ride
[19:43] <alecu> it's the early days of the raspi image... totally understandable.
[19:51] <ryebot> kyrofa: I'm hitting some issue with the aliases, any idea what I might be doing wrong? https://gist.github.com/wwwtyro/aa34ccb81f6928f2bda37b32c7a00c1f
[19:52] <kyrofa> ryebot, I know you need to enable them somehow (it's not done automatically without an assertion that happens store-side)
[19:53] <kyrofa> ryebot, `snap alias` perhaps?
[19:53] <ryebot> ah, okay
[19:53] <ryebot> so it might not work if installed locally?
[19:53] <kyrofa> ryebot, not work == not automatically enabled? Yes
[19:54] <ryebot> kyrofa: gotcha, thanks. seems to work!
[19:54] <ryebot> thanks again!
[19:54] <kyrofa> ryebot, excellent! Of course
[19:55] <kyrofa> jdstrand, how does one request aliases to be automatically granted? Is it all manual right now, or is there a process for it?
[19:56] <jdstrand> kyrofa: it's manual
[20:03] <stokachu> jdstrand, is there anyone familiar with systemd wrt 14.04 snaps?
[20:03] <stokachu> jdstrand, trying to figure out why my snap is failing to install
[20:04] <ogra_> ses__, did you get anywhere with reinstalling snapd ?
[20:04] <jdstrand> stokachu: tvoss spearheaded the effort and I think slangasek may have poked at systemd, but perhaps ask your question here and maybe someone will know
[20:05] <stokachu> jdstrand, thanks
[20:05] <stokachu> it was basically this email https://lists.ubuntu.com/archives/snapcraft/2017-January/002706.html
[20:05] <stokachu> it just seems to not find a systemd service file
[20:05] <ses__> ogra_: I am trying it now. Distracted by other tasks
[20:05] <ogra_> ah, no worries
[20:05] <jdstrand> Main PID: 1548 (code=dumped, signal=SEGV)
[20:06]  * ogra_ grins about stokachu's last paragraph in the mail ... getting rid of maintainer scripts are one of the reasons we started snaps :)
[20:06] <stokachu> there is no snap.conjure-up.bridge.service in /etc/systemd/system
[20:06] <stokachu> but that does exist in 16.04
[20:07] <jdstrand> stokachu: if I had to guess, thinking it is a series 16 built snap with 14.04 libraries thing. this is probably related to the asciinema thread and friends that sergiusens is working on
[20:07] <jdstrand> stokachu: if a service fails to start it fails the install and cleans up after itself
[20:07] <stokachu> ah the email from mark?
[20:07] <tvoss> o/
[20:07] <stokachu> jdstrand, yea my snap never got installed b/c it hits that systemd error
[20:08] <jdstrand> stokachu: that whole thread, yeah-- there are complexities with series 16 built stuff on a 14.04 system that aiui, aren't being handled all the time
[20:08] <stokachu> ok yea, this looks like my systemd service file never makes it onto the system
[20:08] <tvoss> jdstrand: the issue mostly evolves around snaps using classic confinement, though
[20:08] <stokachu> tvoss, yea this is classic
[20:08] <jdstrand> stokachu: you might try turning that into a command (comment out 'daemon: ...', then install, then do 'snap run --shell conjure-up.bridge' and see if you can't debug better
[20:09] <tvoss> stokachu: how do you try to install the service file?
[20:09] <stokachu> tvoss, https://github.com/conjure-up/conjure-up-snap/blob/master/snapcraft.yaml#L16-L20
[20:09] <stokachu> jdstrand, ok i can try that
[20:10] <tvoss> stokachu: do you have a snap handy for testing?
[20:10] <stokachu> what if i run snapcraft on the 14.04 system and build from there?
[20:10] <stokachu> tvoss, yea one sec
[20:10] <stokachu> tvoss, actually you can do sudo snap install conjure-up --classic --edge
[20:10] <stokachu> it's the same one i do for xenial that works
[20:11] <stokachu> err snap download i guess
[20:11] <jdstrand> stokachu: I'm not sure snapcraft is available for 14.04 yet (but I'm not tracking that work)
[20:11] <tvoss> stokachu: let me clean up my testing environment
[20:11] <kyrofa> stokachu, as it stands, snapcraft doesn't run on trusty
[20:11] <kyrofa> (it has xenial-only deps)
[20:11] <stokachu> jdstrand, kyrofa ah ok
[20:11] <stokachu> didnt know if that would make a difference
[20:12] <kyrofa> tvoss, is the core snap on trusty the same as on xenial (i.e. is it still really xenial?)
[20:12] <kyrofa> Err, series 16 I guess
[20:12] <tvoss> kyrofa: yup, it's a series 16 core
[20:13] <kyrofa> tvoss, so we don't anticipate libc symbol issues if we build on xenial and run on trusty?
[20:13] <kyrofa> I hit that back in the day, but it may have been before we actually had a core snap. Everything blurs together
[20:14] <jdstrand> kyrofa: curious, with the lxc stuff, is snapcraft needed inside the container or can snapcraft from outside drive commands inside?
[20:14] <jdstrand> err, lxd*
[20:14] <tvoss> kyrofa: the assumption is to redirect everything to the core snap, and not pull in ABI from the host. classic is the exception here
[20:14] <kyrofa> tvoss, indeed, okay, makes sense
[20:15] <kyrofa> jdstrand, good question. I think the biggest requirement for it to be on the system is fetching stage packages
[20:15] <kyrofa> It also uses the container's sources.list by default for build-packages
[20:16] <stokachu> jdstrand, yea that asciinema thread is pretty much the same thing im hitting too it seems
[20:16] <ses__> ogra_: I was able to install htop. I guess it is working but having issue installing my own snap “Mount snap "cwr" (unset) (snap "cwr" requires consent to use classic confinement)”
[20:16] <ogra_> ses__, sounds like you want --classic in your snap install command
[20:17] <kyrofa> jdstrand, basically, every time snapcraft execs something else, we'd need to check to see if we need to exec in a container or on the host
[20:18] <kyrofa> jdstrand, and how that happens depends on what command is being run. For fetching stage packages we use the python3 apt API, so that's a big one
[20:18] <jdstrand> kyrofa: I don't know if this is at all helpful, but if the stage packages were broken out into a freestanding script, xenial host could copy stage-package script to trusty container, fetch stuff, then go from there. I suspect wanting lxd to build different series is interesting, but 14.04 is clearly the exception. series 18 would have snapcraft
[20:19] <jdstrand> well, python3-apt should be in trusty
[20:19] <kyrofa> jdstrand, yeah, but how do you use it if you're not in the container?
[20:20] <jdstrand> it isn't terribly interesting so long as we have series 16 core on trusty though I think
[20:20] <stokachu> so sergiusens mentioned having a python3 part, is that something I could do as a workaround for this issue?
[20:21] <jdstrand> kyrofa: I figures start the conteriner, lxc push it, lxc exec it, etc
[20:21] <jdstrand> kyrofa: but, I'm not saying you should do it. you guys have given this way more thought than I :)
[20:21] <kyrofa> jdstrand, ah sorry, I was referring to python3-apt being in trusty, not the script
[20:22] <kyrofa> jdstrand, yeah I think it really comes down to "snapcraft wasn't written that way." Not to say we won't get there eventually, it's just a question of the shortest path
[20:22] <tvoss> stokachu: so start of the bridge service fails, with the executable segfaulting. For that, the snap is removed immediately
[20:23] <tvoss> stokachu: and thus no service file :)
[20:24] <stokachu> tvoss, so should i do jdstrand's suggestion and try to run it as a script?
[20:24] <tvoss> stokachu: yup, that would be a good first step
[20:24] <ses__> ogra_: used —classic but got “error: cannot find signatures with metadata for snap cwr_0.1_amd64.snap" ?
[20:24] <stokachu> ok lemme try that
[20:26] <ses__> ogra_: snapcraft.yaml https://pastebin.canonical.com/176952/
[20:27] <stokachu> tvoss, jdstrand: so doing snap run --shell conjure-up.bridge starts my interface and applies the iptables rules
[20:28] <kyrofa> ses__, you need --dangerous as well
[20:29] <kyrofa> ses__, http://pastebin.ubuntu.com/ is your non-2fa-protected friend
[20:29] <tvoss> stokachu: hmmm, that's funky
[20:29] <jdstrand> stokachu: hmm. did you have to snap connect anything?
[20:29] <tvoss> stokachu: would you mind trying to call conjure-up without snap run?
[20:30] <stokachu> jdstrand, nah as long as lxd is installed on the host
[20:30] <stokachu> http://paste.ubuntu.com/23859714/
[20:30] <stokachu> thats from journalctl
[20:30] <stokachu> lemme try running conjure-up
[20:30] <jdstrand> oh duh, its classic
[20:30] <ses__> kyrofa: sorry url autocomplete
[20:30] <jdstrand> ses__: use --dangerous for your cannot find signatures error
[20:30] <stokachu> conjure-up
[20:30] <stokachu> Segmentation fault (core dumped)
[20:31] <stokachu> :(
[20:32] <tvoss> jdstrand: ^
[20:32] <stokachu> Jan 24 20:30:50 darthbawlz kernel: [24152.656439] traps: conjure-up[3152] general protection ip:7f26c316a1ee sp:7ffe79c932e0 error:0 in libc-2.23.so[7f26c3027000+1bf000]
[20:32] <stokachu> is in my syslog
[20:34] <jdstrand> libc-2.23.so is xenial's libc. trusty's is libc-2.19
[20:35] <stokachu> im guessing that gets pulled in during snapcraft build
[20:35] <jdstrand> I don't have the details, but I remember that there were issues on xenial when snaps tried to use a  shipped libc instead of the system one
[20:36] <jdstrand> if I were to guess, I'd guess this is the same issue. I think this is the thread I was mentioning before with the dynamic linker, etc
[20:36] <jdstrand> I've not looked in the issue. others in this channel I believe are actively looking at it
[20:37] <stokachu> ok, sounds like a decision needs to be made whether to use the system's libs in a classic snap?
[20:39] <stokachu> strace shows this open("/snap/core/current/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
[20:40] <jdstrand> stokachu: the only thing I can suggest otoh is adjust LD_LIBRARY_PATH or running your command with /lib/x86_64-linux-gnu/ld-2.19.so $SNAP/bin/your.executable ...
[20:40] <jdstrand> actually
[20:41] <jdstrand> you would want to do /snap/core/current/lib/x86_64-linux-gnu/ld-2.23.so ...
[20:41] <stokachu> still segfaults it seems
[20:41] <jdstrand> anyway, I suspect with effort, you'd be able to use the right set of libraries then take that into a wrapper script for your command
[20:42] <stokachu> jdstrand, ok, but this is something that can be dealt with in snapcraft at some point?
[20:42] <jdstrand> stokachu: that is what the thread is about
[20:42] <stokachu> ok, thanks, at least it's a known issue
[20:43] <jdstrand> and, aiui, people are trying to figure out how to make this work well for people. it is rough now
[20:43] <stokachu> jdstrand, all good, it works fine on xenial. having trusty is just icing on the cake
[20:44] <stokachu> jdstrand, tvoss thanks for looking into it
[20:47] <jdstrand> stokachu: np. keep an eye on that thread and the other related threads on the snapcraft list and hopefully it'll get resolved soon
[20:47] <stokachu> jdstrand, sounds good, will do
[20:49] <mhall119> sergiusens: why does snapcraft require the core snap to be installed on the build-machine when using the classic interface?
[20:49] <kyrofa> mhall119, so it can use its linker
[20:49] <mhall119> ah, ok
[20:50] <mhall119> makes it kind of hard to build in lxc then
[20:50] <kyrofa> mhall119, indeed
[20:50] <kyrofa> mhall119, or LP
[20:51] <kyrofa> mhall119, it's a known issue
[20:51] <mhall119> or on my host, until that update that converts me off ubuntu-core
[20:51] <kyrofa> Ah, yes, that as well
[20:51] <mhall119> kyrofa: ok, as long as it's on someone's list to fix, I'll wait patiently
[20:51] <kyrofa> mhall119, yeah, it's very rough right now, we know
[20:53] <kyrofa> Thanks for bearing with us!
[21:02] <tvoss> stokachu: np
[21:09] <tvoss> stokachu: you might want to watch https://bugs.launchpad.net/snapd/+bug/1657504
[21:09] <stokachu> tvoss, thanks i subscribed to it
[21:44] <ryebot> Is it possible for one snap to execute another snap binary in /snap/bin without using classic confinement?
[21:44] <ryebot> e.g., using some interface?
[21:48] <kyrofa> ryebot, I'm afraid not. Even if there were, there's no way for snap A to even know that snap B is installed (or request for it to be installed)
[21:49] <ryebot> kyrofa: understood, thanks!
[21:50] <kyrofa> ryebot, can you explain what you're trying to accomplish?
[21:50] <ryebot> kyrofa: certainly: I'm wanting to snap up multiple CNI plugins, and they sometimes want to execute one another
[21:51] <ryebot> They're pluggable, too, so I can't put them all in the same snap
[21:52] <kyrofa> ryebot, CNI?
[21:52] <ryebot> I /think/ I can do what I need with classically-confined snaps (barring dealing with possibly hardcoded plugin names!), but wanted to know if it was possible with strict confinement
[21:52] <ryebot> yeah, Container Networking Interface, iirc
[21:52] <ryebot> Basically, a bunch of binary files that sometimes call out to one another
[21:53] <kyrofa> ryebot, within what execution context? i.e. what loads the plugins? (no idea what CNI is)
[21:53] <ryebot> In our use case, kubernetes
[21:53] <ryebot> (and other plugins, of course)
[21:54] <kyrofa> ryebot, so is there a kubernetes snap, and you want to create snaps of its plugins?
[21:55] <ryebot> We'll probably be making a kubernetes snap, and yes, it will need to call its plugins that we're hoping to deliver as snaps
[21:55] <kyrofa> ryebot, bear with me, while I know what kubernetes is I've never used it. How does it "discover" plugins?
[21:56] <ryebot> the node agent, kubelet, is started with a cli argument or env var that points to the directory which contains all the plugins
[21:57] <ryebot> which looks like it's gonna be /snap/bin instead of the typical /opt/cni/bin (that's another thing I wasn't planning on bringing up yet!)
[21:57] <kyrofa> ryebot, and it crawls the directory upon startup, thereby obtaining a list of plugins that are available?
[21:57] <ryebot> As far as I understand, yes
[21:57] <kyrofa> ryebot, it sounds like you need bug #1655125
[21:57] <kyrofa> Hmm... the bot's gone
[21:58] <kyrofa> https://bugs.launchpad.net/snappy/+bug/1655125 rather
[21:58] <ryebot> cool, thanks, I'll take a look :)
[21:58] <ryebot> I need to step into a meeting, thanks for your help, I'll be back to bug you more, I'm sure :D
[21:58] <kyrofa> ryebot, please do add a comment a mark yourself affected if you agree
[21:58] <ryebot> +1 will do!
[22:10] <BLu2> weird, just had to reinstall hexchat snap, because it would keep crashing on start up