Skip to content
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

Closed
3 tasks done
aronchick opened this issue Feb 26, 2022 · 6 comments
Closed
3 tasks done

IPFS_PATH not working with ipfs init on latest from snap #8752

aronchick opened this issue Feb 26, 2022 · 6 comments
Labels
kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization

Comments

@aronchick
Copy link

Checklist

Installation method

third-party binary

Version

0.12

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.

@aronchick aronchick added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels Feb 26, 2022
@welcome
Copy link

welcome bot commented Feb 26, 2022

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

  • "Priority" labels will show how urgent this is for the team.
  • "Status" labels will show if this is ready to be worked on, blocked, or in progress.
  • "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

@Jorropo
Copy link
Contributor

Jorropo commented Feb 27, 2022

@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:

  • dist.ipfs.io
  • go install github.com/ipfs/go-ipfs/cmd/ipfs@latest

@aronchick
Copy link
Author

Thanks! Will try tomorrow - we should have a detection/warning/remove our (blessed) install from snap

@aschmahmann
Copy link
Contributor

#8688 (comment)

@aronchick
Copy link
Author

+1 confirmed. Removing the snap version and installing from dist.ipfs.io solved this. I'll +1 the other bug.

@guseggert
Copy link
Contributor

There is also documentation for this in the Snap section of the go-ipfs README: https://github.com/ipfs/go-ipfs#snap

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization
Projects
None yet
Development

No branches or pull requests

4 participants