Startup Issues

Volume Mounting Error on WSL

Symptom. When running docker compose up -d, the following error occurs:

Error response from daemon: error while mounting volume '/var/lib/docker/volumes/proxy_proxy_configs/_data': 
failed to mount local volume: mount /run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu/...
: no such file or directory

Solution.

A volume can only be deleted after deleting the containers it is mounted to. Monitoring data (Grafana, Prometheus) will be preserved.

1. In Docker Desktop, go to the Containers section, open the proxy project.
2. Delete the hashcore-stratum-proxy and hashcore-proxy-configurator containers.
3. Go to the Volumes section and delete proxy_proxy_configs.
4. Restart WSL (in PowerShell as administrator): powershell wsl --shutdown
5. Wait for Docker Engine to restart and its status to change to "Engine running".
6. Start all services again — Docker will recreate the containers and volume automatically: bash docker compose up -d
7. Make sure all containers are running: ```bash docker ps

#### Port Conflicts
**Symptom.** Containers do not start, and logs show a message that a port is already in use.

**Solution.** Change the occupied ports in the `docker-compose.yml` file.

> ⚠️ Ports are specified in the format `"EXTERNAL_PORT:INTERNAL_PORT"`.
Only change the **left** value (the port available on your PC). The right value (the internal container port) must not be changed.

Examples of correct replacement:

- **Configurator:** `5001:5001` → `5002:5001` (change only the left part)

- **Grafana:** `5000:3000` → `5050:3000` (keep internal port 3000 unchanged)

- **Proxy API:** `5010:5010` → `5020:5010`

#### Permissions Issues (Linux)
**Symptom.** Docker fails to start due to access rights.

**Solution.** Add the current user to the docker group:

```bash
sudo usermod -aG docker $USER

After executing the command, log out and log back in for the changes to take effect.

Monitoring Not Working After Update

Symptom. After running docker compose pull, Grafana or Prometheus do not start or display errors.

Cause. When updating services to a new major version, the data storage format in volumes may change and become incompatible with previously accumulated monitoring data.

Solution A — Delete Monitoring Data (data will be lost):

1. Open Docker Desktop.
2. Go to the Containers section and find the proxy project.
3. Delete the grafana and prometheus containers. > ⚠️ This step will permanently delete all accumulated monitoring data. If the data is important, first back up the volumes.
4. Go to the Volumes section and delete: - proxy_grafana_data

- `proxy_prometheus_data`

5. In the terminal, run: bash docker compose up -d

The system will recreate the volumes and start monitoring with fresh data.

Solution B — Pin Image Versions (data will be preserved):

To prevent this situation from recurring during the next update, pin the image versions in docker-compose.yml. See section 3.4 for details.

If the problem persists after Solution A, please contact support.