Hey,
after a deploy yesterday, suddenly one of our services (a Sidekiq worker) fails to deploy because the process exits with code 0 all the time. Rolling back the code changes doesn’t help. Other services with the identical container image but different CMD args have no issues (even another Sidekiq worker processing a different queue is deploying just fine).
What helped was not executing Sidekiq via sh -c (switching CMD args from sh -c bundle exec sidekiq -e $RAILS_ENV to bundle exec sidekiq -e $RAILS_ENV). We’d like to understand the reason though because the former worked before. Did something change on your end?
