This PR fixes issue #104 , as PR #108 does not correctly set the volumes to access the gtt configuration file without having to mount the complete user home directory which is a security risk. It also uses a non privileged user to run gtt instead of the root user, which is also a security risk.
Coverage remained the same at 65.979% when pulling 6d1ece0ba50dbbffc40d182f30a2ab9f2cd91311 on juanluisbaptiste:run_as_non_root_user into ec5ca47d2e45f087dccb6bbdddc970935a61c256 on kriskbx:master.
Hi,
This PR fixes issue #104 , as PR #108 does not correctly set the volumes to access the gtt configuration file without having to mount the complete user home directory which is a security risk. It also uses a non privileged user to run gtt instead of the root user, which is also a security risk.