Error response from daemon: Ports are not available: exposing port TCP 0.0.0.0:8080 -> 127.0.0.1:0: listen tcp 0.0.0.0:8080: bind: address already in use

[ericobreque]

Preconditions and environment

In the automated setup: Error response from daemon: Ports are not available: exposing port TCP 0.0.0.0:8080 -> 127.0.0.1:0: listen tcp 0.0.0.0:8080: bind: address already in use

Steps to reproduce

.

Expected result

.

Actual result

.

Additional information

No response

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @ericobreque. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hi @ericobreque,

Thanks for your reporting and collaboration.

Could you please provide us Steps to reproduce,actual and expected results to proceed further.

Thanks.

[bhennesAdv]

Hello @ericobreque ,

Once again, I'm pretty sure that the issue is not related with the magento codebase.
According to the message you gave, you are trying to start a docker container which needs to bind on 8080 port of your machine.

I'm assuming that you are already running an apache2 or nginx on the current machine meaning that the port cannot be binded by docker.
If you are using linux, you can list the application binding on 8080 using :

sudo lsof -i :8080
# I think you should get the following result (or nginx instead of apache2)
COMMAND    PID     USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
apache2 XXXXXX     root    4u  IPv6 XXXXXXX      0t0  TCP *:http (LISTEN)
apache2 XXXXXX www-data    4u  IPv6 XXXXXXX      0t0  TCP *:http (LISTEN)
apache2 XXXXXX www-data    4u  IPv6 XXXXXXX      0t0  TCP *:http (LISTEN)

If you want to start docker with those listening port, you must close the application already listening to the port.
You can find tons of article on the internet about this issue.

Hope this helps,
Regards,
Baptiste

[engcom-Bravo]

@bhennesAdv Thanks for your Contribution!!.

As per this comment #39778 (comment) since the issue is not related to magento codebase we are closing this issue.

Thanks.