# Docker Manager를 ea174f7e로 업데이트한 후 오류 발생

**URL:** <https://meta.discourse.org/t/error-after-update-docker-manager-to-ea174f7e/332415>\
**Category:** Product Support\
**Created:** [10월 23, 2024, 6:18오후 UTC](https://meta.discourse.org/t/error-after-update-docker-manager-to-ea174f7e/332415 "2024-10-23T18:18:58Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [10월 28, 2024, 5:03오후 UTC](https://meta.discourse.org/t/error-after-update-docker-manager-to-ea174f7e/332415/9 "2024-10-28T17:03:50Z")

</div>

오류는 docker\_manager가 업그레이드를 staff-action-log에 기록하려고 할 때 발생하고 있습니다. 이 PR을 통해 문제를 해결할 수 있을 것입니다:

> <https://github.com/discourse/docker_manager/pull/247>
>
> The upgrade process was triggering the database migrations, and then calling \`Us…er.find()\`. This is problematic because the \`users\` table may have been changed by the migrations, and accessing it with the 'old code' will raise an exception.
> 
> This commit tweaks the Upgrader so that it loads the user object into memory \*\*before\*\* running database migrations.

---

_[View the full topic](https://meta.discourse.org/t/error-after-update-docker-manager-to-ea174f7e/332415)._