[06:54] <mborzecki> morning
[08:08] <pstolowski> morning
[08:15] <mborzecki> pstolowski: hey
[09:17] <mup> PR snapd#9851 closed: o/snapshotstate: fix returning of snap names when duplicated snapshot is detected <Bug> <Created by stolowski> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9851>
[09:27] <avn> Hello folks! What mean `cannot update snap namespace: cannot create writable mimic over "/": permission denied` when I use `bare` base snap?
[09:40] <pstolowski> avn: are you trying to use layouts at the same time?
[09:42] <avn> pstolowski: I'd like to have standalone  image, w/o base (with /nix properly bindmounted to root, if possible)
[09:42] <avn> If not, just make standalone image
[09:44] <avn> Someone on #snapcraft told me, that I need use `base: bare` stanza to have no depends
[10:07] <pstolowski> avn: right, that should work. in fact we have something like this run in our tests https://github.com/snapcore/snapd/blob/master/tests/lib/snaps/test-snapd-busybox-static/snapcraft.yaml
[10:08] <pstolowski> avn: perhaps create a forum topic and paste your snap.yaml (or snapcraft.yaml) so we can take a look
[10:09] <pstolowski> (i've just run test-snapd-busybox-static, it's in the store, and got no errors)
[10:09] <avn> pstolowski: will take a look, ty.  I have snap.yaml only, because I have snap built by nix, not snapcraft
[10:09] <pstolowski> avn: yeah, that's fine
[10:11] <pstolowski> avn: for a quick sanity test, sudo snap install --beta test-snapd-busybox-static and see if it works on your system
[10:14] <mup> Bug #1912615 opened: Snapd refresh doesn't recover from connection interruption <Snappy:New> <https://launchpad.net/bugs/1912615>
[10:24] <pstolowski> degville: hey, while looking at 'base: bare' i noticed https://snapcraft.io/docs/base-snaps has a copy-paste error
[10:24] <pstolowski> (for bare:)
[10:25] <degville> pstolowski: oh, thanks for letting me know - I'll fix it now.
[10:47] <mup> PR snapd#9853 opened: api: validate against validation set assert from the store <Needs Samuele review> <validation-sets :white_check_mark:> <Created by stolowski> <https://github.com/snapcore/snapd/pull/9853>
[11:31] <zyga> re
[11:31]  * zyga needs to tarball git snapd.git for ian 
[11:32] <zyga> avn, hey
[11:33] <zyga> avn, it means that the bare snap - which has almost nothing in it
[11:33] <zyga> avn, is the foundation of your mount namespace
[11:33] <zyga> avn, and that your snap defines a layout that adds a new top-level directory (somewhere in /) that doesn't exist there
[11:33] <zyga> avn, so snap-update-ns goes belly up and gives up
[11:33] <zyga> avn, can you paste your layout section of the snap please?
[11:38] <avn> zyga: https://gist.github.com/avnik/43ba955c2d857fffe6d3cded9a684f74  (and I planned to use proot to pseudo-mount /srv/nix -> /nix, because /nix is blacklisted top-level now)
[11:39] <avn> so I need add empty directories, if I use bare?
[11:40]  * pstolowski bbiab
[11:42] <zyga> avn, not exactly, let me look at your file now
[11:42] <zyga> avn, I think the bare snap doesn't have /srv
[11:42] <zyga> one sec
[11:42] <zyga> correct
[11:42] <zyga> avn, do you absolutely need /srv/nix?
[11:43] <zyga> if so, please open a bug against bare or just ask mvo here, to add an empty directory to the 'bare' snap
[11:43] <zyga> and then once that is released
[11:43] <zyga> you should be good to go
[11:43] <avn> I am absolutely need /nix ;) so I can use /lib/nix and proot for example
[11:43] <zyga> for /nix that's a different story
[11:44] <zyga> perhaps nix should be a base, like bare but explicitly for nix work
[11:44] <zyga> you really just need a snap like bare with that extra directory
[11:44] <zyga> have a look (snap download bare) at the bare snap
[11:44] <zyga> it's rather simple
[11:44] <zyga> there's some required structure
[11:44] <zyga> but bare was meant to be empty
[11:44] <avn> we have nix-base in store, but it stop works after blacklisting top-level items
[11:44] <zyga> so I'm not sure mvo will be happy to add more
[11:45] <zyga> hmm? what do you mean by "it stops work after blacklisting top-level items"?
[11:46] <avn> error: cannot read snap file: layout "/nix" defines a new top-level directory "/nix"` (is with /nix come from nix-base)
[11:48] <zyga> avn, it's a bug in snapd
[11:48] <zyga> mborzecki, ^
[11:48] <zyga> mborzecki, in snap/validate.go:446 we should allow nix if the base is nix-base
[11:49] <zyga> mborzecki, can you work with avn on getting this fixed
[11:49] <zyga> nix-base was something that was brought up in Montreal a few years back
[11:49] <zyga> but I guess it's not tested as a working base
[11:49]  * zyga is off to his open harmony work now
[11:50] <avn> probably we need a issue (we have issue in nixpkgs, about makeSnap not work anymore, but we need need it in smapd ;))
[11:50] <avn> (and I willing to package snapd to nixos, so will ask some more questions later)
[11:51] <zyga> sure, thank you
[11:51]  * zyga is no longer working on snapd but is happy to help from the side
[11:53]  * zyga goes afk for a while
[12:03] <avn> `cannot update snap namespace: cannot create writable mimic over "/": permission denied` looks like I walking by cicle
[12:47] <mborzecki> avn: please open a forum topic and include the logs from `SNAPD_DEBUG=1 SNAP_CONFINE_DEBUG=1 snap run <snapapp>`
[13:50] <mup> Bug #1912639 opened: Snap installs don't reliably resume on network flakiness <Snappy:New> <https://launchpad.net/bugs/1912639>
[13:53] <mup> Bug #1912639 changed: Snap installs don't reliably resume on network flakiness <Snappy:New> <https://launchpad.net/bugs/1912639>
[15:53]  * cachio lunch
[17:19] <zyga> stgraber, is there a way to check if "lxd init" was done from command line somehow?
[17:20] <stgraber> zyga: check if you have a default profile with root and nic device, that's usually what you want when you want to check if init was run
[17:20] <zyga> stgraber, how would I check that?
[17:21] <zyga> lxc profle list?
[17:21] <stgraber> zyga: lxc profile show or lxc profile device list
[17:21] <zyga> thanks, that's exactly what I wanted
[17:21] <zyga> I want to improve spread UX when used with lxd
[17:21] <zyga> cheers, thank you!
[17:22] <stgraber> `lxd init` isn't special, all it does is let you create storage pools and networks and some other config through a single command, so it's usually best to check for what you actually want. If it's to have usable containers, then best check if the default profile has the basics setup :)
[17:23] <zyga> I think right now I just want to guide people with first contact with spread and lxd together
[17:23] <zyga> stgraber, are you presenting at fosdem?
[17:23] <stgraber> Yep
[17:24] <zyga> cool, looking forward to that :)
[17:49] <zyga> niemeyer, could you please look at https://github.com/snapcore/spread/pull/112 when you have a moment
[17:49] <mup> PR spread#112: Bump base version of go to 1.13 <Created by zyga> <https://github.com/snapcore/spread/pull/112>
[17:54] <mup> PR snapd#9854 opened: gadget: pass sector size in to mkfs family of functions, use to select block sz <UC20> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9854>