come-maiz / ipfs-snap

IPFS packaged as a snap

ipfs-snap

IPFS is the Distributed Web, and this is its snap package.

Install

To install the latest stable release:

$ sudo snap install ipfs

To help testing the upcoming release:

$ sudo snap install ipfs --edge

Note that this is an edge release, so it's available there only for brave early adopters that would like to help testing it.

Build

In Ubuntu 16.04 or newer

Install snapcraft:

$ sudo apt install snapcraft

Clone the repo:

$ sudo apt install git
$ git clone https://github.com/elopio/ipfs-snap
$ cd ipfs-snap

Build the snap:

$ snapcraft

Install it:

$ sudo snap install ipfs*.snap --dangerous

In archlinux

Install docker:

$ sudo pacman -S docker
$ sudo systemctl start docker
$ sudo gpasswd -a $USER docker
$ newgrp docker

Clone the repo:

$ sudo packman -S git
$ git clone https://github.com/elopio/ipfs-snap
$ cd ipfs-snap

Build the snap in a docker container:

$ docker run -v $(pwd):/cwd snapcore/snapcraft sh -c 'apt install software-properties-common wget -y && add-apt-repository -y ppa:gophers/archive && apt update && cd /cwd && snapcraft

Install snapd:

$ sudo pacman -S snapd
$ sudo systemctl enable --now snapd.socket

Install the built snap:

$ sudo snap install ipfs*.snap --dangerous

Try

$ /snap/bin/ipfs init

ipfs-snap's Issues

IPFS snap not found

Hi there,
I'm sure this is probably something super basic and obvious, but this is my first time trying a snap, but I came across your blog post "Crowdtesting with the Ubuntu community: the case of IPFS" and thought I'd give it a try. When I run sudo snap install ipfs on my Kubuntu 16.10 machine though, I just get the error:

error: cannot install "ipfs": snap not found

...and I'm not sure why. Is there a snap equivalent of apt-get update I need to run first?

sudo snap install hello-world

...works just fine though.

Currently, I'm trying to drum up support in the Nextcloud community for adding IPFS to Nextcloud as an external storage source, so users can have their data backed up in a distributed, remote fashion (and add a ton of IPFS nodes around the world at the same time ;P )

Does it support snap services?

How can i easily make it running in the background process, because I would like to let it automatically start with ipfs daemon after reboot

updates... raspbian

iam running the snap on raspbian on a raspberry pi.... the error i got on every ipfs command is
ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libarmmem.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
realy dont care because it is working "fine" Aldo i am interested in helping test and i love a 0.4.20 branch.... my main server runs ipfs from the "offical" docker image and is on 0420... the pi i s running 0419 and is running fine for client testing... thanks for your work (Y)

ipfs config edit

ipfs config edit seems impossible to use because of snap's limitations.

EDITOR=/bin/nano

ipfs config edit
sh: 1: /bin/nano: not found
Error: exit status 127

A workaround would be to use $EDITOR $IPFS_PATH/config instead of ipfs config edit, but that's long to type and I don't want to have to remember that command. Any other idea?

Document IPFS storage location

There is no Datastore.Path in ipfs config show as described in the last step of this tutorial:

https://flyingzumwalt.gitbooks.io/decentralized-web-primer/install-ipfs/lessons/initialize-repository.html

I'd like to see all files that are served by my node.

i386/arm64 builds

It would be great if this snap would be available on other architectures.

Update to v0.4.21

Kindly update this snap to v0.4.21. Currently its installing v0.4.19

Deprecate in favour of https://github.com/ipfs-shipyard/ipfs-snap

Now that the snap is building from https://github.com/ipfs-shipyard/ipfs-snap it would be wise to deprecate this repo and add a note point folks there. I realise now that I should have forked this repo or requested a transfer, but at the time I really needed to start from scratch to get my head around it.

Thank you so much for your work on this! Hopefully https://github.com/ipfs-shipyard/ipfs-snap will be a short term stop gap, and we can land ipfs/kubo#7529

Update to v0.4.23

Version 0.4.23 was released 2 weeks ago.
It has critical bug fixes before v0.5.0 is released
https://github.com/ipfs/go-ipfs/releases/tag/v0.4.23

ipfs mount fails when installed via snap

Originally reported in ipfs/kubo#3788 by @mattseh

Version information:

root@snap:~# ipfs version --all
go-ipfs version: 0.4.6-
Repo version: 5
System version: amd64/linux
Golang version: go1.7.5

Type: Bug

Priority: P3

Description:

On a fresh Ubuntu 16.04 VM, I installed go-ipfs:

root@snap:~# snap install ipfs
ipfs v0.4.6 from 'elopio' installed

With the daemon running, and /ipfs and /ipns created, I get this error:

root@snap:~# ipfs mount
Error: fusermount: exec: "fusermount": executable file not found in $PATH

This issue seems to suggest that it is because the snap doesn't depend on FUSE?

Thanks

IPFS snap copying full block storage with every version (e.g. we're not using the "common" directory)

Possibly not an issue, but this is starting to eat up a lot of disk space for me, especially as I'm using the --edge distribution.

I'm new to snap in general. Is there a standard practice for using the common directory for large directories like this? Happy to help put together a patch.

Thank you for putting this package together!

Unable to add files that are outside of the snap confinement

It is not possible to, for example
ipfs add ~/somefile
as the file is not accessible from the snap. A permission denied error is seen.

It would make sense to allow access to files in the users home directory structure.