Skip to content
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

[community] Kubo not installed #248

Open
developersteve opened this issue Jul 10, 2024 · 6 comments
Open

[community] Kubo not installed #248

developersteve opened this issue Jul 10, 2024 · 6 comments
Assignees

Comments

@developersteve
Copy link
Member

developersteve commented Jul 10, 2024

Using a Ubuntu 22 instance, attempting to run ipfs init results in a kubo not installed error which needs to be installed manually and not via a snap (snap install is not longer supported).

This originates from the bacalhau error bacalhau[8980]: please run: 'ipfs init', which then indicates the need to have kubo installed via a snap, which will install then return a response about not being supported.

Additional information https://docs.ipfs.tech/install/command-line/#install-official-binary-distributions

See the discord thread

@developersteve
Copy link
Member Author

developersteve commented Jul 10, 2024

Manually installing kubo fixes this issue which seems to maybe be only ubuntu specific, its important to note that you cannot use the snap install method that ipfs will recommend.

@PBillingsby ill get you a VM to test on so you can step through it for doc updates and also to have another set of eyes on it

@rhochmayr
Copy link
Contributor

rhochmayr commented Jul 10, 2024

This is how I installed it on Ubuntu 22.04 and 24.04.
https://docs.ipfs.tech/install/command-line/#install-kubo-linux

cd ~
wget https://dist.ipfs.tech/kubo/v0.29.0/kubo_v0.29.0_linux-amd64.tar.gz
tar -xvzf kubo_v0.29.0_linux-amd64.tar.gz
cd Kubo/
sudo ./install.sh

Now check if ipfs works

ipfs --version

Afterwards I think the default IPFS path should be set to /app/data/ipfs before running ipfs init.

export IPFS_PATH=/app/data/ipfs
cd /app/data/ipfs/
ipfs init

@bgins
Copy link
Contributor

bgins commented Jul 10, 2024

We did some investigation and this issue is likely due to Bacalhau removing support for embedded IPFS: bacalhau-project/bacalhau#3816. For the moment, the fix is to pin to Bacalhau v1.3.2 which is the last version with embedded IPFS support.

We plan to implement another strategy for storing and delivering results (#157), and we will announce when pinning to Bacalhau v1.3.2 is no longer needed.

Closing this issue for now, but please re-open if this wasn't the root cause.

@bgins bgins closed this as completed Jul 10, 2024
@rhochmayr
Copy link
Contributor

This is happening with v1.3.2 though. Didn't the deprecation of embedded IPFS happen in v.1.4.0, which currently isn't compatible with LP anyways?

@bgins bgins reopened this Jul 10, 2024
@bgins
Copy link
Contributor

bgins commented Jul 10, 2024

Didn't the deprecation of embedded IPFS happen in v.1.4.0, which currently isn't compatible with LP anyways?

That's correct. Embedded IPFS has been removed as of v1.4.0. Version v1.3.2 still has it.

This is happening with v1.3.2 though.

Any chance you have IPFS running somewhere else on your system? Bacalhau might prioritize non-embedded IPFS if it is installed.

@developersteve you got this working after moving to Bacalhau v1.3.2 right?

@rhochmayr
Copy link
Contributor

Any chance you have IPFS running somewhere else on your system? Bacalhau might prioritize non-embedded IPFS if it is installed.

This was on a clean Ubuntu installation. I'm pretty sure there was no other IPFS instance running or installed. Funnily enough, the same error popped up in the latest AMA video. Around the 34:30 mark. Have a look here.
https://youtu.be/Q2E65wvbyyU?t=2070

image

The error message instructs the user to run: 'ipfs init'. When you do (on a fresh Ubuntu installation), IPFS is not available and needs to be installed. Unless the embedded version needs to be called in a different way maybe?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants