-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
OSXFUSE failure #3250
Comments
We should update our bazil/fuse dep then. |
Yes, with the latest official FUSE for macOS, the helpers have moved from |
What is the last known working FUSE for macOS version, then? Symlinking the above paths does not seem to make |
It is in our dependency, update for it is queued but we won't be able to test it for next release. For now 3.0.0 is no supported. |
We have updated our fuse dep, This should be resolved. Please reopen the issue if problems still exist |
Thanks. Can you clarify when that update happened, i.e. which release it will be / has been part of? |
@hmeine it should have been in at least 0.4.8, before closing the issue i installed osxfuse 3.6.3 on macOS high sierra and successfully mounted /ipfs and /ipns with ipfs 0.4.10 (downloaded from dist.ipfs.io) |
Seems I am out of luck with >>>ipfs mount |
> ipfs mount macOS 10.15.5 (19F101) |
Unfortunately, osxfuse has now gone closed source and the fuse library we're using has dropped support for it. We're probably not going to be able to solve your issue. |
I fixed it myself. It couldn't mount into the root folder on macOS. Mounting into the home folder was possible. Thanks, anyways! |
Version information:
go-ipfs version: 0.4.3-
Repo version: 4
System version: amd64/darwin
Golang version: go1.7
Type: Bug
Priority: P3?
Description:
I installed osxfuse from their website, as suggested, version 3.5.
When running ipfs mount, I get: "Error: fork/exec /Library/Filesystems/osxfusefs.fs/Support/load_osxfusefs: no such file or directory"
Based on this: bazil/fuse#103 it looks like version 3 changed some paths, whereas IPFS is still using old V2 paths.
The text was updated successfully, but these errors were encountered: