add: Dockerized mining setup

[upbqdn]

Motivation

• Close Add Dockerized mining setup #10239

Follow-up Work

PR Checklist

• The PR name is suitable for the release notes.
• The PR follows the contribution guidelines.
• The library crate changelogs are up to date.
• The solution is tested.
• The documentation is up to date.

[gustavovalverde]

Nit:nheqminer already uses profiles: [miner]. A consideration (doesn't need to be this PR): redis and s-nomp could also be placed behind a profiles: [mining] in the main docker/docker-compose.yml, rather than living in a separate docker/mining/ directory with its own compose file.

This would allow composing capabilities from a single file:

# Just Zebra
docker compose up -d

# Zebra + mining pool
docker compose --profile mining up -d

# Zebra + mining pool + CPU miner
docker compose --profile mining --profile miner up -d

# Zebra + observability
docker compose --profile monitoring up -d

# Everything
docker compose --profile mining --profile miner --profile monitoring up -d

This is the pattern used in Z3 for the monitoring stack and avoids duplicating the zebra service definition across multiple compose files.

Not blocking for this PR; just flagging the direction in case we'd like to start consolidating the Docker compose

[upbqdn]

Nit:nheqminer already uses profiles: [miner]. A consideration (doesn't need to be this PR): redis and s-nomp could also be placed behind a profiles: [mining] in the main docker/docker-compose.yml, rather than living in a separate docker/mining/ directory with its own compose file.

This would allow composing capabilities from a single file:

# Just Zebra
docker compose up -d

# Zebra + mining pool
docker compose --profile mining up -d

# Zebra + mining pool + CPU miner
docker compose --profile mining --profile miner up -d

# Zebra + observability
docker compose --profile monitoring up -d

# Everything
docker compose --profile mining --profile miner --profile monitoring up -d

This is the pattern used in Z3 for the monitoring stack and avoids duplicating the zebra service definition across multiple compose files.

Not blocking for this PR; just flagging the direction in case we'd like to start consolidating the Docker compose

This mining setup is not something we'd support in production. It's just a forge for devs to bash on, so keeping it separate works better.

[gustavovalverde]

utACK.

Just need CI docs fix

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-04-08 09:52 UTC · Rule: batched
• ✅ Checks skipped · PR is already up-to-date
• ✅ Merged — 2026-04-08 10:03 UTC · at fc4882ae96a1f292d8e9742b403c9ef0f8b9301c

This pull request spent 11 minutes 9 seconds in the queue, including 2 seconds running CI.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • add: Dockerized mining setup #10301
• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule PR Requirements]
  • add: Dockerized mining setup #10301
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • add: Dockerized mining setup #10301
• #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule PR Requirements]
  • add: Dockerized mining setup #10301
• #review-threads-unresolved = 0 [🛡 GitHub repository ruleset rule PR Requirements]
  • add: Dockerized mining setup #10301
• any of [🛡 GitHub repository ruleset rule PR Requirements]:
  • check-success = test crate build success
  • check-neutral = test crate build success
  • check-skipped = test crate build success
• any of [🛡 GitHub repository ruleset rule PR Requirements]:
  • check-success = lint success
  • check-neutral = lint success
  • check-skipped = lint success
• any of [🛡 GitHub repository ruleset rule PR Requirements]:
  • check-success = test success
  • check-neutral = test success
  • check-skipped = test success