Dashmate fails to upgrade from v2.0.1

[pshenmic]

Expected Behavior

I have a node with a dashmate running v2.1.3, I expect to succesfully install a v3.0.0-rc.2 and a successful dashmate restart

Current Behavior

After an installation of dashmate 3.0.0-rc.2, the update via dashmate update --config testnet processed succesfully:

$ dashmate update --config=testnet
╔═════════════════════╤════════════════════════════════════╤════════════╗
║ Service             │ Image                              │ Updated    ║
╟─────────────────────┼────────────────────────────────────┼────────────╢
║ Dashmate Helper     │ dashpay/dashmate-helper:3.0.0-rc.2 │ updated    ║
║ Core                │ dashpay/dashd:22.1.0               │ up to date ║
║ Drive ABCI          │ dashpay/drive:3-rc                 │ updated    ║
║ Drive Tenderdash    │ dashpay/tenderdash:1.5             │ up to date ║
║ rs-dapi (Rust DAPI) │ dashpay/rs-dapi:3-rc               │ updated    ║
║ Gateway             │ dashpay/envoy:1.30.2-impr.1        │ up to date ║
╚═════════════════════╧════════════════════════════════════╧════════════╝

However the subsequent dashmate restart failed with error. After raising the --verbose it seems there is a port binding issue:

dashuser@seed-1:~$ dashmate start --config testnet --verbose
[STARTED] Start testnet node
[STARTED] Check node is not started
[SUCCESS] Check node is not started [0.2s]
[STARTED] Remove legacy DAPI stack
[SUCCESS] Remove legacy DAPI stack [0.2s]
[STARTED] Start services
[FAILED] Docker Compose error: time="2026-01-17T19:52:40Z" level=warning msg="Found orphan containers ([dashmate_4b6ad327_testnet-gateway_rate_limiter-1 dashmate_4b6ad327_testnet-gateway_rate_limiter_redis-1]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up."
[FAILED]  Container dashmate_4b6ad327_testnet-drive_abci-1  Created
[FAILED]  Container dashmate_4b6ad327_testnet-dashmate_helper-1  Created
[FAILED]  Container dashmate_4b6ad327_testnet-drive_abci-1  Starting
[FAILED]  Container dashmate_4b6ad327_testnet-dashmate_helper-1  Starting
[FAILED]  Container dashmate_4b6ad327_testnet-core-1  Starting
[FAILED]  Container dashmate_4b6ad327_testnet-drive_abci-1  Started
[FAILED]  Container dashmate_4b6ad327_testnet-dashmate_helper-1  Started
[FAILED] Error response from daemon: driver failed programming external connectivity on endpoint dashmate_4b6ad327_testnet-core-1 (e0543e20a7cba6eebdcd1a639bbf03ae265ecd73e9a66b5511bf877a5a55d903): Bind for 127.0.0.1:39998 failed: port is already allocated
[FAILED] 
[FAILED] Docker Compose error: time="2026-01-17T19:52:40Z" level=warning msg="Found orphan containers ([dashmate_4b6ad327_testnet-gateway_rate_limiter-1 dashmate_4b6ad327_testnet-gateway_rate_limiter_redis-1]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up."
[FAILED]  Container dashmate_4b6ad327_testnet-drive_abci-1  Created
[FAILED]  Container dashmate_4b6ad327_testnet-dashmate_helper-1  Created
[FAILED]  Container dashmate_4b6ad327_testnet-drive_abci-1  Starting
[FAILED]  Container dashmate_4b6ad327_testnet-dashmate_helper-1  Starting
[FAILED]  Container dashmate_4b6ad327_testnet-core-1  Starting
[FAILED]  Container dashmate_4b6ad327_testnet-drive_abci-1  Started
[FAILED]  Container dashmate_4b6ad327_testnet-dashmate_helper-1  Started
[FAILED] Error response from daemon: driver failed programming external connectivity on endpoint dashmate_4b6ad327_testnet-core-1 (e0543e20a7cba6eebdcd1a639bbf03ae265ecd73e9a66b5511bf877a5a55d903): Bind for 127.0.0.1:39998 failed: port is already allocated
[FAILED] 

I have both network mainnet and testnet networks running on the same instance, and probably that's what is affecting

Possible Solution

Probably code does not handle port for different network on the same machine

Steps to Reproduce (for bugs)

1. Install dashmate v3.0.0-rc.2 on a node where both mainnet and testnet network running
2. dashmate update
3. dashmate restart

Context

There was a similar issue in v2.0.0 dev releases that from what I remember gave me the same errors