Specifying Modules on Gateway Docker Compose

I noticed on @kcollins1 Docker Hub, there’s an environment variable to specify the which modules are enabled GATEWAY_MODULES_ENABLED. Is there any way to accomplish this with the Inductive’s Docker Hub?

Restoring a gateway backup with limited modules does not affect which modules are enabled in the container.

What I’d like to accomplish is automatic provisioning of frontend/backend gateways in the scale-out architecture without manually going in and removing unwanted modules.

Right now I think you’d have to build your own image, but this functionality is something on the team’s backlog*.

* well, there’s a ticket describing it, anyway. It looks like it’s being incubated.

@Kevin.Herron beat me to it. We’ve chosen not to implement the solution used by kcollins/ignition image since even it has some nuance that we’d like to be a little cleaner for the official image (regarding managing modules from the gateway webpage being one aspect that comes to mind). That is the reason it is still “incubating”–we want to make sure we get this behavior right and ensure that all aspects work smoothly.

The good news is that if you don’t want to wait, you can customize via a derived image and add some of your own logic rather easily. I whipped up an example that brings in that same GATEWAY_MODULES_ENABLED environment variable functionality against the official image.

forum-50361.zip (3.2 KB)

It works by introducing an entrypoint “shim” script that executes custom logic on container launch and then hands off to the built-in entrypoint from the official image. This approach helps you build your own image without having to start from scratch!

Hope this helps! There will be more examples like this coming “soon”, too, so stay tuned. :slight_smile:


This works great! Thank you for the help.