I am an Engineering Physics graduate from IIT Guwahati, but merely not restricted to Physics itself. In the past few years, I involved in many Cybersecurity blogging and now on Open-source.
Here the ruby version was 2.7.2, It didn't failed.
----------> Releasing leewardslope...
----------> Checking for predeploy task
No predeploy task found, skipping
---------------> Checking for release task
---------------> Executing release task from Procfile: ./release-tasks.sh
=====> Start of leewardslope release task (69c4b09c5) output
+ [[ '' = \b\l\o\c\k\e\d ]]
+ STATEMENT_TIMEOUT=4500000
+ bundle exec rails app_initializer:setup
== Preparing database ==
== Performing setup tasks ==
== Updating Data ==
== Bust Caches ==
+ bundle exec rake fastly:update_configs
+ bundle exec rails runner 'puts '\''app load success'\'''
/app/app/services/edge_cache/bust/nginx.rb:44: warning: already initialized constant Net::HTTP::Purge::METHOD
/app/vendor/bundle/ruby/2.7.0/gems/fastly-3.0.2/lib/fastly/client.rb:166: warning: previous definition of METHOD was here
/app/app/services/edge_cache/bust/nginx.rb:45: warning: already initialized constant Net::HTTP::Purge::REQUEST_HAS_BODY
/app/vendor/bundle/ruby/2.7.0/gems/fastly-3.0.2/lib/fastly/client.rb:167: warning: previous definition of REQUEST_HAS_BODY was here
/app/app/services/edge_cache/bust/nginx.rb:46: warning: already initialized constant Net::HTTP::Purge::RESPONSE_HAS_BODY
/app/vendor/bundle/ruby/2.7.0/gems/fastly-3.0.2/lib/fastly/client.rb:168: warning: previous definition of RESPONSE_HAS_BODY was here
app load success
=====> End of leewardslope release task (69c4b09c5) output
---------------> App Procfile file found
=====> Processing deployment checks
No CHECKS file found. Simple container checks will be performed.
For more efficient zero downtime deployments, create a CHECKS file. See https://dokku.com/docs/deployment/zero-downtime-deploys/ for examples
---------------> Deploying leewardslope...
WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
---------------> Attempting pre-flight checks (sidekiq_worker.1)
Waiting for 10 seconds ...
Default container check successful!
Scheduling old container shutdown for sidekiq_worker.1 in 60 seconds
WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
---------------> Attempting pre-flight checks (web.1)
Waiting for 10 seconds ...
Default container check successful!
Scheduling old container shutdown for web.1 in 60 seconds
---------------> Running post-deploy
---------------> Configuring test.leewardslope.com...(using built-in template)
---------------> Creating https nginx.conf
Enabling HSTS
Reloading nginx
---------------> Renaming containers
Found previous container(s) (b69dd1fc5aeb) named leewardslope.sidekiq_worker.1
Renaming container (b69dd1fc5aeb) leewardslope.sidekiq_worker.1 to leewardslope.sidekiq_worker.1.1630646338
Renaming container (bd6a2cbb3bf8) sleepy_wing to leewardslope.sidekiq_worker.1
Found previous container(s) (4eaea067c9f2) named leewardslope.web.1
Renaming container (4eaea067c9f2) leewardslope.web.1 to leewardslope.web.1.1630646339
Renaming container (d981b4adfe33) nice_dijkstra to leewardslope.web.1
---------------> Checking for postdeploy task
No postdeploy task found, skipping
---------------> Shutting down old containers in 60 seconds
=====> Application deployed:
http://test.leewardslope.com
https://test.leewardslope.com
For further actions, you may consider blocking this person and/or reporting abuse
Fresh installation with Old repository.
Here the ruby version was 2.7.2, It didn't failed.