Based on the work by wjordan in this comment
The solution is to force the update of RubyGems to side step the issue.
gem update --force --system 2.6.11
Then the error does not occur.
Based on the work by wjordan in this comment
The solution is to force the update of RubyGems to side step the issue.
gem update --force --system 2.6.11
Then the error does not occur.