FAILED (./launcher rebuild app)

installation
1 
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle install --deployment --retry 3 --jobs 4 --verbose --without test development' failed with return #<Process::Status: pid 399 exit 5>
Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle install --deployment --retry 3 --jobs 4 --verbose --without test development'"]}
ca462b1f91a2a26fbb18db9569c96004022ada36de8827030016cd112d3da145
** 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.

2020-07-30_133205
2020-07-30_1332051612×658 44.5 KB

2

If you have plugins, I’d try removing all plugins then rebuild, see if that fixes it. Then add them back one by one.

1 Like
3

disabled all plugins
except - docker_manager.git

4

Which Git revision should this container use? (default: tests-passed)

version: ‘3d050bdaa31633a954758894629c0eb9fea537d0’

5

is there more to that error log ??

maybe check the logs @ /var/discourse/shared/standalone/log/

6

the .yml files are sensitive. You might have used a tab instead of two spaces somewhere.
Paste your file in this tool http://www.yamllint.com/ to find the culprit.

2 Likes
7

everything worked fine until today did not update docker manager *.yml files did not change

8

did you retry ./discourse-doctor ?

1 Like
9

Looks related to that :
https://github.com/discourse/discourse/commit/fe71c43c57c0248a8264245cb6ff0dc114da335a

10

yes ./discourse-doctor got the same error messagesstrong text

2020-07-30_134446
2020-07-30_1344461693×343 16.5 KB

11

something is already using your https port

12

what is your platform/environment/host ? There is also a make error in your first screenshot :face_with_raised_eyebrow:

13

replaced the branch version tests-passed 3d050bdaa31633a954758894629c0eb9fea537d0 to 5e2e374c72f75d71c63c78a57edddde895b37e2a

it worked,

but I want to stay on > 3d050bdaa31633a954758894629c0eb9fea537d0

14

We don’t really test our base image with every single point in time specific commit, so there is no guarantee it will ever work.

It will always work with tests-passed branch, and that’s it. For everything else you are treading your own path, bugs and everything.

3 Likes