# GLIBC\_2.29 error when not using cached docker image

**URL:** <https://discuss.circleci.com/t/glibc-2-29-error-when-not-using-cached-docker-image/41880>\
**Category:** Build Environment\
**Tags:** docker\
**Created:** [November 10, 2021, 1:41pm UTC](https://discuss.circleci.com/t/glibc-2-29-error-when-not-using-cached-docker-image/41880 "2021-11-10T13:41:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![key88sf](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/key88sf/32/9271_2.png) [@key88sf](https://discuss.circleci.com/u/key88sf)\
**Post date:** [November 10, 2021, 1:41pm UTC](https://discuss.circleci.com/t/glibc-2-29-error-when-not-using-cached-docker-image/41880/1 "2021-11-10T13:41:18Z")

</div>

Starting on Nov 8th, our builds which compile assets for a Rails project started sporadically failing with this error:

```auto
LoadError: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found

```

No code changes were done on our end. The only thing we can point to for the failures is that it looks like if the cached docker image is not found, it will download it and then we get the error. So if we see this message, it will error:  
`image cache not found on this host, downloading circleci/ruby:2.6.3-stretch-node-browsers`

On builds where the cached docker image is found, it seems to work. However, we confirmed that the SHA of both the cached image and the newly downloaded image are the same!

Any ideas? Again, this only started on Nov 8, 2021.