Troubleshooting - Alfresco Content Services - 23.4 - 23.4 - Ready - Alfresco

Troubleshooting - Alfresco Content Services - 23.4 - 23.4 - Ready - Alfresco - external

Alfresco Content Services

Platform

Alfresco

Product

Alfresco Content Services

Release

23.4

License

If you have issues running docker-compose up after deleting a previous Docker Compose cluster, try replacing step 5 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 to Docker, as advised in docker-compose.yml.

For example, in Docker, change the memory setting in Preferences (Mac) or Settings (Windows) > Resources > Advanced > Memory to at least 13 GB. If you make changes, click Apply & Restart and wait for the process to finish before continuing.

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

When using Linux as Docker host, all the memory in the computer is available to Docker Compose. So no additional actions are required.

When using Docker with Windows Subsystem for Linux (WSL) 2 Backend in Windows, use the .wslconfig file to increase the memory available for Docker Compose.

Note: In order to deploy onto Docker Desktop you need to allocate at least 13 GB (preferably 16 GB) to the Docker Engine on the Resources tab in Docker Desktop’s preferences pane as shown in the screenshot below. This is required because insufficient memory will cause containers to exit without warning.