-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ipfs mount fails when installed via snap #6
Comments
Thanks for the report! I haven't added support for mount on the snap yet, so it was an expected failure. In snaps you bundle all your dependencies, so installing fuse is simple, just add stage-packages: [fuse]. What might not be so simple is to give permission to the snap to mount. I need to give it a try, and if it's blocked by the strict confinement of the snap, talk to the security team to design a safe plug for this. I will have time for this during the weekend. Maybe it doesn't require any work at all, but I need to check. |
I had some time to try it, and as I expected, the syscall is blocked by the confinement. I've reported a bug in snapd for them to add an interface that will allow fusermount: https://bugs.launchpad.net/snapd/+bug/1673191 |
@ElOpio is there any progress on this front? |
@abitrolly nothing yet. The reported bug is still open. There's a workaround changing ipfs to run as root, but that would take a lot more work and testing than what I can do now. It would be nice if you or somebody else from the community give it a try :) |
It is suggested that |
What is the current status, the same? |
Originally reported in ipfs/kubo#3788 by @mattseh
Version information:
root@snap:~# ipfs version --all
go-ipfs version: 0.4.6-
Repo version: 5
System version: amd64/linux
Golang version: go1.7.5
Type: Bug
Priority: P3
Description:
On a fresh Ubuntu 16.04 VM, I installed go-ipfs:
With the daemon running, and /ipfs and /ipns created, I get this error:
This issue seems to suggest that it is because the snap doesn't depend on FUSE?
Thanks
The text was updated successfully, but these errors were encountered: