I'm getting the following while trying to build a NextJS app on the latest version of Dagger
#502 and crashing Dagger container
dusk holly
do you have the dagger logs available by any chance for a failed run?
upbeat adder
👋 have you checked if your engine is running and heahtly?
if you run docker exec -i dagger-engine-e4885af3e03f784c buildctl dial-stdiofrom your machine, does it work?
how about docker logs dagger-engine-e4885af3e03f784c?
eternal crater
The container resets when this happens
This probably contains a few of them
I'm also having issues where the build fails in Dagger, but works fine outside of it, but I'm not seeing a clear error from the terminal logs (Dagger or Next)
eternal crater
Could this sort of thing happen because of resource constraints?
My node_modules is like 2.5Gig
well, it just passed for the first time. I feel like there were some errors being hidden, let me see if I can reproduce
eternal crater
Just had a build "hang" for 2 hours, then after another crash like the one above, retrying with the, now restarted, dagger-engine
ok, fresh build passed
eternal crater
it's still pretty flakey, or maybe a pattern?
- good build after a restart
- failed build, no restart, sometimes a few of these
- 502 build, container restart
Once it starts failing, it needs to restart before it works again
Failure always happens during yarn build -> next build
upbeat adder
hey @eternal crater we released v0.9.8 yesterday. Just checking if this still happens there 🙌