> ## Content Index
> Fetch the complete content index at: https://www.gowthamaraja.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# level=warning network was found but has incorrect label com.docker.compose.network set to ""
- URL: https://www.gowthamaraja.com/fix-sitecore-docker-installation-errors/
- Published: 2023-09-10T18:30:00.000Z
- Updated: 2025-11-17T07:18:40.000Z
- Author: Gowtham
- Tags: Sitecore Docker, Sitecore

I ran into an error while trying to install a Sitecore Docker instance using the Sitecore Getting Started Template and if the error is related to "network nat is ambiguous". This happened recently.

```
level=warning msg="a network with name tac_default exists but was not created by compose.\nSet `external: true` to use an existing 
network"
network tac_default was found but has incorrect label com.docker.compose.network set to ""d

```

![No connection could be made because the target machine actively refused it](https://static.wixstatic.com/media/14fd51_cd5540b149b74dcea2b2c112ca8f9326~mv2.jpg/v1/fill/w_740,h_434,al_c,q_80,usm_0.66_1.00_0.01,enc_avif,quality_auto/14fd51_cd5540b149b74dcea2b2c112ca8f9326~mv2.jpg)

No connection could be made because the target machine actively refused it

I couldn't find a straightforward answer online to fix the problem, so I decided to investigate it myself. You might run into a similar issue when you use the up.ps1 script to start a container, and then you get an error when you try to use "*docker compose down*" followed by "*docker compose up*." This problem probably happens because the network interface created by up.ps1 isn't working correctly when you run "docker compose up."

To solve this issue, do the following:

1. Type "*docker network ls*" to see all the networks available.
2. Enter "*docker network prune*" to remove all the networks. Note: This command deletes any unused networks on your system.
3. If you need to remove a specific network, use "*docker network rm <network Id>*" followed by the network Id to remove the problematic one.
4. Once the network cleanup is done, use "*docker compose up -d*" to start the containers.

After following these steps, the problem should be fixed, and "docker compose up" should work without any issues.

## Reference

1. [https://docs.docker.com/engine/reference/commandline/network\_prune/](https://docs.docker.com/engine/reference/commandline/network%5Fprune/?ref=gowthamaraja.com)
2. [https://docs.docker.com/engine/reference/commandline/network\_ls/](https://docs.docker.com/engine/reference/commandline/network%5Fls/?ref=gowthamaraja.com)
3. [https://sitecore.stackexchange.com/a/35447/976](https://sitecore.stackexchange.com/a/35447/976?ref=gowthamaraja.com)