[BUG] Docker image does not start: `next: command not found`

[Giulio De Pasquale]

Describe the bug
The image built through the official Dockerfile does not run as expected.

> web@0.0.1 start /unsaged/apps/web
> next start

sh: next: not found
 ELIFECYCLE  Command failed.
 WARN   Local package.json exists, but node_modules missing, did you mean to install?
 ```

[ufulu]

I had a similar issue, where I would get the exact same output if I built the image via docker-compose.

If I first build the image with:
docker build -t unsaged -f apps/web/Dockerfile . --rm

and then reference this image in my docker-compose, everything works fine.