# Unable to uninstall modules in an ignition 8.3 docker container

**URL:** <https://forum.inductiveautomation.com/t/unable-to-uninstall-modules-in-an-ignition-8-3-docker-container/110861>\
**Category:** Ignition\
**Tags:** ignition83\
**Created:** [September 23, 2025, 3:50am UTC](https://forum.inductiveautomation.com/t/unable-to-uninstall-modules-in-an-ignition-8-3-docker-container/110861 "2025-09-23T03:50:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Samuel\_Weston](https://avatars.discourse-cdn.com/v4/letter/s/b5e925/32.png) [@Samuel\_Weston](https://forum.inductiveautomation.com/u/Samuel_Weston)\
**Post date:** [September 23, 2025, 3:50am UTC](https://forum.inductiveautomation.com/t/unable-to-uninstall-modules-in-an-ignition-8-3-docker-container/110861/1 "2025-09-23T03:50:42Z")

</div>

I’ve spun up a docker container running the ignition 8.3 image, linked here:

[https://hub.docker.com/r/inductiveautomation/ignition](https://hub.docker.com/r/inductiveautomation/ignition)

For some reason I’m unable to delete any of the default modules from the gateway, regardless of if they’re disabled or not. I just get this error message each time:

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

---

<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:** [September 23, 2025, 11:33am UTC](https://forum.inductiveautomation.com/t/unable-to-uninstall-modules-in-an-ignition-8-3-docker-container/110861/2 "2025-09-23T11:33:44Z")

</div>

You cannot uninstall them--they are part of the base image IIRC. You can only disable them.

---

<div class="post-metadata">

**Author:** ![mar.zapala](https://avatars.discourse-cdn.com/v4/letter/m/45deac/32.png) [@mar.zapala](https://forum.inductiveautomation.com/u/mar.zapala)\
**Post date:** [November 7, 2025, 5:11pm UTC](https://forum.inductiveautomation.com/t/unable-to-uninstall-modules-in-an-ignition-8-3-docker-container/110861/3 "2025-11-07T17:11:43Z")

</div>

You can actually remove module files using container console. But anyway…

Is it normal, that after disabling any module (for example Omron), status of the module is shown as “faulted” instead of “disabled” after restarting Ignition container?

---

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [November 11, 2025, 4:57pm UTC](https://forum.inductiveautomation.com/t/unable-to-uninstall-modules-in-an-ignition-8-3-docker-container/110861/4 "2025-11-11T16:57:26Z")

</div>

> [@mar.zapala](#):
>
> Is it normal, that after disabling any module (for example Omron), status of the module is shown as “faulted” instead of “disabled” after restarting Ignition container?

Nope. If it is in `FAULTED` state, there should be an error in the wrapper log with more insight. It should display `INACTIVE` status once disabled (and gateway has restarted).

 ![SCR-20251111-jyra](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/7/772657e8fd3923a15017e64ee1b6b398d40af419.png)

Inspecting the `data/modules.json` (the file that defines which modules to load and whether they're enabled/disabled) will also show the module with an `onStartup` as disabled:

```json
...
  "com.inductiveautomation.opcua.drivers.omron": {
    "filename": "/usr/local/bin/ignition/user-lib/modules/Omron-Driver.modl",
    "onStartup": "disabled",
    "certFingerprint": "0299d53c38bdbe7ca79bd6c778a5bab884e4c813"
  },
...

```