Repository navigation
fix(validator): restore the runner's Prometheus (bittensor_prometheus 1.0.3) - #858
Merged
kacper-wolkiewicz-reef merged 2 commits intoOct 26, 2026
Merged
Conversation
bittensor_prometheus:1.0.2 ships /entrypoint.sh without the executable bit, so the Prometheus container restart-loops with "exec: /entrypoint.sh: Permission denied" and validators stop reporting metrics. Running the script through sh works with the pinned image and keeps working with future builds.
bittensor_prometheus 1.0.3 ships an executable /entrypoint.sh, fixing the "Permission denied" restart loop of 1.0.2. Bump bittensor-prometheus-proxy to the same release.
Commit message lint report
Status: ❌ Issues found. gitlint output: Fix by amending/rewording your commits (e.g., using |
kacper-wolkiewicz-reef
deleted the
fix-validator-prometheus-entrypoint
branch
October 26, 2026 16:19
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Since the validator runner pinned
backenddevelopersltd/bittensor_prometheus:1.0.2(4785735, deployed to prod today), the runner'sprometheuscontainer restart-loops:The 1.0.2 image ships
/entrypoint.shas-rw-rw-r--, so validators that update send no metrics at all. The script was never executable in git, and the Dockerfile only ranchownon it. Fixed in bittensor-church/bittensor-prometheus-proxy#11 and released as 1.0.3.Changes
bittensor_prometheus:1.0.2→1.0.3@sha256:35112f61….lateston Docker Hub now points at the same build, which also heals validators still on the old runner compose.bittensor-prometheus-proxy:1.0.2→1.0.3@sha256:39caeb31…. This is the same release, built by CI from tagv1.0.3; the proxy code is unchanged.exec /entrypoint.sh …→exec sh /entrypoint.sh …, so the runner no longer depends on the script's file mode.Testing
bittensor_prometheuswith a throwaway wallet and a minimal config template, using the runner'sexec /entrypoint.sh …call:1.0.2:Permission denied,1.0.3:/entrypoint.shis-rwxr-xr-x, Prometheus logs "Server is ready to receive web requests.", and the hotkey is substituted intoprometheus.yml.exec sh /entrypoint.shalso starts Prometheus with the old1.0.2image.1.0.3digests pull from their registries. The proxy image importspylon_clientandbittensor.docker compose config.🤖 Generated with Claude Code