Josiah_Toppin encountered a bootstrap failure when upgrading from Discourse 1.6.0.beta 7 to beta 8, specifically during asset precompilation, which failed with exit code 137. watchmanmonitor suggested checking the Docker version, noting they successfully upgraded after updating Docker from 1.9.1 to 1.11.2. Steven linked to a meta thread indicating the issue may relate to Docker image version 1.3.3 and provided upgrade guidance. Josiah_Toppin confirmed the fix: updating Docker resolved the issue, but noted a system reboot was also required to clear cache and ensure success. In a follow-up, Josiah_Toppin clarified that the Docker update had already been performed during a prior beta upgrade, though it was still necessary to resolve the current issue.
Coming from 1.6.0.beta 7 to beta 8 today. I don’t have time to delve into it too much right now, but here is the error that is thrown - running ./launcher rebuild app
FAILED
Pups::ExecError: cd /var/www/discourse && su discourse -c ‘bundle exec rake assets:precompile’ failed with return #<Process::Status: pid 296 exit 137>
Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn’
exec failed with the params {“cd”=>“$home”, “hook”=>“bundle_exec”, “cmd”=>[“su discourse -c ‘bundle install --deployment --verbose --without test --without development’”, “su discourse -c ‘bundle exec rake db:migrate’”, “su discourse -c ‘bundle exec rake assets:precompile’”]}
0ab4149a5803934ef38dd9009f53670dcc5d48b3839ed83feefcf719a3330d51
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one
I updated my 4 discourse to beta 8 yesterday with no real problems, though I did update one of mine from docker 1.9.1 to 1.11.2 before updating. What version of docker are you on? Would you paste the full output into a gist?