Docker: will not start, Error: listen EADDRINUSE: address already in use :::3001

[sabotagebeats]

@HenkHui @jairo-bc is this the same issue?

$ docker run -p 3000-3010:3000-3010 -v /$(pwd):/usr/src/app -it ghcr.io/bigcommerce/stencil-cli:lat
est stencil start

...

[Browsersync] Watching files...
node:events:502
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE: address already in use :::3001
    at Server.setupListenHandle [as _listen2] (node:net:1908:16)
    at listenInCluster (node:net:1965:12)
    at Server.listen (node:net:2067:7)
    at Object.startServer [as fn] (/usr/local/lib/node_modules/@bigcommerce/stencil-cli/node_modules/browser-sync-ui/lib/async.js:123:39)
    at /usr/local/lib/node_modules/@bigcommerce/stencil-cli/node_modules/browser-sync-ui/lib/UI.js:185:14
    at iterate (/usr/local/lib/node_modules/@bigcommerce/stencil-cli/node_modules/async-each-series/index.js:8:5)
    at /usr/local/lib/node_modules/@bigcommerce/stencil-cli/node_modules/async-each-series/index.js:16:16
    at /usr/local/lib/node_modules/@bigcommerce/stencil-cli/node_modules/browser-sync-ui/lib/UI.js:193:13
    at Object.setUrlOptions [as fn] (/usr/local/lib/node_modules/@bigcommerce/stencil-cli/node_modules/browser-sync-ui/lib/async.js:76:9)
    at /usr/local/lib/node_modules/@bigcommerce/stencil-cli/node_modules/browser-sync-ui/lib/UI.js:185:14
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1944:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRINUSE',
  errno: -98,
  syscall: 'listen',
  address: '::',
  port: 3001
}

Node.js v20.20.2

Originally posted by @sabotagebeats in #1054

[sabotagebeats]

this issue has to do with using the default port of 3000. When I change to another port other than 3000 or 3001 this lets me at least fire up the container. I'm still unable to see the site at the port I set, but I'm able to see the browsersync page at least.

The page that the site is supposed to come at is listed in browsersync now at http://localhost:3003/ and proxying at http://localhost:3004/

3004 gets empty response
3003 loads infinitely