After having a full disk and not managing to move my images, I decided to delete everything, start a new discourse container and use the backup. I deleted /var/discourse and did a docker system prune -a Then I followed the official guide. But… something is wrong: ./launcher rebuild app x86_64 ar…

Did you stop the old container? docker stop app docker rm app

Well, while that would totally be like me, this time it’s not that simple: # sudo -s # cd /var/discourse/ # docker stop app Error response from daemon: No such container: app # docker rm app Error: No such container: app I think the problem might be that I moved everything from the old default lo…

/var/run/postgresql does not exist. I have no idea why this isn’t working anymore. :cry:

What does your app.yml look like?

$# cat app.yml ## this is the all-in-one, standalone Discourse Docker container template ## ## After making changes to this file, you MUST rebuild ## /var/discourse/launcher rebuild app ## ## BE *VERY* CAREFUL WHEN EDITING! ## YAML FILES ARE SUPER SUPER SENSITIVE TO MISTAKES IN WHITESPACE OR ALIGNME…

[Bild] Karsten: This worked till I changed daemon.json: Then that’s your problem. This is a docker issue, not a Discourse issue. My guess is that it has to do with permissions or the drive not being there somehow.

I assume so. But all the other services in dockers work as intended! It’s just discourse that won’t try to access the new data-root. That’s why I hoped to find a solution here.

You might try changing the volumes to be somewhere other than /var/discourse/shared/standalone I presume that you already deleted /var/discourse/shared?

I did a rm -R /var/discourse and followed the official install guide as one of the first steps. [Bild] Jay Pfaffman: You might try changing the volumes to be somewhere other than /var/discourse/shared/standalone I’ll try that!

[Bild] Jay Pfaffman: You might try changing the volumes to be somewhere other than /var/discourse/shared/standalone I tried both a directoy on the same disk as well als a folder in “data-root” - nothing changed. Why does the rm command fail? I assume this is still the file system of the oper…

Rm: kann '/var/run/postgresql' nicht entfernen: Verzeichnis nicht leer

Unterstützung Installation

Blechpirat (Karsten) 6. März 2023 um 15:35 13

Vielen, vielen Dank trotzdem!

Thema		Antworten	Aufrufe
Welcome to nginx! page before rebuild, site won't rebuild now Support	20	432	13. Juni 2025
Failed to install Discourse in Ubuntu14.04: docker problems Self-hosting docker	19	8444	25. Januar 2015
Building bootstrap error Self-hosting	45	2259	20. November 2022
Data directory "/shared/postgres_data" has group or world access Self-hosting	4	5052	18. April 2017
Discourse Bad Gateway after reboot Self-hosting	15	2198	2. Juli 2020

Rm: kann '/var/run/postgresql' nicht entfernen: Verzeichnis nicht leer

Verwandte Themen