Replies: 1 comment
-
One small update - I realized the 'host' only network is not supported on osx and thats why the host's network interface was not showing up in the container (was testing on osx) Still a little stuck with the provided docker images for IPFS and IPFS-Cluster though -
I think we would need to build our own docker images for IPFS + IPFS Cluster. Edit: there are docker linux/arm/v7 images for IPFS, however, there does not seem to be any for ipfs-cluster So I believe the path of least resistance is still using Ansible. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am starting to think perhaps we should scrap docker on rPi because it is overcomplicating the networking -
Let’s say I am connecting Box1 to Box0 that sits in a docker container.
Options are :
I am thinking about trying out ansible since ipfs cluster already provides some ansible roles for ipfs and ipfs-cluster.
We could probably still makes things work with a simplified setup which was the original goal.
I have a feeling things will run better with less virtualization anyway (but at this point its just a hunch). We could still provide a docker (or some other container/virtualization) solution in the future for ipfs cluster but for now I think our main target is rPi anyway. People can still use Box standalone with IPFS on top of docker for dev.
I also ran into issues connecting a browser to the 'Box' app in a docker container on an rPi, however, using a host driver solved this.
In both cases running the 'libp2p' application on the host OS simplifies the networking.
Perhaps another option is to setup relays (and is probably going to be needed at some point), however, setting up relays just to support docker seems wrong.
Beta Was this translation helpful? Give feedback.
All reactions