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 notworking #7805

Closed
CGsama opened this issue Dec 7, 2020 · 3 comments
Closed

IPFS_PATH notworking #7805

CGsama opened this issue Dec 7, 2020 · 3 comments
Labels
kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization

Comments

@CGsama
Copy link

CGsama commented Dec 7, 2020

Version information:

go-ipfs version: 0.7.0-ea77213e3
Repo version: 10
System version: amd64/linux
Golang version: go1.14.9

Description:

Tried both way, but ipfs only start repo on snap path, and /ipfsrepo/ubuntu still empty

$ IPFS_PATH=/ipfsrepo/ubuntu ipfs init
generating ED25519 keypair...done
peer identity: 12D3KooWEAn7ZszToMCz1Ux5G145Cp4Qm1YvwggfprzPEAP9N8TD
initializing IPFS node at /home/ubuntu/snap/ipfs/common
Error: ipfs configuration file already exists!
Reinitializing would overwrite your keys.

$ export IPFS_PATH=/ipfsrepo/ubuntu
$ ipfs init
generating ED25519 keypair...done
peer identity: 12D3KooWPHyr2Rjo8qduMwXPPUMNvFXyJhre73w8w6keQBcViBf3
initializing IPFS node at /home/ubuntu/snap/ipfs/common
Error: ipfs configuration file already exists!
Reinitializing would overwrite your keys.


@CGsama CGsama added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels Dec 7, 2020
@welcome
Copy link

welcome bot commented Dec 7, 2020

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.

@CGsama
Copy link
Author

CGsama commented Dec 7, 2020

its snap problem

@CGsama CGsama closed this as completed Dec 7, 2020
@NCGThompson
Copy link

initializing IPFS node at /home/ubuntu/snap/ipfs/common

Snap, by default only allows IPFS to access that directory. However, you can easily give it access to peripheral storage by following this guide.

I am not saying doing that will fix it, but it definitely won't work if you don't do that. In my case, Snap is overriding my preferences because "cgroup v2 is not fully supported yet" so I don't know if it will work for me.

If you haven't already, change your permission settings and report back please.

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

2 participants