Troubleshooting - Alfresco Control Center - 9.3 - 9.3 - Ready - Alfresco - external

If you have issues running docker-compose up after deleting a previous Docker Compose cluster, try replacing step 4 in the initial Docker Compose instructions with:

 docker-compose down && docker-compose build --no-cache && docker-compose up

If you’re having issues running docker-compose up on Windows environments due to unavailable or reserved ports, and get errors such as:

bind: An attempt was made to access a socket in a way forbidden by its access permissions

which means that the Windows NAT (WinNAT) service has reserved the port range that Docker Compose is trying to use.

To remedy this issue, run the following in a terminal:

 net stop winnat
 docker-compose up
 net start winnat

Stop the session by using CONTROL+C.

Remove the containers (using the --rmi all option):

 docker-compose down --rmi all

Try allocating more memory resources, as advised in docker-compose.yml.

For example, in Docker, change the memory setting in Preferences (or Settings) Resources > Advanced > Memory to at least 13 GB. Make sure you restart Docker and wait for the process to finish before continuing.

Go back to step 4 in the initial Docker Compose instructions to start the deployment again.