The installer (ipfs-update) breaks all the time, so as of this moment there is no IPFS peer running on dweb.archive.org to have this code connect to anyway. See https://github.com/ipfs/ipfs-update/issues/114 . This is likely to be ongoing, Protocol Labs have not prioritised having a reliable installer so it breaks FREQUENTLY, and the dweb.archive.org gateway is setup to just ignore failures to install it.
ipfs-update is currenly dependent on a specific version of Go, that isn't in the ubuntu:rolling docker image;
ipfs-update's API changed recently to require an environment variable being set (now fixed);
It goes through Protocol's http>IPFS gateway which goes through phases of being overloaded and therefore unreliable.
We've suggested multiple times that IPFS do one of the following (presented in order of preference).
a) add itself to apt-get or similar distributions,
b) add itself to go-get (just slows things down to get go)
c) provide a solid HTTP URL that pointed to the LATEST release via something that doesnt get overloaded, something like .... https://ipfs.io/installer/ipfs/arm/latest
d) make it available at a consistent urls on their (overloaded) gateway, eg. so http://ipfs.io/ipns/12345 always pointed to the current release
Any of a-c should be solid, even (d) would at least that would reduce the chain of dependencies.
However ... there seems to be little interest in a reliable installation process so beware ....
The installer (ipfs-update) breaks all the time, so as of this moment there is no IPFS peer running on dweb.archive.org to have this code connect to anyway. See https://github.com/ipfs/ipfs-update/issues/114 . This is likely to be ongoing, Protocol Labs have not prioritised having a reliable installer so it breaks FREQUENTLY, and the dweb.archive.org gateway is setup to just ignore failures to install it.
We've suggested multiple times that IPFS do one of the following (presented in order of preference). a) add itself to
apt-getor similar distributions, b) add itself to go-get (just slows things down to get go) c) provide a solid HTTP URL that pointed to the LATEST release via something that doesnt get overloaded, something like .... https://ipfs.io/installer/ipfs/arm/latest d) make it available at a consistent urls on their (overloaded) gateway, eg. so http://ipfs.io/ipns/12345 always pointed to the current releaseAny of a-c should be solid, even (d) would at least that would reduce the chain of dependencies.
However ... there seems to be little interest in a reliable installation process so beware ....