StakeSquid/ethereum-rpc-docker
1
0
Fork 0
Code Issues Pull Requests 3 Packages Projects Releases Wiki Activity

ink-mainnet: remove orphaned op-geth compose files #45

Closed
claude wants to merge 1 commits from issue-2048 into main
pull from: issue-2048
merge into: StakeSquid:main
Conversation 1 Commits 1 Files Changed 4 -808
claude commented 2026-07-28 11:50:39 +00:00
Collaborator
Copy Link

Summary

Remove four orphaned op-geth compose files for ink-mainnet that caused a Traefik router collision.

Root cause: Source config dropped ink-mainnet op-geth in PR #1808, but the generated compose files remained orphaned on rpc main. Both op-geth and op-reth defined the same Traefik service name ink-mainnet, causing: ERR Router cannot be linked automatically with multiple Services. This broke routing (404 on /ink-mainnet) despite the node being healthy and syncing fine.

Fix: Delete the four orphaned op/geth/ink-mainnet-op-geth-*.yml files. After merge and deploy, only op-reth (and op-erigon backup) remain, and Traefik's single router binds correctly.

Verification: ./update.sh confirmed clean—orphans stay deleted (not regenerated); COMPOSE_FILE contains only op-reth + op-erigon for ink-mainnet.

Branches:

  • rpc asset: issue-2048 @ 75d3b6d610e4
  • vibe-node source: no change (already dropped geth in main)

Fixes issue #2048 (ink-ink @rpc-de-14 unavailable due to Traefik collision).

## Summary Remove four orphaned op-geth compose files for ink-mainnet that caused a Traefik router collision. **Root cause:** Source config dropped ink-mainnet op-geth in PR #1808, but the generated compose files remained orphaned on rpc main. Both op-geth and op-reth defined the same Traefik service name `ink-mainnet`, causing: `ERR Router cannot be linked automatically with multiple Services`. This broke routing (404 on `/ink-mainnet`) despite the node being healthy and syncing fine. **Fix:** Delete the four orphaned `op/geth/ink-mainnet-op-geth-*.yml` files. After merge and deploy, only op-reth (and op-erigon backup) remain, and Traefik's single router binds correctly. **Verification:** `./update.sh` confirmed clean—orphans stay deleted (not regenerated); COMPOSE_FILE contains only op-reth + op-erigon for ink-mainnet. **Branches:** - rpc asset: `issue-2048` @ `75d3b6d610e4` - vibe-node source: no change (already dropped geth in main) Fixes issue #2048 (ink-ink @rpc-de-14 unavailable due to Traefik collision).
claude added 1 commit 2026-07-28 11:50:40 +00:00
ink-mainnet: remove orphaned op-geth compose files 75d3b6d610 
Source already dropped ink-mainnet op-geth from config.yml, but
update.sh never prunes orphans — stale op/geth/ink-mainnet-op-geth-*.yml
files stayed in COMPOSE_FILE and fought op-reth for Traefik /ink-mainnet
(404). Delete the four orphans so only op-reth remains for that path.
sebastian commented 2026-07-29 02:43:40 +00:00
Owner
Copy Link

@claude is this still necessary?

@claude is this still necessary?
sebastian closed this pull request 2026-07-31 03:25:55 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude cursor rob sebastian
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: StakeSquid/ethereum-rpc-docker#45
Delete Branch "issue-2048"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?