Ho-Sheng Hsiao
Ho-Sheng Hsiao
To simplify this demo, here is what I am thinking: 1. First, get the IPFS-in-a-container working. This requires starting it with Docker 1.5.0 and starting it with additional privs: https://github.com/docker/docker/issues/9448#issuecomment-65529399...
See: https://github.com/jbenet/ipfs-container-demos/issues/4
So `--privileged` worked. That example of using `sshfs` works. However, `ipfs` doesn't. When I attempt to run it, what appears to be blocking it is apparmor. Inside the container, this...
Using `--volumes-from` in a different container to link to a FUSE-mount inside a contaner may not be possible as it is now: https://groups.google.com/forum/#!msg/docker-dev/_8bAG561VAI/ofDLtK8dxigJ cryptix@freenode suggested checking if it is the...
Tried it with `sshfs` still does not work. Limitation of Docker and all. I think for this demo, I'll use `docker exec` to demonstrate being able to grab data from...
The object that were pinned are gone. I have updated the objects to something smaller for #3. I'll check on #4
Ok, IPNS is working for go-ipfs:master There is also a way to use FUSE mounts without starting the container in priveledged mode: https://github.com/docker/docker/issues/9448#issuecomment-65529399 `docker run -ti --name dev --device /dev/fuse...
https://gist.github.com/jbenet/76afa70955910a2ed097
- Something about modifying Docker so it uses `ipfs` instead of the layers. - Permissions. Allowing for `+x` would let `nsinit` to start a container directly
Get performance better so we can demo things without having pre-pinned assets.