Stop jag startup on crashed container after `-D jag.disabled -D jag.timeout=16h`

Toit

#Stop jag startup on crashed container after `-D jag.disabled -D jag.timeout=16h`

Thread channel in help

addshore 03/04/2025 06:54 AM

I have a jag container that I start with -D jag.disabled -D jag.timeout=16h, however if it crashes or restarts jag seems to come back.
Is there a way to prevent this?

bitphlipphar 03/04/2025 06:56 AM

Would you want your container to restart on crashes? How does the container restart?

bitphlipphar 03/04/2025 06:57 AM

I think jag just listens for termination events, but that could be extended.

bitphlipphar 03/04/2025 06:58 AM

The logic is around here: https://github.com/toitlang/jaguar/blob/c3781580d5a11f2f1e7c4db57e84922f664c431a/src/jaguar.toit#L291

jaguar/src/jaguar.toit at c3781580d5a11f2f1e7c4db57e84922f664c431a ...

Use live reloading over WiFI to turbo-charge developing for your ESP32. - toitlang/jaguar

addshore 03/04/2025 07:03 AM

Would you want your container to restart on crashes? How does the container restart?

Yes probably.
TLDR for the container is it sets up its own access point, hence jag needs turning off
and seemingly sometimes it OOMs in the wifi stack for some reason (perhaps while im buksy dooing other stuff

floitsch 03/04/2025 08:39 AM

Just in case: I see a 16h timeout and infrequent OOMs being a concern. This makes me think you want to deploy Jaguar in production.
Typically we use Jaguar only for development. Deployed products don't need it anymore.

6 messages in total