# Docker update error

**URL:** <https://meta.discourse.org/t/docker-update-error/302140>\
**Category:** Self-hosting\
**Tags:** maxmind\
**Created:** [April 2, 2024, 11:44pm UTC](https://meta.discourse.org/t/docker-update-error/302140 "2024-04-02T23:44:48Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [April 3, 2024, 2:09pm UTC](https://meta.discourse.org/t/docker-update-error/302140/6 "2024-04-03T14:09:47Z")

</div>

I would say that anytime a problem with maxmind causes a rebuild to fail, it’s a bug. I’m pretty sure that it’s always been possible for issues with Maxmind to cause a build to fail.

So I don’t know whether it’s the same bug, or multiple bugs.

I think the solution could be as simple as adding a `rescue` (somewhere in [discourse/lib/discourse\_ip\_info.rb at 3d49df2953fd14ae75eeab7621ad687f1b06f504 · pfaffman/discourse · GitHub](https://github.com/pfaffman/discourse/blob/3d49df2953fd14ae75eeab7621ad687f1b06f504/lib/discourse_ip_info.rb#L28-L75)) to allow life to go on without Maxmind, regardless of whether a key, valid or invalid, was provided.

---

_[View the full topic](https://meta.discourse.org/t/docker-update-error/302140)._