Meet troubles when building Foreman container

Problem:
I buid a foreman container in virtualbox step by step as below:
docker-compose pull
docker-compose run app bundle exec rake db:create db:migrate
docker-compose run app bundle exec rake db:seed permissions:reset password=changeme
docker-compose up

and then there are two lines ouptut continously:
worker_1 | Redis#exists(key) will return an Integer in redis-rb 4.3, if you want to keep the old behavior, use exists? instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. (/home/foreman/vendor/ruby/2.6.0/gems/sidekiq-5.2.8/lib/sidekiq/launcher.rb:105:in block (2 levels) in ❤') orchestrator_1 | Redis#exists(key)will return an Integer in redis-rb 4.3, if you want to keep the old behavior, useexists?instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. (/home/foreman/vendor/ruby/2.6.0/gems/sidekiq-5.2.8/lib/sidekiq/launcher.rb:105:inblock (2 levels) in :heart:’)

docker-compose info as below
docker@default:/docker/foreman$ docker-compose ps
Name Command State Ports
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
foreman_app_1 entrypoint.sh bundle exec … Up (healthy) 127.0.0.1:3000->3000/tcp, 127.0.0.1:5910->5910/tcp, 127.0.0.1:5911->5911/tcp,
127.0.0.1:5912->5912/tcp, 127.0.0.1:5913->5913/tcp, 127.0.0.1:5914->5914/tcp,
127.0.0.1:5915->5915/tcp, 127.0.0.1:5916->5916/tcp, 127.0.0.1:5917->5917/tcp,
127.0.0.1:5918->5918/tcp, 127.0.0.1:5919->5919/tcp, 127.0.0.1:5920->5920/tcp,
127.0.0.1:5921->5921/tcp, 127.0.0.1:5922->5922/tcp, 127.0.0.1:5923->5923/tcp,
127.0.0.1:5924->5924/tcp, 127.0.0.1:5925->5925/tcp, 127.0.0.1:5926->5926/tcp,
127.0.0.1:5927->5927/tcp, 127.0.0.1:5928->5928/tcp, 127.0.0.1:5929->5929/tcp,
127.0.0.1:5930->5930/tcp
foreman_db_1 docker-entrypoint.sh postgres Up (unhealthy) 0.0.0.0:32773->5432/tcp
foreman_orchestrator_1 entrypoint.sh bundle exec … Up (health: starting) 3000/tcp, 5910/tcp, 5911/tcp, 5912/tcp, 5913/tcp, 5914/tcp, 5915/tcp, 5916/tcp,
5917/tcp, 5918/tcp, 5919/tcp, 5920/tcp, 5921/tcp, 5922/tcp, 5923/tcp, 5924/tcp,
5925/tcp, 5926/tcp, 5927/tcp, 5928/tcp, 5929/tcp, 5930/tcp
foreman_redis-cache_1 docker-entrypoint.sh redis … Up 6379/tcp
foreman_redis-tasks_1 docker-entrypoint.sh redis … Up 6379/tcp
foreman_worker_1 entrypoint.sh bundle exec … Up (health: starting) 3000/tcp, 5910/tcp, 5911/tcp, 5912/tcp, 5913/tcp, 5914/tcp, 5915/tcp, 5916/tcp,
5917/tcp, 5918/tcp, 5919/tcp, 5920/tcp, 5921/tcp, 5922/tcp, 5923/tcp, 5924/tcp,
5925/tcp, 5926/tcp, 5927/tcp, 5928/tcp, 5929/tcp, 5930/tcp

Expected outcome:
login to http://localhost:3000 username admin, password changeme
Foreman and Proxy versions:

Foreman and Proxy plugin versions:

Distribution and version:
Docker version 19.03.5, build 633a0ea838
docker-compose version 1.26.0, build d4451659
Other relevant data:

I just tried on a clean environment and it worked for me… can you please provide the full logs from docker compose?

I did see this warning, but its just a warning…