# Installing Chrome Natively

**URL:** <https://universal-blue.discourse.group/t/installing-chrome-natively/529>\
**Category:** Bluefin\
**Created:** [February 1, 2024, 2:45pm UTC](https://universal-blue.discourse.group/t/installing-chrome-natively/529 "2024-02-01T14:45:43Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![rrenomeron](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/rrenomeron/32/1290_2.png) [@rrenomeron](https://universal-blue.discourse.group/u/rrenomeron)\
**Post date:** [May 25, 2024, 2:29pm UTC](https://universal-blue.discourse.group/t/installing-chrome-natively/529/9 "2024-05-25T14:29:11Z")

</div>

I don’t think there is, unless you go through the trouble to make a custom image, and do all of the installation at build time. I’ve made updating work for me by manually importing the GPG keys and then doing `rpm-ostree install` with the yum repo enabled. If I don’t import the keys ahead of time, Chrome won’t install due to signature failures (see above).

Unfortunately, the reason I have to do that at container build time is because you can’t install the keys while the system is running.

---

_[View the full topic](https://universal-blue.discourse.group/t/installing-chrome-natively/529)._