MK_ONLY_SERVER is broken?

[caipira113]

💡 Summary

Running with MK_ONLY_SERVER set to true is not possible.

🥰 Expected Behavior

Only web servers are running normally.

🤬 Actual Behavior

--- LEGION-5P (PID: 45948) ---
18:10:37 INFO * [core boot]     Welcome to Misskey!
18:10:37 INFO * [core boot]     Misskey v2023.9.0-beta.2
18:10:37 INFO * [core boot env] NODE_ENV: production
18:10:37 INFO * [core boot nodejs]      Version v20.6.0 detected.
18:10:37 DONE * [core boot config]      Loaded
18:10:37 INFO * [core nest]     NestFactory: Starting Nest application...
18:10:37 INFO * [core nest]     InstanceLoader: MainModule dependencies initialized
18:10:37 INFO * [core nest]     InstanceLoader: QueueModule dependencies initialized
18:10:39 INFO * [core nest]     InstanceLoader: GlobalModule dependencies initialized
18:10:39 INFO * [core nest]     InstanceLoader: RepositoryModule dependencies initialized
18:10:39 INFO * [core nest]     InstanceLoader: DaemonModule dependencies initialized
18:10:40 INFO * [core nest]     InstanceLoader: ServerModule dependencies initialized
18:10:40 INFO * [core nest]     InstanceLoader: EndpointsModule dependencies initialized
18:10:40 INFO * [core nest]     InstanceLoader: CoreModule dependencies initialized
18:10:46 DONE * [core boot]     Misskey initialized
18:10:46 INFO * [core boot]     Starting 1 worker...
18:10:53 INFO 1 [core nest]     NestFactory: Starting Nest application...
18:10:53 INFO 1 [core nest]     InstanceLoader: MainModule dependencies initialized
18:10:53 INFO 1 [core nest]     InstanceLoader: QueueModule dependencies initialized
18:10:55 INFO 1 [core nest]     InstanceLoader: GlobalModule dependencies initialized
18:10:55 INFO 1 [core nest]     InstanceLoader: RepositoryModule dependencies initialized
18:10:55 INFO 1 [core nest]     InstanceLoader: DaemonModule dependencies initialized
18:10:55 INFO 1 [core nest]     InstanceLoader: ServerModule dependencies initialized
18:10:55 INFO 1 [core nest]     InstanceLoader: EndpointsModule dependencies initialized
18:10:55 INFO 1 [core nest]     InstanceLoader: CoreModule dependencies initialized
18:11:01 DONE * [core boot]     All workers started
18:11:01 DONE * [core boot]     Now listening on port 3000 on http://127.0.0.1:3000
18:11:01 ERR  1 [server]        Port 3000 is already in use by another process.
18:11:01 ERR  * [core boot]     The server Listen failed due to the previous error.
18:11:01 INFO * [core]  The process is going to exit with code 1
Error: bind EADDRINUSE 0.0.0.0:3000
    at listenOnPrimaryHandle (node:net:1808:18)
    at shared (node:internal/cluster/child:156:3)
    at Worker.<anonymous> (node:internal/cluster/child:109:7)
    at process.onInternalMessage (node:internal/cluster/utils:49:5)
    at process.emit (node:events:525:35)
    at emit (node:internal/child_process:937:14)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -4091,
  code: 'EADDRINUSE',
  syscall: 'bind',
  address: '0.0.0.0',
  port: 3000
}
18:11:01 INFO 1 [core]  The process is going to exit with code 0
 ELIFECYCLE  Command failed with exit code 1.

📝 Steps to Reproduce

1. MK_ONLY_SERVER="true" pnpm start

📌 Environment

🛰 Backend (for server admin)

• Installation Method or Hosting Service: local dev
• Misskey: 2023.9.0-beta.2
• Node: 20.6.0
• PostgreSQL: 15.4
• Redis: 7
• OS and Architecture: Windows 11 Pro Insider Preview 23531.1001 amd64