Why is Port 8080 So Common in Docker Compose Files?

0
1
Asked By TechGuru1995 On

I've noticed that many Docker Compose files default to using port 8080, like for Filebrowser and QbitTorrent. Can someone explain why this specific port is often chosen? I tried changing it to port 8888 in my .yml file, but then I couldn't access the applications. How do I properly change ports in my setup?

2 Answers

Answered By CuriousCoder92 On

Port 8080 is just a widely accepted convention. It’s often used as an alternative to port 80, which is the default for HTTP traffic. This makes it easier to remember for developers, especially in local dev environments. For example, many applications use port 8080 so they don't conflict with port 80. If you want to change ports, you can use the `--expose` option in your Docker run command. Check out the Docker docs for more details on that!

Answered By AppDevNinja On

When creating apps, developers often stick to default ports like 8080, but you can map it to any external port you want. If you can't access your app after changing the port, there's a good chance your port mapping setup isn’t right. Sharing your Docker Compose file could help us assist you better!

TechGuru1995 -

Here's my Docker Compose file, but I also can't access Sonarr on port 8989 now. I even tried reinstalling everything. Any ideas?

PortMaster123 -

It's also possible that your Sonarr instance might still be using port 8989 somehow, or there's a permission issue. Have a look at the logs for any clues!

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.