snapstore VS snapd

- from https://github.com/noise/snapstore/

the snapstore demonstrated there is no longer in the github repo, or compatible with snapd anymore https://github.com/noise/snapstore

The current Snap Store is not open source. The one you referenced is dead as proven by the repo you're article refers to: https://github.com/noise/snapstore/

If you're referring to the old HOWTO article for hosting your own snap store server, the software it used to do that stopped working several years ago.

That's nice and all, but besides the complete lack of official serversoftware that can be hosted by anyone, I'm going to guess that forcing another URL would mean that it uses that repo INSTEAD OF the official one. With regular package managers and Flatpaks, that's not the case. You can add repo's in ADDITION to the originals with those. The only mention of a self-hostable snap server that I can find, is this one. However, it is an unofficial server and has been depreciated. In other words: it's not compatible/functional with the latest version of Snapd (the clientside) anymore and will remain like that.

They used to have an example implementation here, though: https://ubuntu.com/blog/howto-host-your-own-snap-store https://github.com/noise/snapstore

interesting read. unfortunately, the 'snapstore' github project (here) that it links to now says:

Your link is an blogpost from 2016 that points to: https://github.com/noise/snapstore README: snapstore was a minimalist example of a "store" for snaps, but is not compatible with the current snapd implementation. As a result I have removed the contents here to avoid further confusion.

In fact, Bret Barker has published an open source (Apache License) SNAP store on GitHub. We’re already looking at how to flesh out his proof-of-concept and bring it into snapcore itself.

https://github.com/noise/snapstore/

Oh don't get me started on that. I use Firefox on a work machine and I spent a number of hours troubleshooting why it couldn't access the Internet when I was connected on VPN.

I suspected it had something to do with snapd, so I downloaded the .tar.gz release of Firefox and it worked. I kept investigating and figured it must have something to do with snap.firefox.firefox apparmor profile because the VPN client was symlinking the /etc/resolv.conf to /opt/.../resolv.conf

However, updating the apparmor profile didn't help so I ultimately realized that snap has a hardcoded list of mounts that it mounts into the app container [1] and there's no way to change this.

There are a number of reasons to hate on snapd, but this almost made me flip the table.

[1]: https://github.com/snapcore/snapd/blob/3a88dc38ca122eba97192...

https://github.com/snapcore/snapd - snapd itself

you know this is false right , snap is opensource https://github.com/snapcore/snapd

So there's a PR opened to fix this here: https://github.com/snapcore/snapd/pull/12845

Of course, nothing's stopping anyone from contributing more complete selinux support. Looks like they take external pull requests in a pretty straightforward manner.

the system is actually open https://github.com/snapcore/snapd, its just the url they use is their own

That's not true. The git is here.

thanks for that. Following your link I arrived at https://github.com/snapcore/snapd/pull/12495 which covers the code. 22 commits, 19 files touched, this was a big job which indicates a little bit of a design miss, it will be very good to have this. It's the last remaining piece of "firefox snap sucks" I think.