[Bug] The web application fails to start, and there are no logs. What could be the problem?

[nocultrue]

Component

Docker / infrastructure

Description

The web application fails to start, and there are no logs. What could be the problem?

Steps to Reproduce

./redamon.sh install

Expected Behavior

web not run

Actual Behavior

The web application fails to start

Environment

Logs

no logs

Screenshots

[samugit83]

Hi @nocultrue, thanks for the detailed report and the inspect output, that helps a lot.

The key clue is in your docker inspect: the container is running with Args: ["node"] and exits with code 0 after ~300ms. That means the webapp container is starting a bare node process (the base image default), which opens a Node REPL, immediately hits end-of-input, and exits cleanly with no output. So the empty logs are expected: nothing actually started. The restart: unless-stopped policy then loops it, which is your RestartCount: 11.

A correctly built webapp image does not do this. Its startup command is /app/entrypoint.sh, which prints Syncing Prisma schema... and then runs node server.js. Seeing Args: ["node"] instead means the container is not running the finished production image, so the real failure happened earlier (at build time or in image resolution), not at runtime. That is why there are no runtime logs to see.

The two usual causes:

1. A leftover docker-compose.override.yml. Docker Compose auto-merges that file on every command. If one exists and swaps the webapp to a plain node:* image, you get exactly this behavior.
2. The webapp image build did not finish the final stage (commonly the Next.js npm run build step was killed for running out of memory), so an intermediate node-based image is what ends up running.

Could you share the following so we can pinpoint it:

1. Does an override file exist?

   ls -la docker-compose.override.yml
   

2. What image and command is the container actually using?

   docker inspect redamon-webapp --format '{{.Config.Image}} | {{json .Config.Cmd}} | {{json .Config.Entrypoint}}'
   

3. The build output (this is where the real error will appear):

   docker compose --profile tools build webapp
   

   Please paste the last ~30 lines, especially any step that ends in Killed, error, or a non-zero exit.
4. Your machine's RAM and CPU architecture (x86_64 vs arm64).

If it turns out to be the build running out of memory, raising Docker's available memory (4 GB or more) and rebuilding with docker compose build --no-cache webapp usually resolves it. We will confirm once we see the output above.