The ipfs/ipfs-cluster docker container runs both the ipfs and the ipfs-cluster peers on the same container.
The ipfs Peer ID is completely different from the ipfs-cluster peer ID. ipfs swarm peers will not list ipfs-cluster peers.
ipfs-cluster-ctl --debug peers add takes an ipfs-cluster peer multiaddress. By default this will be a /9096/ as that is the port in which the cluster peer listens.
Note that by default by launching two separate containers both ipfs-cluster peers will be initialized with different cluster_secret and will not be able to talk to each other. I recommend mounting the configuration (/data/ipfs-cluster folder, including service.json) from the outside, setting at least the same secret in both (or leaving it empty). Alternatively you could set the CLUSTER_SECRET environment variable with the same value for both containers, for example CLUSTER_SECRET=c5c7199d2b3bf59a6369c249982fcf309285bdecd79396af6838dbd489d9e019 (32 byte hex-encoded secret). That should make sure that they are initialized with the same secret.
First, thanks a lot for your answer. Yes, I noticed that the ipfs/ipfs-cluster docker container runs both. But I wanted to add more peers. So itās why I created the other containers.
And it was one of my question. I didnāt know if i should create multiple ipfs/ipfs-cluster or add more ipfs/go-ipfs containers if I wanted multiple peers. If I understand your reply, I should definitely create multiple ipfs/ipfs-cluster containers.
Hi, Iām going to lock this topic as it is old and instructions here might be misleading. For docs on cluster, head over to https://cluster.ipfs.io/documentation.