# Error after update Docker Manager to ea174f7e

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

<div class="post-metadata">

**Author:** ![xkhalid](https://avatars.discourse-cdn.com/v4/letter/x/3ab097/32.png) [@xkhalid](https://meta.discourse.org/u/xkhalid)\
**Post date:** [October 23, 2024, 6:18pm UTC](https://meta.discourse.org/t/error-after-update-docker-manager-to-ea174f7e/332415/1 "2024-10-23T18:18:58Z")

</div>

Dear Gents,

I have a self-hosted Discourse instance, and when I attempted to update the Docker Manager to version ea174f7e, I encountered the following error:

```plaintext
Docker Manager: FAILED TO UPGRADE
#<ActiveRecord::StatementInvalid:"PG::UndefinedColumn: ERROR: column users.password_hash does not exist\nLINE 1: ...ed_at\", \"users\".\"name\", \"users\".\"last_posted_at\", \"users\".\"p...\n ^\n">
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-3.3.1/lib/patches/db/pg.rb:69:in `exec_params'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-3.3.1/lib/patches/db/pg.rb:69:in `exec_params'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/postgresql_adapter.rb:894:in `block (2 levels) in exec_no_cache'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/abstract_adapter.rb:1027:in `block in with_raw_connection'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-7.1.4/lib/active_support/concurrency/null_lock.rb:9:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/abstract_adapter.rb:999:in `with_raw_connection'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/postgresql_adapter.rb:893:in `block in exec_no_cache'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-7.1.4/lib/active_support/notifications/instrumenter.rb:58:in `instrument'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/abstract_adapter.rb:1142:in `log'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/postgresql_adapter.rb:892:in `exec_no_cache'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/postgresql_adapter.rb:872:in `execute_and_clear'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/postgresql/database_statements.rb:64:in `internal_exec_query'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:630:in `select'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:71:in `select_all'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/abstract/query_cache.rb:115:in `select_all'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/querying.rb:62:in `_query_by_sql'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/querying.rb:51:in `find_by_sql'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/statement_cache.rb:150:in `execute'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/core.rb:431:in `cached_find_by'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/core.rb:252:in `find'
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:261:in `log_version_upgrade'
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:136:in `upgrade'
/var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:19:in `block in <main>'
/var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:6:in `fork'
/var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:6:in `<main>'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.1.4/lib/rails/commands/runner/runner_command.rb:41:in `load'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.1.4/lib/rails/commands/runner/runner_command.rb:41:in `block in perform'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-7.1.4/lib/active_support/execution_wrapper.rb:92:in `wrap'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.1.4/lib/rails/commands/runner/runner_command.rb:40:in `perform'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/thor-1.3.2/lib/thor/command.rb:28:in `run'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/thor-1.3.2/lib/thor/invocation.rb:127:in `invoke_command'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.1.4/lib/rails/command/base.rb:178:in `invoke_command'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/thor-1.3.2/lib/thor.rb:538:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.1.4/lib/rails/command/base.rb:73:in `perform'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.1.4/lib/rails/command.rb:71:in `block in invoke'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.1.4/lib/rails/command.rb:149:in `with_argv'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.1.4/lib/rails/command.rb:69:in `invoke'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.1.4/lib/rails/commands.rb:18:in `<main>'
/usr/local/lib/ruby/3.3.0/bundled_gems.rb:74:in `require'
/usr/local/lib/ruby/3.3.0/bundled_gems.rb:74:in `block (2 levels) in replace_require'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/bootsnap-1.18.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
bin/rails:18:in `<main>'

```

However, on the update page, it looks like everything is fine:

 ![image](https://global.discourse-cdn.com/meta/original/4X/f/0/a/f0a3b640218e76ed8a2270e66ee753ecad5f2161.png)

So, is there anything else I need to do?

Thanks !

---

<div class="post-metadata">

**Author:** ![ajtowns](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ajtowns/32/267792_2.png) [@ajtowns](https://meta.discourse.org/u/ajtowns)\
**Post date:** [October 25, 2024, 6:21am UTC](https://meta.discourse.org/t/error-after-update-docker-manager-to-ea174f7e/332415/2 "2024-10-25T06:21:52Z")

</div>

I got the same error with the update progress bar aborted maybe 90%, 95% of the way through. Everything was reported as up to date afterwards, and then later updating Discourse to a new commit seemed to work fine.

---

<div class="post-metadata">

**Author:** ![otseng](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/otseng/32/339935_2.png) [@otseng](https://meta.discourse.org/u/otseng)\
**Post date:** [October 26, 2024, 3:21pm UTC](https://meta.discourse.org/t/error-after-update-docker-manager-to-ea174f7e/332415/3 "2024-10-26T15:21:39Z")

</div>

I had the same error. But after running the update again, it seemed to have upgraded correctly.

---

<div class="post-metadata">

**Author:** ![xkhalid](https://avatars.discourse-cdn.com/v4/letter/x/3ab097/32.png) [@xkhalid](https://meta.discourse.org/u/xkhalid)\
**Post date:** [October 26, 2024, 8:55pm UTC](https://meta.discourse.org/t/error-after-update-docker-manager-to-ea174f7e/332415/4 "2024-10-26T20:55:25Z")

</div>

**CC: @sam @ella**

Any help or suggestions regarding the error after updating Docker Manager? Everything is working fine for me now, but I’m worried that the next update might cause something to go wrong.

---

<div class="post-metadata">

**Author:** ![ella](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ella/32/260722_2.png) [@ella](https://meta.discourse.org/u/ella)\
**Post date:** [October 28, 2024, 4:43pm UTC](https://meta.discourse.org/t/error-after-update-docker-manager-to-ea174f7e/332415/7 "2024-10-28T16:43:45Z")

</div>

Thanks for reporting! We’re taking a look.

---

<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:** [October 28, 2024, 5:03pm UTC](https://meta.discourse.org/t/error-after-update-docker-manager-to-ea174f7e/332415/9 "2024-10-28T17:03:50Z")

</div>

The error is happening while docker\_manager attempts to record the upgrade in the staff-action-log. This PR should get things sorted:

[https://github.com/discourse/docker\_manager/pull/247](https://github.com/discourse/docker_manager/pull/247)

---

<div class="post-metadata">

**Author:** ![xkhalid](https://avatars.discourse-cdn.com/v4/letter/x/3ab097/32.png) [@xkhalid](https://meta.discourse.org/u/xkhalid)\
**Post date:** [October 29, 2024, 7:35pm UTC](https://meta.discourse.org/t/error-after-update-docker-manager-to-ea174f7e/332415/10 "2024-10-29T19:35:58Z")

</div>

Thank you @david 😀

 ![image](https://global.discourse-cdn.com/meta/original/4X/9/3/d/93d5a5cc562d7367cba51518993710b9e4373549.png)

---

<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:** [November 28, 2024, 7:36pm UTC](https://meta.discourse.org/t/error-after-update-docker-manager-to-ea174f7e/332415/11 "2024-11-28T19:36:45Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.