Loading
ci: pull bor from ghcr.io (0xpolygon/bor:2.5.9 is gone)
🔎 Visual review off6c701ac: explainer, review flags and prompts to ask an AI about the change
Why
test-simulation is red repo-wide, on develop too (pipeline 2981849157, pipeline 2980284221), plus the MR pipeline 2981837994. run-mocknet-cluster-l1 can't pull the polygon mocknet image:
pull access denied for 0xpolygon/bor, repository does not exist or may require 'docker login'The 0xpolygon/bor repository is gone from Docker Hub. docker manifest inspect docker.io/0xpolygon/bor:2.5.9 (and :latest) is denied, and the 0xpolygon org listing on Docker Hub no longer includes bor. Polygon now publishes bor at ghcr.io/0xpolygon/bor. The oldest tag there is v2.6.3, and there is no 2.5.9 on ghcr.
What
build/docker/docker-compose.yml is the only reference in the repo. It changes from
${DOCKER_MIRROR:-}0xpolygon/bor:2.5.9to
ghcr.io/0xpolygon/bor:v2.6.3@sha256:8d6bbd1cbdaa0e70746b95e375fed5fb4d6eae58edfdf3d49138c7a334449a95- Version:
v2.6.3is the closest version to 2.5.9 that is still published. It is pinned by digest (a multi-arch index for amd64 and arm64). - No
DOCKER_MIRRORprefix: in CI,DOCKER_MIRRORis the GitLab group dependency proxy, which only proxies Docker Hub, so prefixing a ghcr reference would break the pull. This follows the other non-Docker-Hub images in the file (op-geth, node-launcher).
Verification
docker pull ghcr.io/0xpolygon/bor:v2.6.3works, andbor versionreports 2.6.3 (commit d72f1cf0).- I brought up the
polygoncompose service (same entrypoint,--dev --dev.period 2 --bor.withoutheimdall) and compared it with a locally cached 2.5.9 image:- the account import and
Using developer account 0x8db97C7c…lines are identical; - both give chain ID
0x539, andeth_accountsis[]on both; - the etherbase is funded, and v2.6.3 seals a block every 2s.
- the account import and
make lint-ciandmake generatepass, with a clean tree afterwards.- The full end-to-end check is this MR's
test-simulationjob.
Edited by Huginn Ai