Falha na compilação no novo host

Instalação
1

Copiei todo o /var/discourse para um novo host. Atualizei o CNAME e o SSL, tudo funcionando bem. Quando tento reconstruir, recebo um problema que não consigo resolver.

 sudo ./launcher rebuild app
I, [2022-03-11T16:50:42.832830 #1]  INFO -- :
I, [2022-03-11T16:50:42.833980 #1]  INFO -- : Replacing pid /run/nginx.pid; with daemon off; in /etc/nginx/nginx.conf
I, [2022-03-11T16:50:42.834524 #1]  INFO -- : Replacing (?m-ix:upstream[^\\}]+\\}) with upstream discourse { server 127.0.0.1:3000; } in /etc/nginx/conf.d/discourse.conf
I, [2022-03-11T16:50:42.834854 #1]  INFO -- : Replacing (?-mix:server_name.+$) with server_name _ ; in /etc/nginx/conf.d/discourse.conf
I, [2022-03-11T16:50:42.835184 #1]  INFO -- : Replacing (?-mix:client_max_body_size.+$) with client_max_body_size $upload_size ; in /etc/nginx/conf.d/discourse.conf
I, [2022-03-11T16:50:42.835501 #1]  INFO -- : Replacing (?-mix:worker_connections.+$) with worker_connections $nginx_worker_connections ; in /etc/nginx/nginx.conf
I, [2022-03-11T16:50:42.835804 #1]  INFO -- : > echo "done configuring web"
I, [2022-03-11T16:50:42.839749 #1]  INFO -- : done configuring web

I, [2022-03-11T16:50:42.840160 #1]  INFO -- : > cd /var/www/discourse && gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,""); print $0 }' Gemfile.lock)
ERROR:  Could not find a valid gem 'bundler' (= 2.3.4), here is why:
          Unable to download data from https://rubygems.org/ - Net::OpenTimeout: execution expired (https://rubygems.org/specs.4.8.gz)
I, [2022-03-11T16:55:43.338723 #1]  INFO -- :
I, [2022-03-11T16:55:43.339140 #1]  INFO -- : Terminating async processes
I, [2022-03-11T16:55:43.339338 #1]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main pid: 42
I, [2022-03-11T16:55:43.339402 #1]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 103
2022-03-11 16:55:43.339 UTC [42] LOG:  received fast shutdown request
103:signal-handler (1647017743) Received SIGTERM scheduling shutdown...
2022-03-11 16:55:43.340 UTC [42] LOG:  aborting any active transactions
2022-03-11 16:55:43.342 UTC [42] LOG:  background worker "logical replication launcher" (PID 51) exited with exit code 1
2022-03-11 16:55:43.346 UTC [46] LOG:  shutting down
2022-03-11 16:55:43.361 UTC [42] LOG:  database system is shut down
103:M 11 Mar 2022 16:55:43.363 # User requested shutdown...
103:M 11 Mar 2022 16:55:43.363 * Saving the final RDB snapshot before exiting.
103:M 11 Mar 2022 16:55:43.433 * DB saved on disk
103:M 11 Mar 2022 16:55:43.434 # Redis is now ready to exit, bye bye...

Um wget do rubygems funciona bem, a conectividade com a internet está boa. Alguma sugestão?

1 curtida
2

Se a conectividade com a internet estiver funcionando no host, você precisará depurar a conectividade com a internet dentro dos contêineres Docker nesse host.

2 curtidas
3

Encontrei meu problema. Tenho o IPv6 ativado no docker, o que parece confundir as coisas.

Tive que desativá-lo e depois recarregar o docker.

{
  "ipv6": false,
  "fixed-cidr-v6": "2001:db8:1::/64"
}

Obrigado pela ajuda!

2 curtidas
4

Mais especificamente: você tinha o IPv6 ativado e configurado para distribuir endereços que não retornarão aos seus contêineres.

Nem todos os aplicativos são escritos para voltar para v4 se a conectividade v6 estiver quebrada.

2 curtidas
5

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