-
-
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
IPFS_PATH not working with ipfs init on latest from snap #8752
Comments
Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
Finally, remember to use https://discuss.ipfs.io if you just need general support. |
@aronchick snaps run inside isolated dockers and doesn't allows that kind of things to happen (to my knowlege, anyway even if there is an option they are a pain). If you want to play with ipfs on that kind of level, you should install from:
|
Thanks! Will try tomorrow - we should have a detection/warning/remove our (blessed) install from snap |
+1 confirmed. Removing the snap version and installing from dist.ipfs.io solved this. I'll +1 the other bug. |
There is also documentation for this in the Snap section of the |
Checklist
Installation method
third-party binary
Version
Config
N/a
Description
When I execute the following command, I get a warning saying it’ll overwrite my existing keys. Am I missing something?
‘IPFS_PATH=/tmp/foobaz ipfs init’
I also tried exporting the env variable earlier as well.
The text was updated successfully, but these errors were encountered: