Failed Docker instructions to remove and clean up Gems on openc3-cmd-tlm-api image

[NuclearFizzler]

I'm building a COSMOS gem via openc3.sh cli rake build VERSION=(number), and I've been getting the following warning. The gem still builds fine, that's why this is a question and not a bug report. I decided to track down the source of the issue.

WARN: Unresolved or ambiguous specs during Gem::Specification.reset:
      stringio (>= 0)
      Available/installed versions of this gem:
      - 3.1.2
      - 3.0.4
WARN: Clearing out unresolved specs. Try 'gem cleanup <gem>'

From some digging, stringio 3.1.2 is coming from the Gemfile.lock inside the image, while I suspect 3.0.4 is coming from installing RubyGems 3.3.14 based on the release dates of both versions (May and December 2022). I know that migrations are in progress; however, why is RubyGems 3.3.14 required?

Additionally, it seems that the instructions to remove grpc and google-protobuf did not run successfully. I opened a terminal on the latest version of cmd-tlm-api and found the following:

Running the uninstall command with the --debug flag revealed issues with the flags set in gemrc.

I'm not sure what the overall impact of these issues are. I'd like to hear your feedback on these issues, given that you have more experience working on COSMOS.

[NuclearFizzler]

I did some more testing with the docker images; cleaning up the gem options cleared some of the exceptions, but the uninstall commands still seem to have no effect. The gem still appears in gem list afterward.

[jmthomas]

The grpc stuff is a little weird because we need to install with the --platform ruby flag and then uninstall the --platform aarch64-linux flag. I think you're on to something with the .gemrc stuff though. I'm doing some local testing and will let you know.

[jmthomas]

Thanks @NuclearFizzler! I'd love for you to reach out to us (https://www.openc3.com/contact) and let us know what you're using COSMOS for!