There are definitely some differences that exist between the kcollins/ignition and inductiveautomation/ignition images. I’m not sure why you’d be having trouble with named volumes on either one (assuming you respect the different locations that you need to use between the two images–kcollins/ignition uses /var/lib/ignition/data as the target location for named volume versus inductiveautomation/ignition needing /usr/local/bin/ignition/data.
Next, let’s talk about why your script might behave differently (under kcollins/ignition image) between a direct shell execution and from under the gateway. When you start a container, the entrypoint is called and launches your application as the configured user (set in the image, see here). The entrypoint for both inductiveautomation/ignition and kcollins/ignition is run as root, but kcollins/ignition steps down (via this logic and the use of gosu) to a normal user called ignition (default UID/GID of 999) to launch the gateway instead of running as root. So unless you docker exec -it -u ignition <container name> bash, you’ll be running as root instead of what the gateway is running at… Sometimes pictures help:
So I suppose where I’d start is to make sure you’re running it as the same user as the gateway is running. It is possible you might have some permissions problems.
Note that as of 8.1.x, inductiveautomation/ignition official image still runs as root.