search

everywhere-computer / docs

Everywhere Computer documentation for running nodes, writing workflows, and working with IPVM
https://docs.everywhere.computer
2 stars 0 forks source link

tip: Make sure you only have one instance of IPFS running #9

Open depatchedmode opened 9 months ago

depatchedmode commented 9 months ago

Also from Brook's clean install:

$ homestar start -c ./settings.toml
ts=2024-01-30T22:00:28.151813Z level=info target=homestar
# ...snip...
thread 'main' panicked at homestar-runtime/src/main.rs:56:41:
Failed to start runtime: Address already in use (os error 48)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

What can we highlight, generally, from this error to help people realize they might have two instances of IPFS running? In Brook's case she had the kubo daemon running as well as IPFS desktop.

zeeshanlakhani commented 9 months ago

@depatchedmode In this case, you can check for something running at the default port of the settings or have the system check for an IPFS running already. We do this in the cat lines example for homestar. Homestar does run with configurable IPFS host/port API, so that's something to make sure is the same for both.

bmann commented 9 months ago

For the Fission CLI tools, we fully puppet-ted IPFS on a separate / non default port. I'm NOT proposing we do that...until / if we decide to fully bundle in the future.

We may want to not have Homestar do anything about IPFS and the only thing we do is config on which port it is running? And the error is "no IPFS node found at port XXXX defined in "

I think I just said the same thing as @zeeshanlakhani with different words :)

bmann commented 9 months ago

@matheus23 points out we'll have rs-car-mirror soon, which means no local IPFS required --> does sync of bits over https

@expede had incepted 18 Nix shells and who knows what else, so also likely not a common pattern :)