e9e61d50
November 11, 2018, 6:13pm
2
Take a look at the error message at the very top, you should to update Docker. The version you are currently running is outdated. Although, this may not be your exact issue, it was the first line I noticed.
edit:@zyouchi is having the same issue. @Stephen posted in I got an error after updating my forked install about checking which version is set in /var/discourse/containers/app.yml.
hosna:
fatal: ambiguous argument ‘@’: unknown revision or path not in the working tree. Use ‘–’ to separate paths from revisions, like this: ‘git <command> [<revision>…] – [<file>…]’ fatal: Not a valid object name @ ./launcher: line 701: [: @: unary operator expected ./launcher: line 711: [: fd25bb96333032adaae8c8577a3f780441466dd9: unary operator expected Launcher has diverged source, this is only expected in Dev mode
I also see this error:
hosna:
2018-11-11 17:15:42.875 UTC [81] postgres@postgres ERROR: database “discourse” already exists 2018-11-11 17:15:42.875 UTC [81] postgres@postgres STATEMENT: CREATE DATABASE discourse; createdb: database creation failed: ERROR: database “discourse” already exists I, [2018-11-11T17:15:42.877843 #13 ] INFO – : I, [2018-11-11T17:15:42.878089 #13 ] INFO – : > su postgres -c ‘psql discourse -c “create user discourse;”’ || true 2018-11-11 17:15:43.024 UTC [92] postgres@discourse ERROR: role “discourse” already exists 2018-11-11 17:15:43.024 UTC [92] postgres@discourse STATEMENT: create user discourse; ERROR: role “discourse” already exists
Unfortunately, I do not have a suggestion to help fix this, my bad, jumped the gun.
2 Likes