self-hosted install failing

[raja-kv]

Self-Hosted Version

25.11.0

CPU Architecture

aarch64

Docker Version

28.5.2

Docker Compose Version

Docker Compose version v2.40.3-desktop.1

Machine Specification

• [x] My system meets the minimum system requirements of Sentry

Steps to Reproduce

while running install.sh

Expected Result

sentry should install

Actual Result

Docker images built.

▶ Bootstrapping seaweedfs (node store)...
 Network sentry-self-hosted_default  Creating
 Network sentry-self-hosted_default  Created
 Container sentry-self-hosted-seaweedfs-1  Creating
 Container sentry-self-hosted-postgres-1  Creating
 Container sentry-self-hosted-seaweedfs-1  Created
 Container sentry-self-hosted-postgres-1  Created
 Container sentry-self-hosted-seaweedfs-1  Starting
 Container sentry-self-hosted-postgres-1  Starting
 Container sentry-self-hosted-seaweedfs-1  Started
 Container sentry-self-hosted-postgres-1  Started
 Container sentry-self-hosted-seaweedfs-1  Waiting
 Container sentry-self-hosted-postgres-1  Waiting
 Container sentry-self-hosted-postgres-1  Healthy
 Container sentry-self-hosted-seaweedfs-1  Healthy
**fetch https://dl-cdn.alpinelinux.org/alpine/v3.22/main/aarch64/APKINDEX.tar.gz
201DE99EFFFF0000:error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:2123:
fetch https://dl-cdn.alpinelinux.org/alpine/v3.22/community/aarch64/APKINDEX.tar.gz
WARNING: fetching https://dl-cdn.alpinelinux.org/alpine/v3.22/main: Permission denied
201DE99EFFFF0000:error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:2123:
WARNING: fetching https://dl-cdn.alpinelinux.org/alpine/v3.22/community: Permission denied
ERROR: unable to select packages:
  s3cmd (no such package):
    required by: world[s3cmd]
Error in install/bootstrap-s3-nodestore.sh:4.**
'$dc exec -e "HTTP_PROXY=${HTTP_PROXY:-}" -e "HTTPS_PROXY=${HTTPS_PROXY:-}" -e "NO_PROXY=${NO_PROXY:-}" -e "http_proxy=${http_proxy:-}" -e "https_proxy=${https_proxy:-}" -e "no_proxy=${no_proxy:-}" seaweedfs apk add --no-cache s3cmd' exited with status 1
-> ./install.sh:main:39
--> install/bootstrap-s3-nodestore.sh:source:4

Looks like you've already sent this error to us, we're on it :)
Cleaning up...

Event ID

No response

[aldy505]

Are you behind a network proxy? This does not happen with me and with some other folks on Discord.

[snjv94]

I am alos getting similar issue.

./install.sh is failing with the following ending lines

container sentry-self-hosted-seaweedfs-1 is unhealthy
Error in environment:2.
'command "$cmd" "$@"' exited with status 1
-> ./install.sh:main:39
--> install/bootstrap-s3-nodestore.sh:source:3
---> environment:docker:0
----> environment:log_simple_command:3
-----> environment:safe_execute:2

Cleaning up...

The docker logs sentry-self-hosted-seaweedfs-1 shows following

I1120 16:04:24.975076 volume_loading.go:139 checking volume data integrity for volume 9335
I1120 16:04:24.975223 volume_loading.go:202 loading leveldb large index /data/idx/9335.ldb
I1120 16:04:24.980559 master_grpc_server.go:387 - client [email protected]:9333
I1120 16:04:24.980605 master_grpc_server.go:321 => client [email protected]:8888: cluster_node_update:{node_type:"master"  address:"127.0.0.1:9333"}
I1120 16:04:24.980701 master_grpc_server.go:387 - client [email protected]:8888
I1120 16:04:24.980894 masterclient.go:245 .master masterClient failed to receive from 127.0.0.1:9333: rpc error: code = Unavailable desc = error reading from server: EOF
I1120 16:04:24.980917 masterclient.go:245 .filer masterClient failed to receive from 127.0.0.1:9333: rpc error: code = Unavailable desc = error reading from server: EOF

I have also tried to change the -ip to seaweedfs (servicename) from 127.0.0.1 but not sure what is wrong with it.

[smittyw1]

Getting a similiar error, behind a network proxy. Proxy is set in /etc/environment as well as in /etc/docker/config.json

fetch https://dl-cdn.alpinelinux.org/alpine/v3.22/main/x86_64/APKINDEX.tar.gz
WARNING: fetching https://dl-cdn.alpinelinux.org/alpine/v3.22/main: Permission denied
fetch https://dl-cdn.alpinelinux.org/alpine/v3.22/community/x86_64/APKINDEX.tar.gz
WARNING: fetching https://dl-cdn.alpinelinux.org/alpine/v3.22/community: Permission denied
ERROR: unable to select packages:
  s3cmd (no such package):
    required by: world[s3cmd]
Error in install/bootstrap-s3-nodestore.sh:4.
'$dc exec -e "HTTP_PROXY=${HTTP_PROXY:-}" -e "HTTPS_PROXY=${HTTPS_PROXY:-}" -e "NO_PROXY=${NO_PROXY:-}" -e "http_proxy=${http_proxy:-}" -e "https_proxy=${https_proxy:-}" -e "no_proxy=${no_proxy:-}" seaweedfs apk add --no-cache s3cmd' exited with status 1
-> ./install.sh:main:39
--> install/bootstrap-s3-nodestore.sh:source:4

Edit:

Setting http_proxy, https_proxy BUT ALSO: HTTP_PROXY and HTTPS_PROXY in /etc/environment fixed it for me. Seaweedfs seems to expect the capitalized version and ignores the lowercase variables.

[aldy505]

Setting http_proxy, https_proxy BUT ALSO: HTTP_PROXY and HTTPS_PROXY in /etc/environment fixed it for me. Seaweedfs seems to expect the capitalized version and ignores the lowercase variables.

@snjv94 Can you try this workaround?

[major-s]

I had the same issue but deleting all enviromental variables from the exec command solved the issue. My sentry deployment runs behind a corporate proxy and if the docker is configured properly, those env variables are not needed.

[snjv94]

Setting http_proxy, https_proxy BUT ALSO: HTTP_PROXY and HTTPS_PROXY in /etc/environment fixed it for me. Seaweedfs seems to expect the capitalized version and ignores the lowercase variables.

@snjv94 Can you try this workaround?

I am not using any kind of proxy as such.

Although, the issue was coming up when I was trying to run 'install.sh' after doing some changes. I am using persistent docker volume with path to data directory putting on same level where install.sh is residing just for the sake of simplicity in case I have to move the sentry to another server.

As a temporary solution, when I removed the data/sentry-seaweedfs folder, it started to work again. This issue resurface everytime I will try to run install.sh.

I am not sure how much critical data does the seaweedfs folder holds but after deleting it re-created the folder and the sentry seemd working fine.

No permanent solution yet.