getsentry / getsentry/self-hosted
./install.sh failure: install/dc-detect-version.sh
- Dominant language
- Shell
- Stars
- 9.6k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 15
Description
### Self-Hosted Version
26.7.0
### CPU Architecture
x86_64
### Docker Version
28.1.1, build 4eba377
### Docker Compose Version
v2.35.1
### Machine Specification
- [x] My system meets the minimum system requirements of Sentry
### Installation Type
Upgrade from 26.5.0
### Steps to Reproduce
1. Run `sudo ./install.sh`
### Expected Result
Successful install
### Actual Result
```
container sentry-self-hosted-seaweedfs-1 is unhealthy
Error in install/dc-detect-version.sh:89.
'$dc up --wait "${options[@]}" "${services[@]}"' exited with status 1
-> ./install.sh:main:40
--> install/bootstrap-s3-nodestore.sh:source:3
---> install/dc-detect-version.sh:start_service_and_wait_ready:89
Looks like you've already sent this error to us, we're on it :)
install/dc-detect-version.sh: line 3: pop_var_context: head of shell_variables not a function context
```
### Event ID
_No response_
Contributor guide
Research direction
Start by running the reported upgrade with sudo ./install.sh and inspect install/dc-detect-version.sh around line 89, where the service wait fails. Check install/bootstrap-s3-nodestore.sh and the sentry-self-hosted-seaweedfs-1 health result to identify the failure. Done means the upgrade completes successfully without the unhealthy-service or shell error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100