Skip to content

fix: bump Docker subnet base to avoid conflicts with common VPS networks#117

Open
oxatik wants to merge 1 commit into
circlefin:mainfrom
oxatik:fix/docker-subnet-conflict
Open

fix: bump Docker subnet base to avoid conflicts with common VPS networks#117
oxatik wants to merge 1 commit into
circlefin:mainfrom
oxatik:fix/docker-subnet-conflict

Conversation

@oxatik

@oxatik oxatik commented Jun 6, 2026

Copy link
Copy Markdown

Problem

Running make testnet fails with:
failed to create network arc_testnet_blockscout: invalid pool request:
Pool overlaps with other one on this address space

SUBNET_INDEX_BASE = 21 causes Arc to claim 172.21.0.0/16 and 172.20.0.0/16,
which are commonly occupied on VPS environments by:

  • docker_default (172.20.0.0/16)
  • monitoring leftovers (172.21.0.0/16)
  • Other node software (nesa, quip, etc.)

Fix

  • Bump SUBNET_INDEX_BASE from 21 to 23
  • Update hardcoded blockscout/monitoring template subnets from 172.20 to 172.22
  • Update unit tests to match

Tested

Verified make testnet runs successfully on Ubuntu 22.04 VPS with
existing Docker networks occupying 172.17–172.21.

SUBNET_INDEX_BASE was set to 21, causing arc_testnet_default to claim
172.21.0.0/16 which conflicts with networks commonly found on VPS
environments (docker_default at 172.20, monitoring leftovers at 172.21).

Changes:
- Bump SUBNET_INDEX_BASE from 21 to 23 in subnets.rs
- Update hardcoded blockscout subnet from 172.20 to 172.22 in templates
- Update unit tests to reflect new base index

Fixes: make testnet failing with 'invalid pool request: Pool overlaps
with other one on this address space'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant