---
title: "Comment by John Pankowicz on \"How to run ASP.NET Core & SQL Server from Docker\" | Hashnode"
description: "Thanks for the great article. After cloning your project, I thought I would also be able to build & run the containers with "docker-compose up". B"
url: "https://hashnode.com/posts/how-to-run-aspnet-core-and-sql-server-from-docker/5f944d7540346172a86c1b05/comment/621d7c9c085330c3f79c7490"
---

[Discussion](https://hashnode.com/posts/how-to-run-aspnet-core-and-sql-server-from-docker/5f944d7540346172a86c1b05)

Comment [How to run ASP.NET Core & SQL Server from Docker](https://hashnode.com/posts/how-to-run-aspnet-core-and-sql-server-from-docker/5f944d7540346172a86c1b05)

[John Pankowicz](https://hashnode.com/@johnp)

[Mar 1, 2022](https://hashnode.com/posts/how-to-run-aspnet-core-and-sql-server-from-docker/5f944d7540346172a86c1b05/comment/621d7c9c085330c3f79c7490)

Thanks for the great article.

After cloning your project, I thought I would also be able to build & run the containers with "docker-compose up". But I encountered many problems. (Unable to start Kestrel, db login failure, db seed failure). I would solve one problem and find another.

I finally realized that the containers can only be built successfully by running the docker-compose (.dcproj) project. When that runs, entirely different Dockerfiles and docker-compose.yml files are used, as can be seen in the "container tools" output window.

In other words, if I use Visual Studio to create docker containers, it appears that only developers who use VS will be able to work on the project. This would be a problem on an open source project, where developers are using many different tools. Is this a fair assessment?