# Google-protobuf version issue error updating to 3.2.2 from 3.2.1

**URL:** <https://meta.discourse.org/t/google-protobuf-version-issue-error-updating-to-3-2-2-from-3-2-1/312118>\
**Category:** Self-hosting\
**Created:** [June 14, 2024, 4:34pm UTC](https://meta.discourse.org/t/google-protobuf-version-issue-error-updating-to-3-2-2-from-3-2-1/312118 "2024-06-14T16:34:47Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![hendersj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hendersj/32/507887_2.png) [@hendersj](https://meta.discourse.org/u/hendersj)\
**Post date:** [June 19, 2024, 5:23pm UTC](https://meta.discourse.org/t/google-protobuf-version-issue-error-updating-to-3-2-2-from-3-2-1/312118/7 "2024-06-19T17:23:52Z")

</div>

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.

---

_[View the full topic](https://meta.discourse.org/t/google-protobuf-version-issue-error-updating-to-3-2-2-from-3-2-1/312118)._