I noted an issue while spinning up a server on > RHEL 7 which means there's a couple of compatibility issues with the quick start code provided. I don't think it should be anything changed in that quickstart but I suspect it may be worthwhile adding to the README.
With the permissions and ownership set to that of the container's runas (steam), the container was unable to create the relevant directories. This was due to SELinux blocking access. To resolve this, add a ":z" to the end of the -v mounts which will add the required contexts for the container to run.
By default, DNS resolution failed on the container even when hard set to a known DNS server (8.8.8.8). To resolve this, I needed to run sysctl -w net.ipv4.ip_forward=1 then restart docker systemctl restart docker to fix.
I don't think either of these issues will be apparent on any other OS bar RHEL and it's offshoots so really believe this will simply be a README level thing. I'll add anything more I find during my work here then I'll make any required changes in a fork if it's suitable.
Hi guys,
I noted an issue while spinning up a server on > RHEL 7 which means there's a couple of compatibility issues with the quick start code provided. I don't think it should be anything changed in that quickstart but I suspect it may be worthwhile adding to the README.
sysctl -w net.ipv4.ip_forward=1then restart dockersystemctl restart dockerto fix.I don't think either of these issues will be apparent on any other OS bar RHEL and it's offshoots so really believe this will simply be a README level thing. I'll add anything more I find during my work here then I'll make any required changes in a fork if it's suitable.
Thanks,
Jim