Can't run setup

I know how to install curl :slight_smile: . The thing is that it can’t download anything (the container).

This is the problem with helping people online :slight_smile:, you don’t give me enough information to begin with.

What exactly do you mean with it can’t download anything (the container).. What was the error it print out? Is the network interface down? Do apt command work? Does it give out 404 error? And have you try google the error yet?

I ask you to run curl command to give out more info why the download fail - because if you are good, you can deduce it by previous comment that - curl will give out a lot of information. Do you have curl yet? If not, why? If yes, what was the error when you try to run curl download?

I got this while installing curl:


root@33a9806eae14:/app# apt update && apt install curl
Hit:1 http://deb.debian.org/debian buster InRelease
Get:2 http://deb.debian.org/debian-security buster/updates InRelease [34.8 kB]
Err:2 http://deb.debian.org/debian-security buster/updates InRelease
  Connection failed [IP: 151.101.134.132 80]
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://deb.debian.org/debian-security/dists/buster/updates/InRelease  Connection failed [IP: 151.101.134.132 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  krb5-locales libcurl4 libgssapi-krb5-2 libk5crypto3 libkeyutils1 libkrb5-3
  libkrb5support0 libldap-2.4-2 libldap-common libnghttp2-14 librtmp1
  libsasl2-2 libsasl2-modules libsasl2-modules-db libssh2-1
Suggested packages:
  krb5-doc krb5-user libsasl2-modules-gssapi-mit
  | libsasl2-modules-gssapi-heimdal libsasl2-modules-ldap libsasl2-modules-otp
  libsasl2-modules-sql
The following NEW packages will be installed:
  curl krb5-locales libcurl4 libgssapi-krb5-2 libk5crypto3 libkeyutils1
  libkrb5-3 libkrb5support0 libldap-2.4-2 libldap-common libnghttp2-14
  librtmp1 libsasl2-2 libsasl2-modules libsasl2-modules-db libssh2-1
0 upgraded, 16 newly installed, 0 to remove and 0 not upgraded.
Need to get 2310 kB of archives.
After this operation, 5445 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://deb.debian.org/debian-security buster/updates/main amd64 krb5-locales all 1.17-3+deb10u6 [95.8 kB]
Get:1 http://deb.debian.org/debian-security buster/updates/main amd64 krb5-locales all 1.17-3+deb10u6 [95.8 kB]
Get:2 http://deb.debian.org/debian buster/main amd64 libkeyutils1 amd64 1.6-6 [15.0 kB]
Get:3 http://deb.debian.org/debian-security buster/updates/main amd64 libkrb5support0 amd64 1.17-3+deb10u6 [66.1 kB]
Get:4 http://deb.debian.org/debian-security buster/updates/main amd64 libk5crypto3 amd64 1.17-3+deb10u6 [122 kB]
Get:5 http://deb.debian.org/debian-security buster/updates/main amd64 libkrb5-3 amd64 1.17-3+deb10u6 [369 kB]
Get:6 http://deb.debian.org/debian-security buster/updates/main amd64 libgssapi-krb5-2 amd64 1.17-3+deb10u6 [159 kB]
Get:7 http://deb.debian.org/debian buster/main amd64 libsasl2-modules-db amd64 2.1.27+dfsg-1+deb10u2 [69.2 kB]
Get:8 http://deb.debian.org/debian buster/main amd64 libsasl2-2 amd64 2.1.27+dfsg-1+deb10u2 [106 kB]
Get:9 http://deb.debian.org/debian buster/main amd64 libldap-common all 2.4.47+dfsg-3+deb10u7 [90.1 kB]
Get:10 http://deb.debian.org/debian buster/main amd64 libldap-2.4-2 amd64 2.4.47+dfsg-3+deb10u7 [224 kB]
Err:11 http://deb.debian.org/debian-security buster/updates/main amd64 libnghttp2-14 amd64 1.36.0-2+deb10u2
  404  Not Found [IP: 199.232.170.132 80]
Get:12 http://deb.debian.org/debian buster/main amd64 librtmp1 amd64 2.4+20151223.gitfa8646d.1-2 [60.5 kB]
Get:13 http://deb.debian.org/debian-security buster/updates/main amd64 libssh2-1 amd64 1.8.0-2.1+deb10u1 [141 kB]
Err:14 http://deb.debian.org/debian-security buster/updates/main amd64 libcurl4 amd64 7.64.0-4+deb10u8
  404  Not Found [IP: 199.232.170.132 80]
Err:15 http://deb.debian.org/debian-security buster/updates/main amd64 curl amd64 7.64.0-4+deb10u8
  404  Not Found [IP: 199.232.170.132 80]
Get:16 http://deb.debian.org/debian buster/main amd64 libsasl2-modules amd64 2.1.27+dfsg-1+deb10u2 [104 kB]
Fetched 1623 kB in 1min 1s (26.7 kB/s)
E: Failed to fetch http://deb.debian.org/debian-security/pool/updates/main/n/nghttp2/libnghttp2-14_1.36.0-2+deb10u2_amd64.deb  404  Not Found [IP: 199.232.170.132 80]
E: Failed to fetch http://deb.debian.org/debian-security/pool/updates/main/c/curl/libcurl4_7.64.0-4+deb10u8_amd64.deb  404  Not Found [IP: 199.232.170.132 80]
E: Failed to fetch http://deb.debian.org/debian-security/pool/updates/main/c/curl/curl_7.64.0-4+deb10u8_amd64.deb  404  Not Found [IP: 199.232.170.132 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

