Comment 1 for bug 1812274

I ran into this myself with the standalone. I started the container in interactive mode with paunch debug and found it was selinux denying access to the file. setenforce 0 and the container works fine.