-
Notifications
You must be signed in to change notification settings - Fork 1k
Description
(base) $ cat docker-compose.yaml
services:
inspector:
image: ghcr.io/modelcontextprotocol/inspector:latest
container_name: testins
restart: unless-stopped
ports:
- "6274:6274"
- "6277:6277"
environment:
- HOST=0.0.0.0
- DANGEROUSLY_OMIT_AUTH=true
- ALLOWED_ORIGINS=*
- NPM_CONFIG_REGISTRY=https://registry.npmmirror.com
(base) $ docker compose logs -f
testins |
testins | > @modelcontextprotocol/[email protected] start
testins | > node client/bin/start.js
testins |
testins | Starting MCP inspector...
testins | ⚙️ Proxy server listening on 0.0.0.0:6277
testins |
testins |
testins | 🚀 MCP Inspector is up and running at:
testins | http://0.0.0.0:6274
testins |
testins | 🌐 Opening browser...
testins | Invalid origin: http://192.168.8.88:6274
testins | Invalid origin: http://192.168.8.88:6274
testins | Invalid origin: http://192.168.8.88:6274
testins | Invalid origin: http://192.168.8.88:6274
testins | Invalid origin: http://192.168.8.88:6274
testins | Invalid origin: http://192.168.8.88:6274
When a Docker container is started on an internal network server, is there something wrong with my configuration?