network sxastarter_default was found but has incorrect label com.docker.compose.network set to ""

You might have faced an error while making the container up using the up.ps1 script, and subsequently, when attempting to run docker compose down followed by docker compose up. This mostly happens when you make the containers up and then containers creates the network but you don't down them gracefully, or don't use down command before shutting down your system.

To resolve this problem, follow these steps:

1. Run docker network ls to show all the available networks.


2. If you want to remove specific network use the command docker network rm <network Id> to remove the network causing issue in the up containers, which in our case is sxastarter_default.


Run docker network prune to remove all networks. Note: This command will delete all unused networks on your system.

3. Open command prompt and stop IIS by command iisreset /stop

4. Check in the services if there is any solr service using port 8984 (mostly in the docker-compose file this is the port used untill you did not change it) and stop that service.

5. Once the network deletion is complete, run docker compose up -d or ./up.ps1 to start the containers.

The issue should be resolved, and it should work fine.

6. If after 2nd point you get an error that endpoint is already is in use and unable to delete the network then down your containers -> init.ps1 -> up.ps1.


Reference: https://alvaropmontenegro.com/2024/05/31/sitecore-xm-cloud-local-setup-errors/ 

Thanks!

1 comment:

  1. https://sitecorepeanuts.blogspot.com/2024/06/network-sxastarterdefault-was-found-but_12.html

    ReplyDelete

Creating Solr core for sitecore using command prompt

We setup the solr cores using command “C:\solr8985\sc103solr-8.11.2\bin>solr.cmd create -c sitecore_sxa_web_index -d sitecore_configset” ...