Can Ignition run in Docker containers?

[krish]

Few quick questions.

1. Are there any customers running Ignition components (Gateway, Modules) in Docker containers?
2. If not, in theory, is it possible to containerize Ignition and run components as stateless services, and what are some pitfalls in trying to do so?

[code_skin]

Have a look here.

Docker Image for Maker Edition

For those of you interested in leveraging Maker Edition under Docker, I’ve updated my kcollins/ignition image with full support for Maker Edition (along with Full and Edge from before)! If you haven’t checked it out before, there’s no better time to get started with Docker and Ignition. Here are some useful links for everyone to check out (feedback welcomed as well either via GitHub issues (preferably) or e-mail!): GitHub - thirdgen88/ignition-docker: Ignition Docker Development Environment …

[kcollins1]

I’d also direct you to our official Docker Hub repo: https://hub.docker.com/r/inductiveautomation/ignition That should help you get started. We’re working hard to continue to align the Ignition platform as a great container “citizen”.

I know that there are a lot of folks leveraging Ignition in containers in both development and production. Development is still probably the most prevalent use case as you’re able to easily support multiple versions and quickly bring up and down different environments (through leveraging Docker Compose, as one example). For SI’s this is definitely a great time saver.

With respect to stateful vs stateless, the Ignition Gateway is definitely the former. You’ll want to plan on leveraging a persisted volume against the data/ folder. I suppose there might be some interesting possibilities with respect to derived images that bundle gateway state in with the container definition.

I’m very interested (as always) to hear about some of the container implementations out there…