Docker update then putty

[Full30 (Robert)]

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

which is new to me,

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

[Falco]

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

[Full30 (Robert)]

@Falco

note about it on the latest release topic

which I’ve neglected to read this time

Thank you for the answer

[Martin_Anonym]

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:

Discourse Error - Pastebin.com

So I red this thread:

[Solved]Bootstrap fails, Postgres already running

Hi, I’m attempting to install Discourse, but am failing so far. It appears that bootstrapping doesn’t want to… bootstrap? Anyhow, I read a couple of other threads about it and tried “./launcher rebuild app”, which gave the following output: WARNING: No memory limit support WARNING: No swap limit support Updating discourse docker Already up-to-date. Calculated ENV: -e LANG=en_US.UTF-8 -e RAILS_ENV=production -e UNICORN_WORKERS=3 -e UNICORN_SIDEKIQS=1 -e RUBY_GC_MALLOC_LIMIT=40000000 -e RUBY_HE…

(which is closed so I cant reply)

and I am referring to:

[Solved]Bootstrap fails, Postgres already running

Reboot. It should fix it.

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)

[codinghorror (Jeff Atwood)]

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?

[Martin_Anonym]

@codinghorror

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

Yes like stated here:

@Martin_Anonym

installed like recommended

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.