# Falha na atualização - não é possível reinstalar

**URL:** <https://meta.discourse.org/t/upgrade-failed-unable-to-reinstall/414060>\
**Category:** Self-hosting\
**Created:** [Outubro 6, 2026, 6:16pm UTC](https://meta.discourse.org/t/upgrade-failed-unable-to-reinstall/414060 "2026-10-06T18:16:55Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![embusa](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/embusa/32/579859_2.png) [@embusa](https://meta.discourse.org/u/embusa)\
**Post date:** [Outubro 6, 2026, 6:16pm UTC](https://meta.discourse.org/t/upgrade-failed-unable-to-reinstall/414060/1 "2026-10-06T18:16:55Z")

</div>

Estou tentando me recuperar de uma atualização que deu errado, quando um problema de disco fez com que o container crashesse. Agora, quando tento executar `./discourse-doctor` ou `./launcher rebuild..`, ou mesmo uma nova instalação, ele falha aqui. Parece que pode haver um problema com a imagem do container?

```plaintext
2.0.20260915-0028: Pulling from discourse/base
Digest: sha256:5028d077b061225507e7093fda1ff5bdc64d483b5c0397776f9a52c50008cd9b
Status: Downloaded newer image for discourse/base:2.0.20260915-0028
docker.io/discourse/base:2.0.20260915-0028
Ensuring launcher is up to date
Launcher is up-to-date
2.0.20260915-0028: Pulling from discourse/base
Digest: sha256:5028d077b061225507e7093fda1ff5bdc64d483b5c0397776f9a52c50008cd9b
Status: Image is up to date for discourse/base:2.0.20260915-0028
docker.io/discourse/base:2.0.20260915-0028
/usr/local/lib/ruby/3.4.0/rubygems/basic_specification.rb:42:in 'singleton class': uninitialized constant Gem::Deprecate (NameError)
        from /usr/local/lib/ruby/3.4.0/rubygems/basic_specification.rb:41:in '<class:BasicSpecification>'
        from /usr/local/lib/ruby/3.4.0/rubygems/basic_specification.rb:7:in '<top (required)>'
        from /usr/local/lib/ruby/3.4.0/rubygems/specification.rb:11:in 'Kernel#require_relative'
        from /usr/local/lib/ruby/3.4.0/rubygems/specification.rb:11:in '<top (required)>'
        from /usr/local/lib/ruby/3.4.0/rubygems.rb:1372:in 'Kernel#require_relative'
        from /usr/local/lib/ruby/3.4.0/rubygems.rb:1372:in '<top (required)>'
        from <internal:gem_prelude>:2:in 'Kernel#require'
        from <internal:gem_prelude>:2:in '<internal:gem_prelude>'
cd /pups && git pull && git checkout v1.0.3 && /pups/bin/pups --stdin
git: error while loading shared libraries: /lib/x86_64-linux-gnu/libpcre2-8.so.0: file too short
bootstrap failed with exit code 127
**FAILED TO BOOTSTRAP** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
078e7b891ce7ebf3454c59f2c0ab346d023d16539b4d8b4b33bf268f5109753b

```

---

<div class="post-metadata">

**Author:** ![Full-Stack\_Engineer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/full-stack_engineer/32/579858_2.png) [@Full-Stack\_Engineer](https://meta.discourse.org/u/Full-Stack_Engineer)\
**Post date:** [Outubro 6, 2026, 6:22pm UTC](https://meta.discourse.org/t/upgrade-failed-unable-to-reinstall/414060/2 "2026-10-06T18:22:49Z")

</div>

Olá @embusa, obrigado por entrar em contato.

Analisei o erro. O problema parece estar no nível do ambiente host/Docker, e não na própria aplicação Discourse. O erro principal é `libpcre2-8.so.0: file too short`, o que sugere fortemente uma biblioteca de sistema corrompida após o problema com o disco.

---

<div class="post-metadata">

**Author:** ![embusa](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/embusa/32/579859_2.png) [@embusa](https://meta.discourse.org/u/embusa)\
**Post date:** [Outubro 6, 2026, 6:24pm UTC](https://meta.discourse.org/t/upgrade-failed-unable-to-reinstall/414060/3 "2026-10-06T18:24:29Z")

</div>

Ah! Faz sentido, considerando o problema do disco - eu estava pensando que vinha do contêiner. Vou tentar em um sistema novo. Estava olhando para isso há tanto tempo que não percebi. Eu estava focado no erro do ruby no início.

---

<div class="post-metadata">

**Author:** ![Full-Stack\_Engineer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/full-stack_engineer/32/579858_2.png) [@Full-Stack\_Engineer](https://meta.discourse.org/u/Full-Stack_Engineer)\
**Post date:** [Outubro 6, 2026, 6:27pm UTC](https://meta.discourse.org/t/upgrade-failed-unable-to-reinstall/414060/4 "2026-10-06T18:27:15Z")

</div>

> [@embusa](#):
>
> Ah! Faz sentido considerando o problema do disco - eu estava pensando que vinha do container. Vou tentar em um sistema novo. Estava olhando para isso há tanto tempo que não percebi. Eu estava focado no erro do ruby no início.

Sim, exatamente. O erro do Ruby era apenas uma distração (o erro do `libpcre2` aponta para o problema do disco/sistema). Testar em um sistema limpo deve confirmar isso rapidamente.

Mande uma DM para a discussão. Obrigado

---

<div class="post-metadata">

**Author:** ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)\
**Post date:** [Outubro 6, 2026, 6:28pm UTC](https://meta.discourse.org/t/upgrade-failed-unable-to-reinstall/414060/5 "2026-10-06T18:28:45Z")

</div>

Eu tentaria

```plaintext
cd /var/discourse
./launcher cleanup
docker image rm discourse/base:2.0.20260915-0028
./launcher rebuild app

```

---

<div class="post-metadata">

**Author:** ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)\
**Post date:** [Outubro 6, 2026, 6:32pm UTC](https://meta.discourse.org/t/upgrade-failed-unable-to-reinstall/414060/6 "2026-10-06T18:32:14Z")

</div>

> [@Full-Stack\_Engineer](#):
>
> Obrigado por entrar em contato.

Por que você está agradecendo a eles?