image.png# Troubleshooting
mindos start prints two URLs on startup:
- Local: http://localhost:3002
- Network: http://<server-ip>:3002
Problem: Clicking the Local URL opens nothing when you're connected via SSH.
Cause: localhost refers to the server's own loopback interface. When you access it from your local machine, it resolves to your machine's localhost — not the server's.
Solutions:
-
Use the Network URL — requires the port to be open in the server's firewall.
-
SSH port forwarding (recommended — no need to expose the port publicly):
ssh -L 3002:localhost:3002 user@<server-ip>
Then open
http://localhost:3002in your local browser.
The client is installed but no daemon is listening on /var/run/docker.sock (service not running, or you lack permission).
- Start Docker (Linux):
sudo systemctl start dockerthensudo systemctl enable docker. - Permission: add your user to the
dockergroup, then re-login:sudo usermod -aG docker "$USER". - Not installed: use your distro’s package (
docker.ioon Debian/Ubuntu,docker-cefrom Docker’s docs) or your cloud’s “容器服务”文档.
BuildKit / buildx (optional): sudo apt install docker-buildx-plugin (Debian/Ubuntu) or set export DOCKER_BUILDKIT=1 when building.
See also DOCKER.md in the repo root.
Usually docker compose is not available (Compose V2 plugin not installed), so the CLI does not enter the compose subcommand and --rm is parsed as a top-level docker flag (invalid).
- Install the plugin:
sudo apt install docker-compose-plugin(Debian/Ubuntu) orsudo dnf install docker-compose-plugin/sudo yum install docker-compose-plugin(Fedora/RHEL-style — noapton these). If the package is missing, follow Docker Engine install for your distro. - Verify:
docker compose version. - Run onboard without
--rm:docker compose run mindos mindos onboard, or use standalonedocker-compose run --rm …if you only have the v1 binary.