-
Notifications
You must be signed in to change notification settings - Fork 285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connect to a remote IPFS server with multiaddr /dns4/name — required for docker-compose v3+ usage #462
Comments
@larskluge Just confirming you got the following error from running
|
Yes, that's it. Thank you @lanzafame |
License: MIT Signed-off-by: Hector Sanjuan <code@hector.link>
Hey @larskluge , can you test with docker image (also mind you pasted your secret publicly) |
Beautiful, that fixes it—thanks for addressing and fixing it (well, adding this feature :) so quickly, much appreciated! PS: And thanks for the hint, but don't worry, the posted 'secret' was modified to be more a 'public secret'.. ;-) |
Fix #462: Support DNS multiaddresses for node_multiaddress
@larskluge it's a bug that this feature was not there yet :) |
I know this isn't quite the same issue, but I'm unable to get my cluster to recognize the
Most notably, i'm not seeing the line mentioned above:
|
@dill0wn this is because there is already a
The |
Pre-check
secret
Basic information
which?
which?
Description
I'm trying to get
ipfs-cluster
connect to a remoteipfs
server instance viaIPFS_API
environment var & a docker compose setup v3+ and I'm running into this error:my
docker-compose.yml
:Note: I'd like to use the recent docker compose v3+ format, meaning its not allowed to specify ip4 addresses for services/containers anymore.
A proposed version with fixed IPs does not work for me due to the docker-compose v2 vs. v3 #376 and https://docs.docker.com/compose/compose-file/#ipv4_address-ipv6_address
Is there a way to run ipfs-cluster with docker-compose v3+ ? Thanks!
The text was updated successfully, but these errors were encountered: