microsoft / microsoft/mcp

Docker Image crashing when using "--dangerously-disable-http-incoming-auth"

Open
#3,153 1 comment 0 reactions 0 assignees View on GitHub
bug server-Azure.Mcp tools-Core
Dominant language
C#
Stars
3.7k
Forks
624
Avg merge
2d 20h
Merged PRs (30d)
220

Description

### Describe the bug

When trying to start the mcp server as docker container using it with the flag `--dangerously-disable-http-incoming-auth`, the docker container is restarting over and over again.

### Expected behavior

Should run and accept incoming http requests as it is only a development environment.

### Actual behavior

Docker image is restarting over and over again.

### Reproduction Steps

docker-compose.yml:
```yaml
services:
"mcp-azure":
image: mcr.microsoft.com/azure-sdk/azure-mcp:latest
container_name: mcp-azure
restart: always
ports:
- "8080:8080"
environment:
- AZURE_TOKEN_CREDENTIALS=AzureCliCredential
- ASPNETCORE_URLS=http://0.0.0.0:8080
- ASPNETCORE_ENVIRONMENT=Development
volumes:
- ~/.azure:/root/.azure:ro
command:
[
"--transport",
"http",
"--read-only",
"--dangerously-disable-http-incoming-auth",
]
```

run: `docker compose up`

### Environment

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the docker-compose.yml reproduction and run docker compose up while checking the container logs for the restart cause. Trace how the Docker image handles the http transport and --dangerously-disable-http-incoming-auth flag; done means the container stays running and accepts incoming HTTP requests on port 8080.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, docker, docker-compose
Domain
backend, devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.