Hi, I have installed Discourse on a Fedora 31 server with the recommended install guide, however used podman instead of docker for running the container. It all went perfectly fine this morning when I initially set it up, however I had troubles getting plain HTTP to my Nginx on the host to work and had to use the SSL certs on both nginx instances. I configured Discourse and all was fine. I later decided to rebuild Discourse with SSL turned off and build it on a non-root user account. Plain HTTP to host worked fine, however I got a white page (title was fine, favicon worked). [Screenshot from 2020-01-11 15-25-29] I checked the directory in the container: root@xena-app:/var/www/discourse# ls public/assets -al total 15640 drwxr-xr-x. 2 discourse discourse 10 Jan 11 13:54 . drwxr-xr-x. 3 discourse discourse 29 Jan 11 13:57 .. -rw-r--r--. 1 discourse discourse 595 Jan 11 13:49 _activate-account-7a1f8d46287194007ee607f79af56217e6e6238e4ca159c5da6974005a1254c5.js -rw-r--r--. 1 discourse discourse 250 Jan 11 13:54 activate-account-7a1f8d46287194007ee607f79af56217e6e6238e4ca159c5da6974005a1254c5.js.br -rw-r--r--. 1 discourse discourse 420 Jan 11 13:54 activate-account-7a1f8d46287194007ee607f79af56217e6e6238e4ca159c5da6974005a1254c5.js.gz -rw-r--r--. 1 discourse discourse 695 Jan 11 13:54 activate-account-7a1f8d46287194007ee607f79af56217e6e6238e4ca159c5da6974005a1254c5.js.map -rw-r--r--. 1 discourse discourse 990519 Jan 11 13:50 _admin-91c2a24a61c0ecd0200db1e808dbadafb9f0f1bb5179acea5b2b7dbd4b4cc5f9.js -rw-r--r--. 1 discourse discourse 83903 Jan 11 13:54 admin-91c2a24a61c0ecd0200db1e808dbadafb9f0f1bb5179acea5b2b7dbd4b4cc5f9.js.br -rw-r--r--. 1 discourse discourse 106465 Jan 11 13:54 admin-91c2a24a61c0ecd0200db1e808dbadafb9f0f1bb5179acea5b2b7dbd4b4cc5f9.js.gz -rw-r--r--. 1 discourse discourse 366446 Jan 11 13:54 admin-91c2a24a61c0ecd0200db1e808dbadafb9f0f1bb5179acea5b2b7dbd4b4cc5f9.js.map drwxr-xr-x. 2 discourse discourse 4096 Jan 11 13:54 admin-login ... The files that were requested are indeed missing, even Nginx says so: 2020/01/11 13:59:49 [error] 60#60: *20 open() "/var/www/discourse/public/assets/plugins/poll-57c9059384e3daeaee3d974c985d85a2b8462bb2629eb0b1834451056d1e1459.js" failed (2: No such file or directory), client: 10.0.2.2, server: _, request: "GET /assets/plugins/poll-57c9059384e3daeaee3d974c985d85a2b8462bb2629eb0b1834451056d1e1459.js HTTP/1.0", host: "idlerpg.xyz", referrer: "https://idlerpg.xyz/" I thought that this would be an issue with my install, because they were here on the old install this morning as root on the host! I have wiped the shared folder and rebuilt as non-root with the same results over and over. Then I tried again, this time as root with identical settings like this morning, and I got the same issues. A non-root install always shows the “Congratulations, you have installed Discourse!” page, but after I finish the install, I get the blank page because the asset files are missing. Is there any way to fix the missing assets?

In case anyone wonders if it really worked this morning, here’s a screenshot from my mobile [Screenshot_20200111-022149] Discourse won’t allow me to use 2 images in one post yet :slight_smile:

Changed this as a bug. I cannot manage to get a version with all assets when building tests-passed. I tried entering the container and doing a rake assets:precompile, but the same assets are still gone

Seems after tons of rebuilds, it magically works now. Weird.

Hi Adriany, welcome to the forum [immagine] Adriany: the recommended install guide, however used podman instead of docker The last I knew, docker is a requirement not an option. Where did you see this newer install guide?

I just replaced docker with podman, works fine. Their command line syntax is compatible

Okay, after some testing, I can now tell that it always shows a blank page after every rebuild. If I run RAILS_ENV=production bin/rake assets:precompile, it always works afterwards. No idea why, it should compile them in a rebuild anyways?

Did you see this topic and this post in particular about podman incompatibility with docker? [immagine] Any interest in Podman? Development I took a shot at this for half an hour or so. Podman is command-compatible but not output-compatible, so launcher gets confused when it tries to parse output. (It’s not hard to tell them apart, docker --version replies with podman version 1.0.5 so this is not a serious impediment.) There is no docker0 network device. The default overlay storage driver in podman is basically the overlay2 implementation and is aliased to it, but the output doesn’t say overlay2 and the output of the docker info c…

Well it indeed works. Podman should not influence which files will be the result of the initial asset precompile.

In the assets compilation phase of the rebuild do you see any backtraces on the output?

We’re here because something doesn’t work. Should and does are different states. You are confidently asserting that Podman is not implicated. It would good to prove that to clearly eliminate it as a factor. AFAIK, you haven’t completed the official install method with Docker to see if that eliminates the problem.

Asset di Discourse mancanti

Assistenza prodotto Installazione

Remah (Just another happy Discourse user) 12 Gennaio 2020, 9:11pm 8

Hai visto questo argomento e in particolare questo post sull’incompatibilità di Podman con Docker?

Argomento		Risposte	Visualizzazioni
404 errors (assets) on Subfolder installation Product Support	24	4032	Giugno 28, 2019
Discourse stopped working all of a sudden Self-hosting	8	511	Luglio 6, 2024
Can't get discourse working again Self-hosting	8	2009	Febbraio 16, 2020
Installation Error when rebuilding with Discourse Official Plugins (Discourse v2.0.3) Self-hosting solved	7	2814	Agosto 16, 2018
Installation fails on my Debian server Self-hosting	24	2701	Marzo 18, 2019

Asset di Discourse mancanti

Argomenti correlati