After starting docker-compose yml, the port 5080 is getting conflict. I have attached the YML file.
But I do not know if I did something wrong on docker-compose.yml.
$ docker-compose -f docker-compose-auth-v9011.yml up -d
Starting images_xc_1 ... done
Recreating images_utils_1 ... done
Starting images_db_1 ... done
Recreating images_txn_1 ... error
ERROR: for images_txn_1 Cannot start service txn: driver failed programming external connectivity on endpoint images_txn_1 (1dbb46b53952cf25da7229578b9c80bd38f91e5effe76ef519df4e4b270e8b59): Error starting userland proxy: Bind for 0.0.0.0:5080: unexpected error Permission denied
Starting images_search_master_1 ... done
ERROR: for txn Cannot start service txn: driver failed programming external connectivity on endpoint images_txn_1 (1dbb46b53952cf25da7229578b9c80bd38f91e5effe76ef519df4e4b270e8b59): Error starting userland proxy: Bind for 0.0.0.0:5080: unexpected error Permission denied
ERROR: Encountered errors while bringing up the project.
AzureAD+IgorMonteiroVieira@DESKTOP-FEIKH4N MINGW64 ~/Box Sync/Commerce/Prototype/Images
$ docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
69a04e6193d4 commerce/ts-utils:9.0.1.1 "/SETUP/bin/entrypoi…" 58 seconds ago Up 54 seconds (healthy) 5080/tcp, 5443/tcp images_utils_1
1f2799e8950b commerce/search-app:9.0.1.1 "/SETUP/bin/entrypoi…" 20 minutes ago Up 22 seconds (health: starting) 0.0.0.0:3737-3738->3737-3738/tcp images_search_master_1
e3521501461f commerce/xc-app:9.0.1.1 "/SETUP/bin/entrypoi…" 21 minutes ago Up 55 seconds 0.0.0.0:9080->9080/tcp, 0.0.0.0:9443->9443/tcp images_xc_1
669acff390e8 commerce/ts-db:9.0.1.1 "/bin/bash /SETUP/bi…" 21 minutes ago Up 55 seconds (healthy) 0.0.0.0:50000->50000/tcp, 50001/tcp images_db_1
Sorry, new users cannot upload files. So I had to paste the content of docker-compose.yml .
As you know, the port 5080 is getting conflict, but I do not know what I need to fix on the YML file
The question is, do you really need all these published ports? You publish a port to make it available (for you) at localhost:portnumber. For the communication between the containers you don’t have to publish anything.