Looks like npm install isnt running? I see the install command has some conditional logic in the dockerfile but didn't spend too much time digging into why it's skipping over the install. I did a fresh no-cache build and still had the issue (next ultimately wasn't installed so the startup failed) - I was able to manually fix it by running npm install myself in the container after starting it with a dummy entrypoint.
jon-funk@Atlas:~/projects/robotgen$ docker compose up frontend
[+] Building 0.0s (0/0)
[+] Running 1/0
✔ Container robotgen-frontend-1 Created 0.0s
Attaching to robotgen-frontend-1
robotgen-frontend-1 |
robotgen-frontend-1 | > front@0.1.0 dev
robotgen-frontend-1 | > next dev
robotgen-frontend-1 |
robotgen-frontend-1 | sh: next: not found
robotgen-frontend-1 exited with code 127
Looks like npm install isnt running? I see the install command has some conditional logic in the dockerfile but didn't spend too much time digging into why it's skipping over the install. I did a fresh no-cache build and still had the issue (next ultimately wasn't installed so the startup failed) - I was able to manually fix it by running npm install myself in the container after starting it with a dummy entrypoint.