Startup Issues
Resolving common HashCore Proxy startup problems: WSL volume mount errors, port conflicts, permission issues.
Volume Mount Error on WSL
Symptom. Running docker compose up -d produces an error:
Error response from daemon: error while mounting volume...
failed to mount local volume: no such file or directory
Solution: 1. In Docker Desktop → Containers → project proxy → delete hashcore-stratum-proxy and hashcore-proxy-configurator.
2. Go to Volumes → delete proxy_proxy_configs.
3. Restart WSL in PowerShell as Administrator:
wsl --shutdown
- Wait for the "Engine running" status in Docker Desktop.
- Start the services again:
docker compose up -d
Port Conflicts
Symptom. Containers fail to start, logs show a message that a port is already in use.
Solution. Change the conflicting ports in docker-compose.yml.
⚠️ Ports are specified in the format
"EXTERNAL_PORT:INTERNAL_PORT". Only change the left value — the right value (internal container port) must not be changed.
Examples:
- Configurator:
5001:5001→5002:5001 - Grafana:
5000:3000→5050:3000 - Proxy API:
5010:5010→5020:5010
Permission Issues (Linux)
Symptom. Docker fails to start due to permission errors.
Solution. Add the current user to the docker group:
sudo usermod -aG docker $USER
Log out and back in for the changes to take effect.
Monitoring Not Working After Update
Symptom. Grafana or Prometheus fail to start after docker compose pull.
Cause. A major version upgrade may make the volume data format incompatible with previously accumulated data.
Solution A — delete monitoring data (data will be lost): 1. Docker Desktop → Containers → delete grafana and prometheus containers.
2. Volumes → delete proxy_grafana_data and proxy_prometheus_data.
3. docker compose up -d
Solution B — pin image versions (data preserved):
Pin image versions in docker-compose.yml (see the Update section).