Fix docker-compose.yml reference (#22793)

Fixes #22656 🛠️
dotnet · Feb 12, 2021 · 3043ea9 · 3043ea9
1 parent 72c367b
commit 3043ea9
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/...ices/multi-container-microservice-net-applications/database-server-container.md b/...ices/multi-container-microservice-net-applications/database-server-container.md
@@ -9,7 +9,7 @@ You can have your databases (SQL Server, PostgreSQL, MySQL, etc.) on regular sta
 
 ## SQL Server running as a container with a microservice-related database
 
-In eShopOnContainers, there's a container named `sqldata`, as defined in the [docker-compose.yml](https://github.com/dotnet-architecture/eShopOnContainers/blob/master/docker-compose.yml) file, that runs a SQL Server for Linux instance with the SQL databases for all microservices that need one.
+In eShopOnContainers, there's a container named `sqldata`, as defined in the [docker-compose.yml](https://github.com/dotnet-architecture/eShopOnContainers/blob/main/src/docker-compose.yml) file, that runs a SQL Server for Linux instance with the SQL databases for all microservices that need one.
 
 A key point in microservices is that each microservice owns its related data, so it should have its own database. However, the databases can be anywhere. In this case, they are all in the same container to keep Docker memory requirements as low as possible. Keep in mind that this is a good-enough solution for development and, perhaps, testing but not for production.