최근 업그레이드(2025년 5월 7일) 후 앱을 다시 빌드할 수 없음

기여 버그
1

최신 버전으로 discourse를 업데이트하려고 할 때 실패가 발생하고 있습니다. 파일 경로:

/etc/nginx/conf.d/outlets/server/20-https.conf

이 Ubuntu 24.04 가상 인스턴스에 존재하지 않습니다. 또는 아래 오류는 docker 이미지 내의 nginx 설치에 해당 파일이 누락되어 있음을 의미하는 것일 수도 있습니다. pups-1.2.1에 문제가 있는 것으로 보입니다.

도움을 주시면 감사하겠습니다. 제 메인 시스템에서는 nginx를 사용하지 않고 있으며, 대신 다음을 사용 중입니다:

  - "templates/web.socketed.template.yml"

이는 다음 문서에서 권장하는 방법입니다:
https://meta.discourse.org/t/installing-discourse-behind-reverse-proxy-using-recommended-supported-installation/300191

FAILED                                                                                                            
--------------------                                                                                              
Errno::ENOENT: No such file or directory @ rb_sysopen - /etc/nginx/conf.d/outlets/server/20-https.conf            
Location of failure: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups/replace_command.rb:11:in `read'      
replace failed with the params {"filename"=>"/etc/nginx/conf.d/outlets/server/20-https.conf", "from"=>"/listen 443
 ssl;(\\nlisten \\[::\\]:443 ssl;)?/", "to"=>"listen unix:/shared/nginx.https.sock ssl;\nset_real_ip_from unix:;"}
bootstrap failed with exit code 1                                                                                 
** 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.                                                                 
e3176c7debb5ed1c106765e76f5896b83dac3bb21dd3478b2ac043cbcb8032e1
4

I believe there is a bug as:

  - "templates/web.socketed.template.yml"

wants:

10-http.conf
20-https.conf

but the instruction says to comment out the providers:

  #- "templates/web.ssl.template.yml"
  #- "templates/web.letsencrypt.ssl.template.yml"

and if I comment the first file back in, the web.ssl.template.yml deletes 10-http.conf

5

to compound the situation, when I try to avoid the last commit:

7b042d6157

by doing

git reset --hard HEAD^1

The

./launcher rebuild app

does a git pull.

6

I think that if you do a

./launcher bootstrap app

It won’t do the pull. When it’s done you can destroy and start app. You might need to stop app if it’s running now.

8

I was able to get something working by doing:

git reset --hard HEAD^1
git checkout -b mybranch
./launcher rebuild app

so it appears that commit 7b042d6157 is resulting in issues with my setup.

9

I’m getting the same error message here.
Using also Discourse behind reverse proxy.

Got it back up and running using:

git reset --hard HEAD^1
./launcher bootstrap app
./launcher start app
2개의 좋아요
10

Came here with the same issue, tried doing a redeploy to upgrade & install a plugin. Using Discourse behind reverse proxy too.

So, this is a Discourse bug?

1개의 좋아요
11

Hit the same bug here.

2개의 좋아요
12

It looks related to this commit by @nbianca , putting a high priority tag on this, we will start working on a fix very soon.

https://github.com/discourse/discourse_docker/commit/7b042d6157555c886e1cdcf77e8cb67c56ff8333

4개의 좋아요
15

We have reverted the changes for now while we work towards a fix.

https://github.com/discourse/discourse_docker/pull/958

8개의 좋아요
16

Thank you for the report. I have been working on a fix and will be merged soon:

https://github.com/discourse/discourse_docker/pull/959

4개의 좋아요