go-ipfs is published at: https://snapcraft.io/ipfs
Users report multiple issues related to Snap confinement:
IPFS issues related to Snap appear somewhat consistently with new users, a containerized format does not mesh well with IPFS’s capabilities and use-cases, it also doesn’t help that the errors produced by Snap installs are very vague which makes troubleshooting difficult. This could be partially solved by recommending
snap install --classic ipfs
–
https://github.com/ipfs/go-ipfs/issues/8688
Some examples (new user, so cant post real links…):
https://github.com/ipfs/go-ipfs/issues/7872
https://github.com/ipfs/go-ipfs/issues/8553
https://github.com/ipfs/go-ipfs/issues/8580
https://github.com/ipfs/go-ipfs/issues/3788
In general, user should be able to read any file in the system to do ipfs add myfile.txt
(similar use case as in ipfs-cluster
which was already approved in here) and maintain the same config and repo across upgrades.
To fix go-ipfs for Snap users we want to switch https://github.com/ipfs/go-ipfs/blob/master/snap/snapcraft.yaml
to classic
, but my understanding is that we need to get from this manual process first.
Happy to provide any details needed.