It gets error 404

Thank you! This error belongs to StorJ, because buster is already EOL Debian -- News -- Debian 10 Long Term Support reaching end-of-life

I’ll create an issue on github and in a few day after they fix it, hopefully it’ll be working again.

P/s: Buster is already EOL - should upgrade to Bookworm soon Ā· Issue #21 Ā· storj/storagenode-docker Ā· GitHub

1 Like

Hi @Alexey, could you help me trigger job on my PR again? On my fork, it build successfully Dockerfile: replace legacy key value format Ā· kocoten1992/storagenode-docker@3ba2222 Ā· GitHub.

Thank you for the contribution!
I saw an internal conversation in the team, and I remined them to take it on a review earlier, but I think they would see my note only on Monday.

1 Like

Could you please try to run

wget -d https://github.com/storj/storj/releases/download/v1.105.4/storagenode_linux_arm64.zip

inside the container?

Hi @andrijajepro, I also think issue above is not the root cause of your issue (currently still unknown), you would need provide more information for someone to be able to guess it.

In the mean time, you could try this:

  • stop your storj container
  • export your storj container to a tar file
  • remove your current container (docker rm -f container_name)
  • import storj container tar file (now you will have a hash to use later on)
  • download curl statically linked from this repo Release 8.8.0 Ā· stunnel/static-curl Ā· GitHub
  • start a new container using -v with a named volume (could be storj_debug_volume) - (using hash from above)
  • copy curl file download to storj_debug_volume on your host)
  • log into your container, use curl file from storj_debug_volume to try download the file with maximum deug option on

Let see what going to happen :slight_smile:

1 Like

why not just update debian buster to bookworm ?

I think it would be updated eventually. Right now it doesn’t matter, it’s not a root cause of the issue. It’s ā€œnice to haveā€, because the old distro is not supported.
However, all go binaries are statically built, so they contains all needed libraries up-to-date and will work even with this ancient distro.

Here we likely have a communication issue (something is blocked). It could be a firewall/router/PiHole/ISP with a ā€œsmartā€ security protection. We just need to see, where is it blocked.

1 Like

Sorry for late reply.
It just stopped here:

 wget -d https://github.com/storj/storj/releases/download/v1.105.4/storagenode_linux_arm64.zip
DEBUG output created by Wget 1.20.1 on linux-gnu.

Reading HSTS entries from /root/.wget-hsts
URI encoding = 'ANSI_X3.4-1968'
converted 'https://github.com/storj/storj/releases/download/v1.105.4/storagenode_linux_arm64.zip' (ANSI_X3.4-1968) -> 'https://github.com/storj/storj/releases/download/v1.105.4/storagenode_linux_arm64.zip' (UTF-8)
Converted file name 'storagenode_linux_arm64.zip' (UTF-8) -> 'storagenode_linux_arm64.zip' (ANSI_X3.4-1968)
--2024-07-23 12:30:01--  https://github.com/storj/storj/releases/download/v1.105.4/storagenode_linux_arm64.zip
Certificates loaded: 137
Resolving github.com (github.com)... 140.82.121.4
Caching github.com => 140.82.121.4
Connecting to github.com (github.com)|140.82.121.4|:443... connected.
Created socket 3.
Releasing 0x000063b34f83c690 (new refcount 1).


I’ve heard of some people using a " --network host " setting on their docker. I’ve never tried it, but maybe you can give it a try and see if it makes any difference. Something like:
docker run --rm --network host -e SETUP=ā€œtrueā€ …rest of setup command…

1 Like

So, It cannot download from the GitHub.
Is it a snap version of docker?
If so, could you please uninstall it and install the native one instead: Install Docker Engine | Docker Docs

It is the native one. Should I try to run the non-docker node, I saw it on forum?

It’s up on you. I cannot reproduce the issue though.
Could you please try to run it with the --network host as suggested by @Mark ?

@andrijajepro can you try to execute wget -d https://github.com/storj/storj/releases/download/v1.105.4/storagenode_linux_arm64.zip from a container created from another image like the official debian:bookworm?

By the way, what OS are you running on your host machine?

Just tried it, I ran with this:

docker run --rm --network host -e SETUP="true"     --mount type=bind,source=/opt/s/identity/storagenode,destination=/app/identity     --mount type=bind,source=/opt/s/data,destination=/app/config     --name storagenode storjlabs/storagenode:latest

It worked.
Thank you all for helping me :slight_smile:

This is mean, that the default docker bridge is broken in your setup. Perhaps reinstalling docker could help.
With the --network host option the node’s ports are exposed directly to the host without a docker’s NAT. So the -p option will be redundant.
This is also mean, that for the next node you would need to change all ports from default, not only the node’s listening port and its external address, but also the dashboard, the private and the server addresses, too. See:

I’m not sure if this related, but indeed, wget is extremely slow (it stuck for hours), but it does download and not entirely stuck, I check using du on /tmp/storagenode.zip, I think github hate us @Alexey

Or there could be a broken route from your location to the GitHub. Or you may be have IPv6 enabled (I experienced issues with connections when it was enabled for some reason).