Invalid port versioncontrol service
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
Research direction
Start with the storj-up init entry point and trace how recipes that add versioncontrol generate docker-compose.yaml. Reproduce the issue with a versioncontrol recipe and verify that the generated STORJ_ADDRESS uses a valid port instead of -1.
Written by the indexing model from the issue text.
Description
Reason / Why?
storj-up v1.2.7 assigns an invalid port to the versioncontrol service.
When storj-up init versioncontrol or any other recipe that adds the versioncontrol service to the docker-compose.yaml file is executed it produces the following
version: "3.4"
services:
versioncontrol:
command:
- versioncontrol
- run
deploy:
replicas: 1
environment:
BINARY_GATEWAY_ROLLOUT_SEED: "0000000000000000000000000000000000000000000000000000000000000001"
BINARY_IDENTITY_ROLLOUT_SEED: "0000000000000000000000000000000000000000000000000000000000000001"
BINARY_SATELLITE_ROLLOUT_SEED: "0000000000000000000000000000000000000000000000000000000000000001"
BINARY_STORAGENODE_ROLLOUT_SEED: "0000000000000000000000000000000000000000000000000000000000000001"
BINARY_STORAGENODE_UPDATER_ROLLOUT_SEED: "0000000000000000000000000000000000000000000000000000000000000001"
BINARY_UPLINK_ROLLOUT_SEED: "0000000000000000000000000000000000000000000000000000000000000001"
STORJ_ADDRESS: 0.0.0.0:-1
STORJ_DEBUG_ADDR: 0.0.0.0:11111
STORJ_DEFAULTS: dev
STORJ_LOG_LEVEL: debug
STORJ_METRICS_APP_SUFFIX: sim
image: img.dev.storj.io/storjup/storj:1.104.5
networks: {}
The environment variable STORJ_ADDRESS: 0.0.0.0:-1 has the -1 port, an invalid port.
What needs to be done?
Fix the versioncontrol service docker-compose generation to assign a valid port.
Acceptance criteria
- Fix
storj-up initwith any recipe that adds the versioncontrol service into thedocker-compose.yamlfile to assign a valid port to theSTORJ_ADDRESSenvironment variable.
- Dominant language
- Go
- Stars
- 28
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from storj/up
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
Similar issues
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yanet-platform/ipfw-go#129 ·
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100