# Docker Resourcing

**URL:** <https://forum.inductiveautomation.com/t/docker-resourcing/76331>\
**Category:** Ignition\
**Tags:** docker\
**Created:** [July 13, 2023, 3:05pm UTC](https://forum.inductiveautomation.com/t/docker-resourcing/76331 "2023-07-13T15:05:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![David.Reed.Schmidt](https://avatars.discourse-cdn.com/v4/letter/d/5f9b8f/32.png) [@David.Reed.Schmidt](https://forum.inductiveautomation.com/u/David.Reed.Schmidt)\
**Post date:** [July 13, 2023, 3:05pm UTC](https://forum.inductiveautomation.com/t/docker-resourcing/76331/1 "2023-07-13T15:05:12Z")

</div>

I can find on the IA webpage the minimum resources Ignition will need on a traditional host. Is there the same for docker containers. If I have a Linux VM and I want to run several Ignition containers on it in order to simulate a bigger architecture then how big will that VM need to be?

---

<div class="post-metadata">

**Author:** ![woodsb02](https://avatars.discourse-cdn.com/v4/letter/w/6a8cbe/32.png) [@woodsb02](https://forum.inductiveautomation.com/u/woodsb02)\
**Post date:** [July 13, 2023, 10:15pm UTC](https://forum.inductiveautomation.com/t/docker-resourcing/76331/2 "2023-07-13T22:15:49Z")

</div>

If I understand it correctly, the Igntion project will consume the same amount of CPU/RAM/disk resources if it’s running in a docker container or directly on the host. From the **application** perspective, running multiple ignition docker containers on a single VM would use similar resource as running a VM per ignition m gateway.

However, using containers does save on operating system overhead compared to individual VMs, as only a single kernel is running.

I would probably expect to use the existing sizing guide as is, but ignore the comment in section 3 about leaving 1-2GB RAM available for the operating system (only account for this once on the VM, not per docker container).

[https://inductiveautomation.com/resources/article/ignition-server-sizing-and-architecture-guide](https://inductiveautomation.com/resources/article/ignition-server-sizing-and-architecture-guide)

---

<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:** [July 13, 2023, 11:13pm UTC](https://forum.inductiveautomation.com/t/docker-resourcing/76331/3 "2023-07-13T23:13:04Z")

</div>

Generally agree with @woodsb02 response above. 👍

With containers, you're not only sharing the host kernel, you're also not duplicating all of the other host OS processes such as systemd, sshd, cron, snapd, _and on and on_.

Also, keep in mind that memory settings for the Ignition container targets the JVM Heap memory size. You may observe usage above that threshold due to non-heap memory. Good to leave a buffer above that max heap size.