עדכון Docker ואז putty

תמיכה התקנה

סיכום מבוסס בינה מלאכותית

The discussion revolves around issues encountered during a Docker update and subsequent attempts to rebuild a Discourse instance using putty. anon48433008 reports a new error after updating Docker, which Falco clarifies is a known issue that occurs occasionally and is documented in the latest release notes. Martin_Anonym faces a similar problem with a postgres error during rebuild, despite trying various solutions including reboots. codinghorror identifies two issues: a detached HEAD state in Git and potential PostgreSQL problems, questioning whether the installation followed the standard method. Martin_Anonym confirms the standard installation but resolves the issue by stopping the container and disabling autostart before rebooting and running the commands again.

1

I keep up with updates and when I did the docker today then went to do the rest I got this

image
image628×245 9.68 KB

which is new to me,

all went good with putty but wanted to post and ask, no worries?

2

That is necessary a couple of times a year. We also made a note about it on the latest release topic.

3

:facepalm:

which I’ve neglected to read this time

Thank you for the answer

4

Sorry I got the same message (which i knew from some months ago) so no problem on this, but this time when I run:

cd /var/discourse
git pull
./launcher rebuild app

I get this Error:

So I red this thread:

(which is closed so I cant reply)

and I am referring to:

I have rebootet the server from:

  • CLI
  • ACPI-Command
  • Force Shutdown (disconnect Power)

But everytime I boot the machine back up and try to run

cd /var/discourse
git pull
./launcher rebuild app

It triggers the very same Error.
If you think I should open a new Thread for this please just move my Post into a new one. I dont want to spam the board with new threads, but apparently can not reply on the other closed Thread and its “solution” did not work for me

EDIT:

my Setup is

  • runs in Docker
  • installed like recommended
  • Debian 10 (latest)
5

You have two problems, first, with Git

You are in 'detached HEAD' state. You can look around, make experimental

Somehow you have made local code changes that conflict.

xec failed with the params "socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1"

It also looks like postgres is having problems on your instance. Did you install using the standard method, the only method we support?

6

Yes like stated here:

But I already managed to solve the problem.

I stopped the container and run the commands again after a reboot.
Notice that I had to turn off autostart for this container. Dunno why but then it worked.