Hello, I am facing an issue: I am unable to rebuild Discourse using the command “./launcher rebuild app”, and when I run the command “docker ps”, no Discourse container is visible. However, I can still access Discourse via the web without any problem. How is this possible? Here are the errors that I encounter when I run the command “./launcher rebuild app”: : docker: Error response from daemon: error while creating mount source path '/var/discourse/shared/standalone': mkdir /var/discourse: read-only file system. bootstrap failed with exit code 125 ** 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. f15514ef40f8a25134126ee1c0c7771c60081ce8a8f2f6384be73cbbca7a3d12 Result the command docker ps : CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES I want to rebuild Discourse to use it with HTTPS this time, and with Let’s Encrypt. Thanks for help

I resolve the probleme with new install server discourse. Before in old server i save data with administration setting and after i restore data in new server. In new server Discourse container is visible now CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES e42d24042375 local_discourse/app "/sbin/boot" 25 minutes ago Up 25 minutes 0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp app

You need to look for errors way back in the logs or console, maybe you had made a incomplete change for the https? Start and revert it to get it going again.

[image] Hassan Mahmood: read-only file system This is one problem. [image] Hassan Mahmood: when I run the command “docker ps”, no Discourse container is visible. However, I can still access Discourse via the web without any problem. How is this possible? Maybe you’re not root? Maybe you’re on the wrong server?

In the normal mode of launcher.sh docker containers are stopped before they are rebuild, so if the build fails they might miss (not sure if laufender tries to start the old ones as a recovery step?). (I think there is a reduced-downtime mode - which only stops them after the rebuild, not sure why this is not the default since it would help against such corruptions) That would not explain why you still see discourse however discourse runs offline for quite some time very sneakily :slight_smile:

Hello, Sorry for late answer I follow instruction with Set up HTTPS support with Let's Encrypt for https. Before i follow instruction with vidéo (https://www.youtube.com/watch?v=EaUIsIYivE8) for install discourse http (not https) and I had posted a comment on how to install Discourse on Ubuntu using HTTP in forum in december 23. (Issue with installation in an Ubuntu 22.04 VM - #11 by mrhassan60) I use command with root user docker ps and i use server where discourse application is. i use command ./discourse-doctor and i have other error also with error 125 : Discourse version at forum.dauphine.media: NOT FOUND Discourse version at localhost: NOT FOUND Unable to find image 'local_discourse/app:latest' locally docker: Error response from daemon: pull access denied for local_discourse/app, repository does not exist or may require 'docker login': denied: requested access to the resource is denied. Discourse version at forum.dauphine.media: NOT FOUND Discourse version at localhost: NOT FOUND and discourse turn since 2 months. sorry for my bad english.

[image] Hassan Mahmood: local_discourse/app, repository does not exist or may require 'docker login': denied: requested access to the resource is denied. I’ve seen one other report like this. Are you somewhere that access to docker might be blocked?

i use command docker run hello-world if docker works and the command works. Hello from Docker! This message shows that your installation appears to be working correctly.

try use “docker pull” instead.

I used this command docker pull local_discourse/app:latest but i have same message : Error response from daemon: pull access denied for local_discourse/app, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

./launcher rebuild app error bootstrap failed with exit code 125

Product Support Self-hosting

pfaffman (Jay Pfaffman) March 15, 2024, 6:30pm 3

This is one problem.

Maybe you’re not root?

Maybe you’re on the wrong server?

Topic		Replies	Views
Failed to Bootstrap [read-only filesystem] Product Support	12	2414	April 17, 2019
Can't get discourse working again Self-hosting	8	2009	February 16, 2020
FAILED TO BOOTSTRAP on setup Self-hosting	11	3296	January 6, 2021
Rebuild App - Error Self-hosting	7	1131	December 21, 2020
Unable to rebuild discourse Product Support	9	420	December 24, 2024

./launcher rebuild app error bootstrap failed with exit code 125

Related topics