search

opennms-forge / stack-play

🎢 Just the fun parts! - Some docker-compose container stacks for local labs or playgrounds
GNU General Public License v3.0
6 stars 6 forks source link

Horizon containers bomb out when run with tags that have merged non-root #13

Open jeffgdotorg opened 3 years ago

jeffgdotorg commented 3 years ago

If I bring up the minimal-horizon stack with ONMS_VERSION=bleeding (which tracks develop, currently leading up to Horizon 29, which runs by default as a non-root user), the horizon container exits during the installer run with exit code 127 and I see the following at the tail of the container's logs:

17:39:00.244 [Main] ERROR org.opennms.install.Installer - OpenNMS is configured to run as 'opennms' but '/opt/opennms/deploy/.gitkeep' is not writable by that account.
17:39:00.245 [Main] ERROR org.opennms.install.Installer - To fix permissions, run '/opt/opennms/bin/fix-permissions' as root

I assume this can be fixed by changing the volumes entry in the horizon service to use the long format and specify a user / group to own each volume's mount point, but I don't have time to track all that down at the moment. Dropping an issue as it's the second time I've bumped up against it in the past month or so.

indigo423 commented 2 years ago

Yes the non-root thing introduced a few things to figure out, this here falls in the same category https://issues.opennms.org/browse/NMS-13572.

RangerRick commented 2 years ago

Yeah, the openshift thing is probably not going to get fixed in time for 29 unless we get lucky, sprint timing wise, unfortunately.