Appreciate the feedback, as always.
I just wanted to make sure that I had been clear that I wasn’t running the unsupported developer-style build, but a reference build in Docker that I use so that if we have problems with our self-supported deployment (our infrastructure team prefers to package everything themselves), I can go back to the reference. We don’t run the betas in our self-supported build, and do sometimes lag behind the latest stable release as a result.
In this particular case, because our production deployment is self-supported, we actually had fixed the ruby issue, but I wasn’t sure how to fix the issue in the docker image itself without rebuilding the image myself.