Closed gdkrmr closed 2 months ago
How are you running kubo? Are you running ipfs daemon
as root (shouldn't be needed), the folder permissions changing looks suspicious.
This feature could be reimplemented using "ipfs filestore", I don't know if something similar is already thought of, or if you plan to keep the --mount, but both methods would seem useful to me.
How are you running kubo? Are you running
ipfs daemon
as root (shouldn't be needed), the folder permissions changing looks suspicious.
I don't run kubo
as root.
Basic checklist for FUSE-mounting IPFS:
I know you said that you already did some of these things, but you didn't comment on the other things. Oh wait, I see that you posted '"FuseAllowOther": false,' - and that's almost certainly your problem.
Author input needed to mark this issue as solved?
Thanks for looking at this. I followed the steps and get a different error now:
$ ipfs config --json Mounts.FuseAllowOther
true
$ ll / | grep ip
drwxr-xr-x 2 gkraemer gkraemer 4.0K Feb 12 2024 ipfs
drwxr-xr-x 2 gkraemer gkraemer 4.0K Feb 12 2024 ipns
$ cat /etc/fuse.conf | grep user_allow_other
# user_allow_other - Using the allow_other mount option works fine as root, but
# in order to have it work as a regular user, you need to set user_allow_other
user_allow_other
$ echo test > test
$ ipfs add test
added QmeomffUNfmQy76CQGy9NdmqEnnHU9soCexBnGU3ezPHVH test
5 B / 5 B [===============================================================================================================================================================================================] 100.00%
$ ipfs name publish QmeomffUNfmQy76CQGy9NdmqEnnHU9soCexBnGU3ezPHVH
Published to k51qzi5uqu5dis3bmsaehjsm3v6k1mc94yi0kk79uxxmqphsw5k6plo91jftd2: /ipfs/QmeomffUNfmQy76CQGy9NdmqEnnHU9soCexBnGU3ezPHVH
$ ipfs daemon --mount
Initializing daemon...
Kubo version: 0.29.0
Repo version: 15
System version: amd64/linux
Golang version: go1.22.4
[...]
RPC API server listening on /ip4/127.0.0.1/tcp/5002
WebUI: http://127.0.0.1:5002/webui
2024-09-05T10:46:46.946+0200 ERROR node node/mount_unix.go:96 error mounting: root can't be a file (unixfs type: File)
Error: root can't be a file (unixfs type: File)
error mounting: root can't be a file (unixfs type: File) Error: root can't be a file (unixfs type: File)
It didn't work because you tried to publish a file to IPNS. You can only publish a folder to IPNS (I didn't write that in my steps). Run something like this (folder contains darkhttpd web server source code): "ipfs name publish /ipfs/bafybeiawvadz46hpwl2hw2darjone46gvajm7td4dgowjpdvz5f5eee7qi".
Above in this thread, I said that mounting IPFS doesn't work in 32-bit computers. That's not entirely correct. It didn't work in a specific ~decade-ago version of a certain Linux distro. This month I saw that I could mount IPFS in a 32-bit computer which is basically running a liveboot of the latest Debian. (Now my problem is that I cannot run Tor and torsocks in said 32-bit computer, even after hours of trying to fix it.)
Thanks for taking the time to debug this for me! It works now for me.
Checklist
Installation method
third-party binary
Version
Config
Description
does not work. I have seen similar issues reported here but I couldn't find this exact same issue.
kubo
is installed through the Manjaro repositories. I have also tested this with the v0.26.0 binary downloaded from Github and a colleague confirmed the issue.I have created
/ipfs
and/ipns
and the folders belong to meafter launching
ipfs daemon --mount
, something gets mounted in these folderstrying to access anything from these folders tells me "No such file or directory".
I have tried setting
user_allow_other
and changing the permissions of the directories while unmounted and mounted but to no avail.