-
Notifications
You must be signed in to change notification settings - Fork 293
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Allow ipfs-cluster-ctl to access files #579
Conversation
There were the following issues with your Pull Request
Code contribution guidelines for IPFS Cluster are available at https://cluster.ipfs.io/developer/contribute/#code-contribution-guidelines This message was auto-generated by https://gitcop.com |
Thanks @brianmcmichael! Any chance you can make @GitCop happy by modifying the commit message as indicated above? |
In the snap-installed distribution, calls like `ipfs-cluster-ctl add myfile.txt` fail with error `Error: open myfile.txt: permission denied` due to strict confinement to files in the /snap folder. Modifying confinement to `classic` will allow access to files elsewhere on the system. License: MIT Signed-off-by: brianmcmichael <brian@brianmcmichael.com>
293fb67
to
a1132b7
Compare
Try that, sorry about that! |
It seems snap store automatically rejects snaps with classic confinement. I made a request https://forum.snapcraft.io/t/classic-confinement-request-for-the-ipfs-cluster-snap/8056 |
@brianmcmichael mind jumping on that thread and arguing your case? |
I left a comment. I'll keep an eye on it. If it's accepted this will also require a change to the documentation where the installation invocation will be It's a common pattern though, used by apps that require arbitary file system access like Atom, VS Code, and Intellij |
In the snap-installed distribution, calls like
ipfs-cluster-ctl add myfile.txt
fail with errorError: open myfile.txt: permission denied
due to strict confinement to files in the /snap folder. Modifying confinement toclassic
will allow access to files elsewhere on the system.