/srv/irclogs.ubuntu.com/2021/06/03/#snappy.txt

mwhudsondoes anyone know why 00:02
mwhudsonlxc delete --force wtf-snapd; lxc launch ubuntu-daily:groovy wtf-snapd -c security.privileged=true; sleep 5; lxc exec wtf-snapd -- bash -c "apt-get update && apt-get install snapd"00:02
mwhudsonmight hang?00:02
mwhudsonit the privileged is important and it seems to be something around mounting the snapd snap00:03
mwhudsonrelated to the above https://paste.ubuntu.com/p/XPz7b5s5MY/09:06
pedronismwhudson: I think something like that is done when you turn on parallel instances,  but I probably lost the beginning of this conversation09:34
pedronishere09:34
mwhudsonpedronis: lxc delete --force wtf-snapd; lxc launch ubuntu-daily:groovy wtf-snapd -c security.privileged=true; sleep 5; lxc exec wtf-snapd -- bash -c "apt-get update && apt-get install snapd" hangs09:34
mwhudsonare parallel instances enabled by default these days09:35
pedronisthey shouldn't09:35
mwhudsonpedronis: although that's a bit of a red herring, just launch a privileged lxc ubuntu-daily:groovy and admire how much snapd is not working09:35
pedronismwhudson: did it work before? I don't think we test priveleged containers09:43
mwhudsonpedronis: yeah it started failing a few days ago (it hangs in the subiquity github actions)09:43
mwhudsonhm well09:43
mwhudsonit possibly only shows up on upgrade, i don't think we depend on snapd working inside the container09:44
pedronisanyway, no we do such a mount in another case, but this is code that was there since a long time09:46
pedronisI'm trying to give you pointer09:46
pedronismwhudson: it's related to / itself not being mounted shared fwiw I think09:48
pedronismwhudson: https://github.com/snapcore/snapd/blame/master/cmd/snapd-generator/main.c#L4609:49
pedronismwhudson: this was the original PR https://github.com/snapcore/snapd/pull/479709:50
pedronismwhudson: basically if / is not mounted as shared we create a generated unit that remounts /snap as shared09:52
pedronisbut we do this since a long time09:52
pedronismwhudson: so something else than snapd might have changed in that area? 10:12
pedronismardy: hi, I re-reviewed https://github.com/snapcore/snapd/pull/1028211:39
chaologyhi o/12:34
chaologydoes anyone know whether snaps eventually got confinement on Fedora using SELinux as the confinement backend? I know that AppArmor handles the confinement on Ubuntu based systems12:34
chaologyfrom the following and from the looks of the commit history within snapd repo on github it looks like there has been a lot of work around selinx, but I'm not experienced enough with SElinux to know for sure yet12:38
chaologylink https://www.phoronix.com/scan.php?page=news_item&px=Snaps-Fedora-Arch-More12:38
chaologyhttps://github.com/snapcore/snapd12:39
chaologyhttps://github.com/snapcore/snapd/tree/master/sandbox/selinux12:39
chaologyto be honest I just would like to know whether snaps on say fedora 34 are equal citizens to snaps on ubuntu with respect to their security via confinement12:41
chaologythanks for any information that anyone can provide12:42
ijohnsonchaology: no, the selinux work on snapd was to provide policy for snapd itself to run and be packaged as a fedora package, snapd does not yet support using selinux as a backend for confinement and it's unlikely that work will be scheduled anytime soon12:57
ijohnsonchaology: what's more likely is that linux security module "lsm" stacking would enable folks on fedora to run apparmor stacked inside of selinux, such that snaps are confined the same on fedora as on ubuntu, just with fedora there would be another outer layer beyond apparmor12:58
chaologyijohnson: ah I see. thanks for the explanation13:38
chaologyI have heard about LSM stacking, which would be cool. so hopefully then13:38
ijohnsonpedronis: ah-ha I figured out the oom-killer thing with the spread test, it's because on those systems, an empty cgroup has 4k usage, so when in the test we try to create a cgroup with 500B limits, it triggers the oom killer on that slice15:46
ijohnsonpedronis: I think this means we should enforce a minimum of 4k as the memory limit for quota groups to avoid this probelm15:47
pedronisijohnson: I suppose so15:47
ijohnsonok, I will hold off on filing the PR with the work-around until I first file a PR setting this lower limit I think15:48
ijohnsonjust to make it as easy as possible to follow15:48
ijohnsoncachio: for #10298, we need to upload the snaps to the store17:00
cachioijohnson, in this case we need a snapcraft.yaml17:01
cachiobecause it is required to build it in lp17:01
ijohnsoncachio: ok, please ask for one in the PR then17:01
cachiois it not possible to install locally this?17:02
cachioijohnson, ?17:03
ijohnsoncachio: yes it needs to be pulled by snapd from the store17:03
cachiook17:03
cachioijohnson, I think I can upload manually the snap as it is just needed for amd6417:13
cachioright?17:13
cachioans i38617:13
cachioperhaps we can skip i38617:13
cachiootherwise I need to build that on launchpad17:13
ijohnsoncachio: sure if you want to manually upload the snap that's fine, but it should be transfered to test-snaps-canonical owner17:19
ijohnsoncachio: and you will need to get permission to upload classic, you can talk to the store folks for that I think17:19
=== ijohnson is now known as ijohnson|lunch
pedronisijohnson|lunch: should I merge https://github.com/snapcore/snapd/pull/9932 ?19:02
ijohnson|lunchpedronis: yes that can be merged now 19:07
ijohnson|lunchThanks 19:07
cachioijohnson|lunch, I pushed the snaps for #1029819:34
cachioand also included a small fix19:34
cachioI already gave +119:34
cachioneed a second +119:34
pedronisijohnson|lunch: I merged the other test change as well, you have 2 open PRs now20:16
=== ijohnson|lunch is now known as ijohnson
ijohnsonpedronis: \o/ amazing I can't remember the last time I had this few prs open20:17

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!