Running Ignition in podman container, mount data volume

Ignition
1

Hello I want to use Ignition in podman container and I want to mount my data volume so I have control over the data.

$ cat podman.run
podman  run -d \
-p 11088:8088 \
--name ignition81 \
-e ACCEPT_IGNITION_EULA=Y \
--volume /opt/ignition81/data:/usr/local/bin/ignition/data \
docker.io/inductiveautomation/ignition:8.1.49

I run into:

$ podman logs ignition81
init     | 2025/08/22 13:50:38 | Creating init.properties fileinit     | 2025/08/22 13:50:38 | Creating gateway.xmlcp: cannot stat '/usr/local/bin/ignition/data/gateway.xml_clean': No such file or directory

According to Docker Image | Ignition User Manual I should be able to mount named volume. It alos says “If the volume doesn't already exist, it will be created automatically.” Is this a docker thing? Because when I rm the dir I get “Error: statfs /opt/ignition81/data: no such file or directory“.

I found here on forum some strange cp tricks, no, I just want a fresh install to start a new GW. I also asked AI, it recomend create without named volume, then stop cantainer then:

podman cp ignition81:/usr/local/bin/ignition/data /opt/ignition81/

Which is also totally awkward and doesnt work anyway because this doesnt keep permissions.

What is a standart way to do this? According to the manual, it should be no problem.

2

There is a difference between named volume and a host volume.

--volume igntion81-data:/usr/local/bin/ignition/data

is a named volume

--volume /opt/ignition81/data:/usr/local/bin/ignition/data

is a host volume.

With any other container image, this makes no difference. But with ignition image it is. One works, the other not.