# Issue with Ignition in a docker container, the container is restarting itself

**URL:** <https://forum.inductiveautomation.com/t/issue-with-ignition-in-a-docker-container-the-container-is-restarting-itself/115646>\
**Category:** Ignition\
**Tags:** docker\
**Created:** [May 21, 2026, 4:51pm UTC](https://forum.inductiveautomation.com/t/issue-with-ignition-in-a-docker-container-the-container-is-restarting-itself/115646 "2026-05-21T16:51:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Daniel\_Fernandez](https://avatars.discourse-cdn.com/v4/letter/d/779978/32.png) [@Daniel\_Fernandez](https://forum.inductiveautomation.com/u/Daniel_Fernandez)\
**Post date:** [May 21, 2026, 4:51pm UTC](https://forum.inductiveautomation.com/t/issue-with-ignition-in-a-docker-container-the-container-is-restarting-itself/115646/1 "2026-05-21T16:51:15Z")

</div>

Hi,

I have an Ignition 8.3.3 running in a container, but it is restarting itself a couple of times every day. In the logs I have not seen any errors:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/d/0dca737d3657ac63e61fa6fdcf1a033c3ca9d083.png)

However, sometimes there are logs about a clock drift detection, but just those warnings, no errors.

Is there a way to debug the issue, or is it possible to avoid that automatic restart of the container, or are there any other ideas about that behavior?

Best regards,

Daniel Fernandez

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 21, 2026, 5:02pm UTC](https://forum.inductiveautomation.com/t/issue-with-ignition-in-a-docker-container-the-container-is-restarting-itself/115646/2 "2026-05-21T17:02:40Z")

</div>

That usually indicated that Ignition crashed. Commonly due to memory constraints, but there are many possibilities. The text stream that would be the `wrapper.log` in a VM or bare metal install is instead forwarded to the Docker host. There will be clues there.
