So while trying to get a portable/automated Docker deployment up I’m spinning up my old system-installed Discourse instance temporarily but I’ve hit some issues and it won’t work properly again (it did for a long time before I switched to using Traefik a few months ago - because Discourse was using a unix:// socket which didn’t make sense in the context of a Traefik container and didn’t know I could switch Discourse to use ports instead.
Anyway, I dug through the forum and discovered I can use
expose: - "3000" - "2222"
And I also added labels for Traefik:
labels: traefik.frontend.rule: "Host:forum.southcla.ws" traefik.docker.network: "gateway" traefik.port: "3000"
And those are working great, Traefik can now talk to my Discourse container!
But, when I loaded up the page, it was pure white and the console contained a ton of 404s. Very strange, because it worked fine literally 3 days earlier when I shut off Traefik and accessed it via Caddy (a reverse proxy from domain.com -> unix://xyz).
So I’m not really sure how just changing the network interface method caused this - couldn’t find anything else in the docs or on the forum.
I poked around the forum, found a thread that mentioned using
stable instead of
testspassed so I tried that, now I just get a 500 error instead of a blank page.
On both of these tests, the logs output the same thing:
rsyslogd: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ] rsyslogd: imklog: cannot open kernel log (/proc/kmsg): Operation not permitted. rsyslogd: activation of module imklog failed [v8.16.0 try http://www.rsyslog.com/e/2145 ] rsyslogd: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.16.0 try http://www.rsyslog.com/e/2039 ] supervisor pid: 41 unicorn pid: 82
Which I have no idea what it means! I assumed the container should Just Work™ because that’s the problem that docker is meant to solve but it seems I’m getting different results after just a couple of days and one config change.
I would change back but that means turning off Traefik and shutting down every other web service I’m hosting - I basically need to run Discourse on a port, not a unix:// socket.
Would love to get my forum back online after months of downtime, aside from all these issues, Discourse is by far my favourite forum software available, thanks!