铁路部门的各位同事，大家好！

我们的生产服务目前不可用，并返回 HTTP 502 错误。

无论是新建镜像还是使用之前已知良好的镜像，都会在 CREATE_CONTAINER 阶段停滞。SNAPSHOT_CODE、BUILD_IMAGE 和 PUBLISH_IMAGE 阶段均成功完成，但容器始终无法启动，并且没有生成任何应用程序启动日志。

回滚到之前运行正常的版本后，出现了同样的故障模式，服务未能恢复。

由于新镜像和已知良好的回滚镜像在应用程序启动之前都失败了，因此这似乎是容器配置、调度程序或编排问题，而不是应用程序启动失败。

请检查该服务的容器配置和调度程序状态，并协助恢复该服务。

Additional evidence for this ongoing production outage:

The build itself completes successfully:

• Railpack detects Node 22.23.2.
• npm install completes successfully.
• The application files are copied successfully.
• An OCI/Docker image is exported with a valid image digest.
• The image is pushed successfully.

There are no application startup logs because the deployment never reaches the point where the application process can start.

Railway's deployment diagnostics report:

“The build, image push and release all completed successfully, but the container never managed to start. The deployment stopped without recording any specific error.”

The deployment details show:

• Initialization: completed
• Build: completed
• Deploy: completed / 0:00
• Post-deploy: never started
• No application startup logs

The event sequence confirms that SNAPSHOT_CODE, BUILD_IMAGE, and PUBLISH_IMAGE completed, while CREATE_CONTAINER never completed. The only deployment log recorded afterward is “Stopping Container”.

A rollback to a previously successful production image failed at the same container creation stage.

This further confirms that the failure occurs after image build and publish but before application startup. Could Railway staff please inspect the internal CREATE_CONTAINER, compute scheduling, and volume attachment path for this service?

Try set a Custom Start Command on the Service Settings