container not initialized yet

Can you turn on verbose debugging via settings.php and provide a stack trace?

Set the config in settings.php but no stack trace beyond this below showed

PHPStan command failed:
/usr/bin/php /var/www/public_html/vendor/bin/phpstan analyse --memory-limit=1500M --error-format=json --configuration=/tmp/upgrade_status/deprecation_testing.neon /var/www/public_html/modules/dynamic_entity_reference

Command output:
Empty.

Command error:
PHP Fatal error: Drupal\Core\DependencyInjection\ContainerNotInitializedException thrown while calling __toString on a Drupal\Core\StringTranslation\TranslatableMarkup object in /var/www/public_html/core/lib/Drupal.php on line 170: \Drupal::$container is not initialized yet. \Drupal::setContainer() must be called with a real container. in /var/www/public_html/core/lib/Drupal/Component/Utility/ToStringTrait.php on line 20 Fatal error: Drupal\Core\DependencyInjection\ContainerNotInitializedException thrown while calling __toString on a Drupal\Core\StringTranslation\TranslatableMarkup object in /var/www/public_html/core/lib/Drupal.php on line 170: \Drupal::$container is not initialized yet. \Drupal::setContainer() must be called with a real container. in /var/www/public_html/core/lib/Drupal/Component/Utility/ToStringTrait.php on line 20

This looks like a duplicate.

and yet it was not fixed in rhe duplicate wither

This is STILL an issue. I have updated from 10.4 to 11.1 as recomended and upgrade status gave the green light. Now, those whole this is throwing random errors to do with \Drupal::$container is not initialized yet. \Drupal::setContainer() must be called with a real container.....

As I was googling I noticed this has been an issue when updating for a very very very very very long time. Though, the first time I have run into this issue. So, I am at a loss. I have disabled all the themes and modules to the bare core and stable them. It still throws errors, There must be a way to fix this?