Bootstraping a fresh container image fails. Some days ago it worked, “nothing changed”, today it fails. Log:
[0:02:27] Still working on: [0:02:27] v8 ________ running 'vpython third_party/depot_tools/update_depot_tools_toggle.py --disable' in '/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/libv8-184.108.40.206/vendor' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/libv8-220.127.116.11/vendor/depot_tools/.cipd_bin/.cipd/pkgs/0/fI6WggdkRyN1r91MnTeApc2_gyTtXfYpueHZVLcaF8gC/vpython: could not resolve options: failed to resolve Python script: stat /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/libv8-18.104.22.168/vendor/third_party/depot_tools/update_depot_tools_toggle.py: no such file or directory Error: Command 'vpython third_party/depot_tools/update_depot_tools_toggle.py --disable' returned non-zero exit status 1 in /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/libv8-22.214.171.124/vendor ... ** 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.
Digging into it: For libv8 there is already a similar problem reported on github, related to a version change in the ruby builder. During bootstraping, an upgrade of builder is performed. I think the problem seems to be related to the version 2.2.15 of bundler (released yesterday). To be honest: I’m not a ruby guy, so maybe the real issue is slightly different.
However, the following workaround worked for me: Change line 148 in templates/web.template.yml from
- gem update bundler
- gem install bundler -v 2.2.14