The user, bobdude, is trying to update their Discourse installation using the command ./launcher rebuild app, but is encountering issues due to being inside the Docker container. jomaxro and pfaffman provide assistance, suggesting that bobdude needs to connect to the server via SSH and run the commands from the correct directory. After using the exit command to leave the container, bobdude is able to update their installation successfully. pfaffman clarifies that bobdude had entered the container using ./launcher enter app, which caused the issue.
Upgrades via the web UI are disabled until you run the latest image.
To do so log in to your server using SSH and run:
cd /var/discourse git pull ./launcher rebuild app
I get the above screen when looking to do an update from the dashboard.
My installation seems to be in var/www/discourse
I ran a git pull in the discourse folder but I don’t know how to rebuild the app properly. Tis is a docker install; any directions would be much appreciated thank you.
Can you share the exact commands you’re running, and the output you’re seeing (feel free to redact IP addresses/hostnames if you prefer)? /var/www/discourse sounds like you’re inside the docker container, rather that on your server.
You should be doing something like:
ssh user@forum.example.com
cd /var/discourse
git pull
sudo ./launcher rebuild app
You’re somehow connecting inside the container. You should probably connect to port 22 and maybe you’re connecting to port 2222; older installations had an ssh port exposed for the container.
I’m using Vultr and I just log into my account and open the console window. My command line shows root@vultr-app. is their a way to log out of the app?
I think i’m there I used an exit command now my folder structure looks right. Update is now rebuilding thanks for the help.
Aha! So apparently it leaves the console running and you forgot that you’d entered the container (with ./launcher enter app).
Yes that’s exactly what happened
C Robert Christensen (Bob)