# Ignition on Docker

**URL:** <https://forum.inductiveautomation.com/t/ignition-on-docker/62442>\
**Category:** Ignition\
**Tags:** docker, perspective, vision\
**Created:** [July 29, 2022, 6:45am UTC](https://forum.inductiveautomation.com/t/ignition-on-docker/62442 "2022-07-29T06:45:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nvk27](https://avatars.discourse-cdn.com/v4/letter/n/ea5d25/32.png) [@nvk27](https://forum.inductiveautomation.com/u/nvk27)\
**Post date:** [July 29, 2022, 6:45am UTC](https://forum.inductiveautomation.com/t/ignition-on-docker/62442/1 "2022-07-29T06:45:37Z")

</div>

If we use the Docker image for running Ignition as a container, can it be used only for running Ignition Designer? Or can we also launch clients/sessions from the Ignition container?

Newbie here, I watched the demos and read the documentations, but I couldn’t find the answer- is the entire Ignition Gateway platform (Designer, Vision clients, perspective sessions) containerized ? or just the launching of Designers from the gateway containerized?

---

<div class="post-metadata">

**Author:** ![mpoulsen921](https://avatars.discourse-cdn.com/v4/letter/m/b4bc9f/32.png) [@mpoulsen921](https://forum.inductiveautomation.com/u/mpoulsen921)\
**Post date:** [July 29, 2022, 8:03am UTC](https://forum.inductiveautomation.com/t/ignition-on-docker/62442/2 "2022-07-29T08:03:42Z")

</div>

Everything is containerized.  
You get the complete Ignition Gateway contained in the docker container.