Nothing is running on 27017. Docker insists otherwise

Amara Walsh · 2026-09-11T06:40:13.625Z

not gonna lie this is driving me nuts this worked fine last week... today, on a fresh Ubuntu box, teh web container dies right away: [code] i didnt change the compose file. port 27017. ive checked Task Manager and htop and i cant find anything obvious :) is Docker keeping a ghost reservation? ive already run docker compose down in the project folder, restarted Docker Desktop and checked that no other terminal is running the stack. The error comes back instantly every time. Is there a command…

Solvedcompose docker ports2 replies · 293 views · started last mo.

Accepted solution by Quinn Garcia — Find who owns the port first: [code] On Windows: netstat ano findstr :8080 and then look up the PID in Task Manager.

Amara Walsh
@quietrider
60 rep · 12 posts
last mo.
not gonna lie this is driving me nuts this worked fine last week... today, on a fresh Ubuntu box, teh web container dies right away:
```
This app can't run on your PC

To find a version for your PC, check with the
software publisher.
```
i didnt change the compose file. port 27017. ive checked Task Manager and htop and i cant find anything obvious :) is Docker keeping a ghost reservation?

ive already run docker compose down in the project folder, restarted Docker Desktop and checked that no other terminal is running the stack. The error comes back instantly every time. Is there a command that just tells me who owns a port? pls help 🙏
4
Quinn Garcia
@quietsmith
43 rep · 5 posts
last mo. Accepted solution
Find who owns the port first:
```
sudo ss -ltnp 'sport = :8080'
# or
sudo lsof -i :8080
```
On Windows: netstat -ano | findstr :8080 and then look up the PID in Task Manager.
2 8 helpful
Amara Walsh
@quietrider
60 rep · 12 posts
last mo.in reply to @quietsmith
@quietsmith omggg moved the mapping to a port outside the excluded range, everything works on a fresh Ubuntu box now, thx for the netsh tip!

2 0 helpful

Reply to this topic