Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
peperunas opened this issue Jan 14, 2024 · 1 comment
Open

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

peperunas opened this issue Jan 14, 2024 · 1 comment

Comments

@peperunas
Copy link

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
Copy link

ufulu commented Jan 17, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants