openc3 make error in NOS3 1.7.4

[mrgross-mitre]

Hello, I have a question about an error we are seeing when trying to change the ground station from cosmos to openc3. I'm not sure if it is a bug so I'm posting my question here in the discussion thread first. The setup is 1) a ubuntu 22.04 host VM, 2) pulling the latest NOS3 (1.7.4), 3) changing the ground station from the default to openc3 leads to this error during the "make" process.

Install plugin...
Container openc3-openc3-cosmos-cmd-tlm-api-run-59aaff7d9693 Creating
Container openc3-openc3-cosmos-cmd-tlm-api-run-59aaff7d9693 Created
{"time":1776261113842378968,"@timestamp":"2026-04-15T13:51:53.842378Z","level":"ERROR","container_name":"9e9782fb204e","message":"Gem file ./openc3-cosmos-nos3-1.0.202604150951.gem error installing to /gems\nFilePermissionError : You don't have write permissions for the /gems/gems/openc3-cosmos-nos3-1.0.202604150951 directory.\n/usr/local/lib/site_ruby/3.3.0/rubygems/installer.rb:340:in rescue in install'\n/usr/local/lib/site_ruby/3.3.0/rubygems/installer.rb:289:in install'\n/usr/local/lib/site_ruby/3.3.0/rubygems/resolver/specification.rb:105:in install'\n/usr/local/lib/site_ruby/3.3.0/rubygems/request_set.rb:195:in block in install'\n/usr/local/lib/site_ruby/3.3.0/rubygems/request_set.rb:183:in each'\n/usr/local/lib/site_ruby/3.3.0/rubygems/request_set.rb:183:in install'\n/usr/local/lib/site_ruby/3.3.0/rubygems/dependency_installer.rb:250:in install'\n/usr/local/lib/site_ruby/3.3.0/rubygems.rb:563:in install'\n/usr/lib/ruby/gems/3.3.0/gems/openc3-6.3.0/lib/openc3/models/gem_model.rb:97:in rescue in install'\n/usr/lib/ruby/gems/3.3.0/gems/openc3-6.3.0/lib/openc3/models/gem_model.rb:92:in install'\n/openc3/bin/openc3cli:460:in cli_pkg_install'\n/openc3/bin/openc3cli:797:in

'","type":"log"}
/usr/local/lib/site_ruby/3.3.0/rubygems/installer.rb:340:in `rescue in install': You don't have write permissions for the /gems/gems/openc3-cosmos-nos3-1.0.202604150951 directory. (Gem::FilePermissionError)

We can track down the exact command where this error is happening, it has to do with the openc3 docker compose.yaml file, but we don't have this error with an older version of NOS3.

Any suggestions would be helpful.
Thanks,
Mike

[zlynch2]

hi @mrgross-mitre!

this is interesting, as im not sure I have seen this error before. your output should look like the following when running "make"

Build plugin...
gem build openc3-cosmos-nos3
WARNING:  make sure you specify the oldest ruby version constraint (like ">= 3.0") that you want your gem to support by setting the `required_ruby_version` gemspec attribute
WARNING:  See https://guides.rubygems.org/specification-reference/ for help
openc3cli validate openc3-cosmos-nos3-1.0.202604151853.gem
  Successfully built RubyGem
  Name: openc3-cosmos-nos3
  Version: 1.0.202604151853
  File: openc3-cosmos-nos3-1.0.202604151853.gem
Installing openc3-cosmos-nos3-1.0.202604151853.gem
Successfully uninstalled openc3-cosmos-nos3-1.0.202512192156
Successfully validated openc3-cosmos-nos3-1.0.202604151853.gem

Install plugin...
Gem installation successful

However, going from 1.7.3 to 1.7.4 included a docker version upgrade for an OpenC3 Upgrade.

A couple follow up questions.

1. Are you using a nos3 VM or a custom built ubuntu
2. What do your filepaths look like, sometime weird things happen with shared folders not sure why, ive had better luck with nos3/ src living inside ubuntu rather than using shared folders.
3. please check docker versioning, (Docker version 28.5.2, build ecc6942) is what we are on and also on
   Description: Ubuntu 22.04.4 LTS
   Release: 22.04
   Codename: jammy

Hopefully its a version or path problem. I have seen the gem file not be loaded with the upgraded openC3 but we resolve that by intalling the gem file manually. After that nos3/ build process seems to install it just fine (again not sure why as our process passes during make per debug prints). But your issue fails during this process.

Let me know if this helps or I can try to keep debugging with you as well!

[mrgross-mitre]

Hi Zachary, Thanks for the quick response – really appreciate it. Several of us on my team are having the same issue – but we are all working within the same MITRE resource (but on different VM instances). To answer your questions: 1. We are doing a custom build – our own VM(s) – all running ubuntu 22.04 2. We are not using shared folders. For me at least NOS3 lives in the /opt directory. I know others have it in their home directories and are having the same issue. 3. My docker version is: 29.4.0 4. And like I said, we are also using Ubuntu 22.04.5 LTS, jammy Thanks, Mike From: Zachary Lynch ***@***.***> Sent: Wednesday, April 15, 2026 3:13 PM To: nasa/nos3 ***@***.***> Cc: Michael R Gross ***@***.***>; Mention ***@***.***> Subject: [EXT] Re: [nasa/nos3] openc3 make error in NOS3 1.7.4 (Discussion #849) hi @mrgross-mitre! this is interesting, as im not sure I have seen this error before. your output should look like the following when running "make" Build plugin. . . gem build openc3-cosmos-nos3 WARNING: make sure you specify the oldest ruby hi @mrgross-mitre<https://urldefense.us/v2/url?u=https-3A__github.com_mrgross-2Dmitre&d=DwMFaQ&c=Al8V6E3U0yBSSEuVtdZbGtsvjPA49U3WmtZAsdW0D_Q&r=_8c2GcHD0JBdjP1w8b2LPLCwqlAdjfa1QyN7RG2NOiA&m=shwTrXjG1lm9Gi1Qr-F6aw5uvSNMwCOvOysQgAJjvKeXqo5_rOfE9odWbSg3Nv1H&s=o-4fQds9NdDE5g1kuOI3-Tgp7D6_oFUhpSVk0Lylo7s&e=>! this is interesting, as im not sure I have seen this error before. your output should look like the following when running "make" Build plugin... gem build openc3-cosmos-nos3 WARNING: make sure you specify the oldest ruby version constraint (like ">= 3.0") that you want your gem to support by setting the `required_ruby_version` gemspec attribute WARNING: See https://guides.rubygems.org/specification-reference/<https://urldefense.us/v2/url?u=https-3A__guides.rubygems.org_specification-2Dreference_&d=DwQFaQ&c=Al8V6E3U0yBSSEuVtdZbGtsvjPA49U3WmtZAsdW0D_Q&r=_8c2GcHD0JBdjP1w8b2LPLCwqlAdjfa1QyN7RG2NOiA&m=shwTrXjG1lm9Gi1Qr-F6aw5uvSNMwCOvOysQgAJjvKeXqo5_rOfE9odWbSg3Nv1H&s=rPVLCdn--LLr3M_FpNcpqf_aOOvZNF8sSkKzBT2RgnY&e=> for help openc3cli validate openc3-cosmos-nos3-1.0.202604151853.gem Successfully built RubyGem Name: openc3-cosmos-nos3 Version: 1.0.202604151853 File: openc3-cosmos-nos3-1.0.202604151853.gem Installing openc3-cosmos-nos3-1.0.202604151853.gem Successfully uninstalled openc3-cosmos-nos3-1.0.202512192156 Successfully validated openc3-cosmos-nos3-1.0.202604151853.gem Install plugin... Gem installation successful However, going from 1.7.3 to 1.7.4 included a docker version upgrade for an OpenC3 Upgrade. A couple follow up questions. 1. Are you using a nos3 VM or a custom built ubuntu 2. What do your filepaths look like, sometime weird things happen with shared folders not sure why, ive had better luck with nos3/ src living inside ubuntu rather than using shared folders. 3. please check docker versioning, (Docker version 28.5.2, build ecc6942) is what we are on and also on Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy Hopefully its a version or path problem. I have seen the gem file not be loaded with the upgraded openC3 but we resolve that by intalling the gem file manually. After that nos3/ build process seems to install it just fine (again not sure why as our process passes during make per debug prints). But your issue fails during this process. Let me know if this helps or I can try to keep debugging with you as well! — Reply to this email directly, view it on GitHub<https://urldefense.us/v2/url?u=https-3A__github.com_nasa_nos3_discussions_849-23discussioncomment-2D16574587&d=DwMFaQ&c=Al8V6E3U0yBSSEuVtdZbGtsvjPA49U3WmtZAsdW0D_Q&r=_8c2GcHD0JBdjP1w8b2LPLCwqlAdjfa1QyN7RG2NOiA&m=shwTrXjG1lm9Gi1Qr-F6aw5uvSNMwCOvOysQgAJjvKeXqo5_rOfE9odWbSg3Nv1H&s=DN0Ig9ktQWrrKuaXy3DzELDmIE0ZItnOv4tgjksRp0o&e=>, or unsubscribe<https://urldefense.us/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_BD3K6LXP77WPJBSVVEUZKLT4V7NJ5AVCNFSM6AAAAACX2JAJZ6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNJXGQ2TQNY&d=DwMFaQ&c=Al8V6E3U0yBSSEuVtdZbGtsvjPA49U3WmtZAsdW0D_Q&r=_8c2GcHD0JBdjP1w8b2LPLCwqlAdjfa1QyN7RG2NOiA&m=shwTrXjG1lm9Gi1Qr-F6aw5uvSNMwCOvOysQgAJjvKeXqo5_rOfE9odWbSg3Nv1H&s=JLpMvYCmuNL9CRraQteaJPv1O4ExIQe4AOQ0ClklrMw&e=>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[zlynch2]

as a quick test, if possible try to downgrade the docker version. You may not need all these commands but i would be cruious if permissions with docker changed with an updated version and we just havent seen it yet.

Upgrading to 28.5.2
 
sudo apt remove docker docker-engine docker.io containerd runc
 
sudo mkdir -p /etc/apt/keyrings
 
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
 
echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
 
sudo apt update
 
sudo apt install docker-ce=5:28.5.2-1~ubuntu.22.04~jammy docker-ce-cli=5:28.5.2-1~ubuntu.22.04~jammy containerd.io docker-buildx-plugin docker-compose-plugin --allow-downgrades
 
docker --version

you could also (as a test) try adding root privileges when building as well just to see if the install can occur. note this will make everything need to run with sudo. or make sure your user can edit appropriate files, Although im sure you made sure you can edit files in that file path.

let me know if any of this helps. Thanks!

[mrgross-mitre]

Hi Zach, Thanks for the tips – I appreciate the help. 1. I downgraded my docker to version 28.5.2. I still get the exact same error. 2. I had already tried to compile as root, but I tried it again just to be sure. Doing that creates a different set of errors. I guess I can push that direction more if needed. I’d like to not have to run as root if we can help it. 3. The file system that would need to have permissions changed is one (and maybe more than one) of the openc3 containers, which get pulled and started during the make process, so its not so clear how to change a dir permission in that situation (to me at least). Thanks, Mike From: Zachary Lynch ***@***.***> Sent: Wednesday, April 15, 2026 4:29 PM To: nasa/nos3 ***@***.***> Cc: Michael R Gross ***@***.***>; Mention ***@***.***> Subject: [EXT] Re: [nasa/nos3] openc3 make error in NOS3 1.7.4 (Discussion #849) as a quick test, if possible try to downgrade the docker version. You may not need all these commands but i would be cruious if permissions with docker changed with an updated version and we just havent seen it yet. Upgrading to 28. 5. 2 sudo as a quick test, if possible try to downgrade the docker version. You may not need all these commands but i would be cruious if permissions with docker changed with an updated version and we just havent seen it yet. Upgrading to 28.5.2 sudo apt remove docker docker-engine docker.io containerd runc sudo mkdir -p /etc/apt/keyrings curl -fsSL https://download.docker.com/linux/ubuntu/gpg<https://urldefense.us/v2/url?u=https-3A__download.docker.com_linux_ubuntu_gpg&d=DwQFaQ&c=Al8V6E3U0yBSSEuVtdZbGtsvjPA49U3WmtZAsdW0D_Q&r=_8c2GcHD0JBdjP1w8b2LPLCwqlAdjfa1QyN7RG2NOiA&m=6duvwz6nndeJltc03sDNrkVKIUqCgvheEoBdDIVloVUV_kdx7Q1Piynq5fN-NjMY&s=QjeVa_7nd6AUqWwb9yIV0kSsVGgkPBpbbkEWfDEGNUo&e=> | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu<https://urldefense.us/v2/url?u=https-3A__download.docker.com_linux_ubuntu&d=DwQFaQ&c=Al8V6E3U0yBSSEuVtdZbGtsvjPA49U3WmtZAsdW0D_Q&r=_8c2GcHD0JBdjP1w8b2LPLCwqlAdjfa1QyN7RG2NOiA&m=6duvwz6nndeJltc03sDNrkVKIUqCgvheEoBdDIVloVUV_kdx7Q1Piynq5fN-NjMY&s=b4AWLNEH4kjfHgdfilHM4H4DQXXc2A142lIdrof0syo&e=> $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null sudo apt update sudo apt install docker-ce=5:28.5.2-1~ubuntu.22.04~jammy docker-ce-cli=5:28.5.2-1~ubuntu.22.04~jammy containerd.io docker-buildx-plugin docker-compose-plugin --allow-downgrades docker --version you could also (as a test) try adding root privileges when building as well just to see if the install can occur. note this will make everything need to run with sudo. or make sure your user can edit appropriate files, Although im sure you made sure you can edit files in that file path. let me know if any of this helps. Thanks! — Reply to this email directly, view it on GitHub<https://urldefense.us/v2/url?u=https-3A__github.com_nasa_nos3_discussions_849-23discussioncomment-2D16575223&d=DwMFaQ&c=Al8V6E3U0yBSSEuVtdZbGtsvjPA49U3WmtZAsdW0D_Q&r=_8c2GcHD0JBdjP1w8b2LPLCwqlAdjfa1QyN7RG2NOiA&m=6duvwz6nndeJltc03sDNrkVKIUqCgvheEoBdDIVloVUV_kdx7Q1Piynq5fN-NjMY&s=GidC1aBhTbo75dAqeCvGwSdQ2sFbUzd7R1lYjE4yDXE&e=>, or unsubscribe<https://urldefense.us/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_BD3K6LXKUAGZTSIOVTULQY34V7WIZAVCNFSM6AAAAACX2JAJZ6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNJXGUZDEMY&d=DwMFaQ&c=Al8V6E3U0yBSSEuVtdZbGtsvjPA49U3WmtZAsdW0D_Q&r=_8c2GcHD0JBdjP1w8b2LPLCwqlAdjfa1QyN7RG2NOiA&m=6duvwz6nndeJltc03sDNrkVKIUqCgvheEoBdDIVloVUV_kdx7Q1Piynq5fN-NjMY&s=twqx6qNbZ7LkYDSimQTW0biYDVT-KcqnaUwk5Mc5k4U&e=>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[zlynch2]

Hi Mike, is your opt directory owned by root in this case. I suspect we may be battling different permission levels when creating the .nos3/ directory at the root level on your host. Can you confirm that the ownership of the directories is sufficient for your user?

I also suspect if the gem/ directory was created with root (or the .nos3/ directory for that matter) then root privledges would stay persistent. A "Make uninstall" may help remove any nos3 build files/containers. Note this will wipe the .nos3 directory so save off changes to opneC3 if you have any. After that, "make prep", "make", this time ensuring you have user access if not already.

[zlynch2]

Im also curious as well, if we are simply having trouble installing the gem file. maybe remove those from the make process during the "build_openC3" script in scripts/gsw/. Then make but when you make launch you will have to manually install the gem file.

[mrgross-mitre]

Morning Zach, I did what you suggested – commented out the offending gem install lines – and that allows things to progress w/o error (for the make command). Sadly, I think this issue is more widely a problem. When I try to do make launch, the openc3 browser comes up but shows a html error. Digging deeper I can see that this container: openc3-openc3-cosmos-init-1 keeps restarting about every 20 sec or so. Looking at: docker logs openc3-openc3-cosmos-init-1 Shows a similar permission issue: (see below) Same kind of gems install permissions issue. I’m tracking it now to the compose.yaml file that gets written to the: ~/.nos3/openc3 directory. Does that make sense? Each openc3 container gets started with this user: user: "${OPENC3_USER_ID:-1001}:${OPENC3_GROUP_ID:-1001}" Which we see is different from an older version of NOS3 (openc3) that we are able to get working. Thanks, Mike Restoring gems to pristine condition... Mon Apr 20 13:17:40 UTC 2026 2026-04-20T13:17:40Z waiting for Minio http://openc3-minio:9000 RC: 0 2026-04-20T13:17:46Z waiting for Redis openc3-redis:6379. RC: 0 2026-04-20T13:17:52Z waiting for Redis Ephemeral openc3-redis-ephemeral:6380. RC: 0 Brand new installation detected All migrations skipped Added `openc3minio` successfully. Created policy `script` successfully. Added user `scriptrunnerminio` successfully. Attached Policies: [script] To User: scriptrunnerminio No version change detected for: openc3-tool-base-6.3.0.gem__20260408183415 Loading new plugin: /openc3/plugins/gems/openc3-cosmos-tool-iframe-6.3.0.gem {"name"=>"openc3-cosmos-tool-iframe-6.3.0.gem", "variables"=>{}, "plugin_txt_lines"=>["TOOL iframe \"Iframe\"", " INLINE_URL main.js", " SHOWN false", " POSITION 50"], "needs_dependencies"=>false, "updated_at"=>nil} ***@***.***":"2026-04-20T13:18:05.653402Z","level":"ERROR","container_name":"506e5c608a9e","message":"Gem file /gems/cosmoscache/openc3-cosmos-tool-iframe-6.3.0.gem error installing to /gems\nFilePermissionError : You don't have write permissions for the /gems/gems/openc3-cosmos-tool-iframe-6.3.0 directory.\n/usr/local/lib/site_ruby/3.3.0/rubygems/installer.rb:340:in `rescue in install'\n/usr/local/lib/site_ruby/3.3.0/rubygems/installer.rb:289:in `install'\n/usr/local/lib/site_ruby/3.3.0/rubygems/resolver/specification.rb:105:in `install'\n/usr/local/lib/site_ruby/3.3.0/rubygems/request_set.rb:195:in `block in install'\n/usr/local/lib/site_ruby/3.3.0/rubygems/request_set.rb:183:in `each'\n/usr/local/lib/site_ruby/3.3.0/rubygems/request_set.rb:183:in `install'\n/usr/local/lib/site_ruby/3.3.0/rubygems/dependency_installer.rb:250:in `install'\n/usr/local/lib/site_ruby/3.3.0/rubygems.rb:563:in `install'\n/usr/lib/ruby/gems/3.3.0/gems/openc3-6.3.0/lib/openc3/models/gem_model.rb:97:in `rescue in install'\n/usr/lib/ruby/gems/3.3.0/gems/openc3-6.3.0/lib/openc3/models/gem_model.rb:92:in `install'\n/usr/lib/ruby/gems/3.3.0/gems/openc3-6.3.0/lib/openc3/models/plugin_model.rb:167:in `install_phase2'\n/openc3/bin/openc3cli:412:in `load_plugin'\n/openc3/bin/openc3cli:788:in `<main>'","type":"log"} Error installing plugin: DEFAULT: /openc3/plugins/gems/openc3-cosmos-tool-iframe-6.3.0.gem FilePermissionError : You don't have write permissions for the /gems/gems/openc3-cosmos-tool-iframe-6.3.0 directory. /usr/local/lib/site_ruby/3.3.0/rubygems/installer.rb:340:in `rescue in install' /usr/local/lib/site_ruby/3.3.0/rubygems/installer.rb:289:in `install' /usr/local/lib/site_ruby/3.3.0/rubygems/resolver/specification.rb:105:in `install' /usr/local/lib/site_ruby/3.3.0/rubygems/request_set.rb:195:in `block in install' /usr/local/lib/site_ruby/3.3.0/rubygems/request_set.rb:183:in `each' /usr/local/lib/site_ruby/3.3.0/rubygems/request_set.rb:183:in `install' /usr/local/lib/site_ruby/3.3.0/rubygems/dependency_installer.rb:250:in `install' /usr/local/lib/site_ruby/3.3.0/rubygems.rb:563:in `install' /usr/lib/ruby/gems/3.3.0/gems/openc3-6.3.0/lib/openc3/models/gem_model.rb:97:in `rescue in install' /usr/lib/ruby/gems/3.3.0/gems/openc3-6.3.0/lib/openc3/models/gem_model.rb:92:in `install' /usr/lib/ruby/gems/3.3.0/gems/openc3-6.3.0/lib/openc3/models/plugin_model.rb:167:in `install_phase2' /openc3/bin/openc3cli:412:in `load_plugin' /openc3/bin/openc3cli:788:in `<main>' Mon Apr 20 13:18:06 UTC 2026 ERROR: While executing gem ... (Gem::FilePermissionError) You don't have write permissions for the /gems/gems/openc3-cosmos-nos3-1.0.202604081419/LICENSE.txt directory. /usr/local/lib/site_ruby/3.3.0/rubygems/installer.rb:340:in `rescue in install' /usr/local/lib/site_ruby/3.3.0/rubygems/installer.rb:289:in `install' /usr/local/lib/site_ruby/3.3.0/rubygems/commands/pristine_command.rb:205:in `block in execute' /usr/local/lib/site_ruby/3.3.0/rubygems/commands/pristine_command.rb:137:in `each' /usr/local/lib/site_ruby/3.3.0/rubygems/commands/pristine_command.rb:137:in `execute' /usr/local/lib/site_ruby/3.3.0/rubygems/command.rb:326:in `invoke_with_build_args' /usr/local/lib/site_ruby/3.3.0/rubygems/command_manager.rb:253:in `invoke_command' /usr/local/lib/site_ruby/3.3.0/rubygems/command_manager.rb:194:in `process_args' /usr/local/lib/site_ruby/3.3.0/rubygems/command_manager.rb:152:in `run' /usr/local/lib/site_ruby/3.3.0/rubygems/gem_runner.rb:57:in `run' /usr/bin/gem:12:in `<main>' From: Zachary Lynch ***@***.***> Sent: Thursday, April 16, 2026 3:21 PM To: nasa/nos3 ***@***.***> Cc: Michael R Gross ***@***.***>; Mention ***@***.***> Subject: [EXT] Re: [nasa/nos3] openc3 make error in NOS3 1.7.4 (Discussion #849) Im also curious as well, if we are simply having trouble installing the gem file. maybe remove those from the make process during the "build_openC3" script in scripts/gsw/. Then make but when you make launch you will have to manually install Im also curious as well, if we are simply having trouble installing the gem file. maybe remove those from the make process during the "build_openC3" script in scripts/gsw/. Then make but when you make launch you will have to manually install the gem file. — Reply to this email directly, view it on GitHub<https://urldefense.us/v2/url?u=https-3A__github.com_nasa_nos3_discussions_849-23discussioncomment-2D16592647&d=DwMFaQ&c=Al8V6E3U0yBSSEuVtdZbGtsvjPA49U3WmtZAsdW0D_Q&r=_8c2GcHD0JBdjP1w8b2LPLCwqlAdjfa1QyN7RG2NOiA&m=sNrB0quxsVU-aVSFt5dYn3SFvseNToDgf63Ej_ZPexwsZHFlo2UV5h4a1RMN7Iul&s=7t2-WlqXp3SzS5svEG04RYSJc4KSX92XI9QpLqO3FhU&e=>, or unsubscribe<https://urldefense.us/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_BD3K6LQF2BGUTXMZWE6CV3T4WEXCRAVCNFSM6AAAAACX2JAJZ6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNJZGI3DINY&d=DwMFaQ&c=Al8V6E3U0yBSSEuVtdZbGtsvjPA49U3WmtZAsdW0D_Q&r=_8c2GcHD0JBdjP1w8b2LPLCwqlAdjfa1QyN7RG2NOiA&m=sNrB0quxsVU-aVSFt5dYn3SFvseNToDgf63Ej_ZPexwsZHFlo2UV5h4a1RMN7Iul&s=IE-MSiXxya1V-jSRG_8tOxOdHaXCDQO6is6_UHwNb94&e=>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[zlynch2]

Hi @mrgross-mitre !

Thinking out loud here. I checked the docker user on my end when launching the openc3 containers and I obtain i believe the same info.
uid=1001(openc3) gid=1001(openc3) groups=1001(openc3)

Now I would check to see that maybe that your user is added to the docker group: sudo usermod -aG docker $USER

It probably is already but please verify. we did downgrade docker at onepoint.

My only other concern is still where nos3 src files are located. I would make sure you dont need root permissions to modify files. When running make we create .nos3/ directory that ideally a user shouldnt need to modify. if these files for whatever reason are being created with root permissions it could cause permission issues. Maybe Change ownership of the entire nos3 directory to the current standard user
sudo chown -R $USER:$USER /opt/nos3 (if not already)

on my system, i have my files located /home/jstar/dev (where jstar is the user and dev is a folder i created as jstar)

Also something to check, make sure we have fresh docker images and nothing is old or mismatched in docker version. Meaning I want to make sure we didnt accidentally create a docker container with root privileges and its still alive.

To remove docker cache and volumes:
docker images ls (checks which images are living on your host)
docker system df
docker builder prune

If you get errors try removing all the images use sudo.
then make prep, make again.

Let me know, Thanks!

[mrgross-mitre]

Hi Zach, Thanks for your thoughts. I’m tracking all your comments, and mostly had already checked the things you mentioned. I was the owner of /opt/nos3 – plus others in my group have had the same problem even when installing in their home dirs. I have an interesting find (and solution). Here is what I did. 1. Stopped all containers (nos3 and openc3) 2. Went into my ./nos3/openc3 directory 3. Changed the openc3 version (to 6.10.5) in the .env file in that directory 4. Ran: ./openc3.sh run (so basically, I installed and ran a newer version of openc3) This works. I get the web interface as expected and it is version 6.10.5. Here’s the strange part. If I now go back in nos3 and run: make prep make without changing the openc3 version (so 6.3.0) that is pointed to by NOS3, I no longer see errors. NOS3 make works as expected and the openc3 web interface comes up w/o errors. The gem install also now works too. Seems like maybe 6.3.0 had some volume permission errors? Maybe something in the compose.yaml file? Ideas? Either way, I have a work around. Appreciate the help. Thanks, Mike From: Zachary Lynch ***@***.***> Sent: Monday, April 20, 2026 11:00 AM To: nasa/nos3 ***@***.***> Cc: Michael R Gross ***@***.***>; Mention ***@***.***> Subject: [EXT] Re: [nasa/nos3] openc3 make error in NOS3 1.7.4 (Discussion #849) Hi @mrgross-mitre ! Thinking out loud here. I checked the docker user on my end when launching the openc3 containers and I obtain i believe the same info. uid=1001(openc3) gid=1001(openc3) groups=1001(openc3) Now I would check to see that maybe Hi @mrgross-mitre<https://urldefense.us/v2/url?u=https-3A__github.com_mrgross-2Dmitre&d=DwMFaQ&c=Al8V6E3U0yBSSEuVtdZbGtsvjPA49U3WmtZAsdW0D_Q&r=_8c2GcHD0JBdjP1w8b2LPLCwqlAdjfa1QyN7RG2NOiA&m=8SXUriz3InqOZZ-hn_xMuL1DiBYgnlE_8ge4QTNpbw-fVnviNsb8G1eB9nglIN7E&s=6vodZIJJ3fqxH0ZKkSwkcWMZTIL_e-ysvwVsILviw5k&e=> ! Thinking out loud here. I checked the docker user on my end when launching the openc3 containers and I obtain i believe the same info. uid=1001(openc3) gid=1001(openc3) groups=1001(openc3) Now I would check to see that maybe that your user is added to the docker group: sudo usermod -aG docker $USER It probably is already but please verify. we did downgrade docker at onepoint. My only other concern is still where nos3 src files are located. I would make sure you dont need root permissions to modify files. When running make we create .nos3/ directory that ideally a user shouldnt need to modify. if these files for whatever reason are being created with root permissions it could cause permission issues. Maybe Change ownership of the entire nos3 directory to the current standard user sudo chown -R $USER:$USER /opt/nos3 (if not already) on my system, i have my files located /home/jstar/dev (where jstar is the user and dev is a folder i created as jstar) Also something to check, make sure we have fresh docker images and nothing is old or mismatched in docker version. Meaning I want to make sure we didnt accidentally create a docker container with root privileges and its still alive. To remove docker cache and volumes: docker images ls (checks which images are living on your host) docker system df docker builder prune If you get errors try removing all the images use sudo. then make prep, make again. Let me know, Thanks! — Reply to this email directly, view it on GitHub<https://urldefense.us/v2/url?u=https-3A__github.com_nasa_nos3_discussions_849-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DBD3K6LRPHKK7OVGJ5J3TGJD4WY3OPA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRWGM3TGNBSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y-23discussioncomment-2D16637342&d=DwMFaQ&c=Al8V6E3U0yBSSEuVtdZbGtsvjPA49U3WmtZAsdW0D_Q&r=_8c2GcHD0JBdjP1w8b2LPLCwqlAdjfa1QyN7RG2NOiA&m=8SXUriz3InqOZZ-hn_xMuL1DiBYgnlE_8ge4QTNpbw-fVnviNsb8G1eB9nglIN7E&s=oa9jyyGRc4Gq0lh7-npZ6KgJ1T5IhJc0-n0kfI1Q_c0&e=>, or unsubscribe<https://urldefense.us/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_BD3K6LSZQWGPL5F66YBGBL34WY3OPAVCNFSM6AAAAACX2JAJZ6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNRTG4ZTIMQ&d=DwMFaQ&c=Al8V6E3U0yBSSEuVtdZbGtsvjPA49U3WmtZAsdW0D_Q&r=_8c2GcHD0JBdjP1w8b2LPLCwqlAdjfa1QyN7RG2NOiA&m=8SXUriz3InqOZZ-hn_xMuL1DiBYgnlE_8ge4QTNpbw-fVnviNsb8G1eB9nglIN7E&s=55OHJZ9O6-5QBwMIYCyc-J2Dnxr6xUzQrBN_B9KuIGI&e=>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[zlynch2]

Interesting! Ive never heard of that until now, but Im glad you were able to work around it. Sounds like now you are able to run nos3 with the openC3 version 6.3 out of the box.

When shutting down nos3 I always make sure to make stop. make uninstall will remove the .nos3/ directory too. however if you are just rebuilding your environment you should be able to just make stop, make clean, make.

Id say next steps is to make sure you can make uninstall, make prep, make, make launch. Id be curious if you would still have to manually edit openC3/ in the .nos3/ directory. Please let me know if you can. Thanks!

[mrgross-mitre]

Thanks Zach, Good tips, appreciate that. It seems that once I install openc3 using the newer version, I don’t have to edit anything after that. By that I mean I can do: make stop, make uninstall, make prep, make, make launch … and the older version of openc3 now works. It sure seems like something on the system (or with my user) is getting set with the newer openc3 install and then it is persisting when I go back to the NOS3 process (and an older openc3). If we discover the exact issue, I’ll let you know. Thanks, Mike From: Zachary Lynch ***@***.***> Sent: Monday, April 20, 2026 3:00 PM To: nasa/nos3 ***@***.***> Cc: Michael R Gross ***@***.***>; Mention ***@***.***> Subject: [EXT] Re: [nasa/nos3] openc3 make error in NOS3 1.7.4 (Discussion #849) Interesting! Ive never heard of that until now, but Im glad you were able to work around it. Sounds like now you are able to run nos3 with the openC3 version 6. 3 out of the box. When shutting down nos3 I always make sure to make stop. make uninstall Interesting! Ive never heard of that until now, but Im glad you were able to work around it. Sounds like now you are able to run nos3 with the openC3 version 6.3 out of the box. When shutting down nos3 I always make sure to make stop. make uninstall will remove the .nos3/ directory too. however if you are just rebuilding your environment you should be able to just make stop, make clean, make. Id say next steps is to make sure you can make uninstall, make prep, make, make launch. Id be curious if you would still have to manually edit openC3/ in the .nos3/ directory. Please let me know if you can. Thanks! — Reply to this email directly, view it on GitHub<https://urldefense.us/v2/url?u=https-3A__github.com_nasa_nos3_discussions_849-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DBD3K6LRKB5AUA3I4PJCEMH34WZXSDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRWGQYDGMBQUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y-23discussioncomment-2D16640300&d=DwMFaQ&c=Al8V6E3U0yBSSEuVtdZbGtsvjPA49U3WmtZAsdW0D_Q&r=_8c2GcHD0JBdjP1w8b2LPLCwqlAdjfa1QyN7RG2NOiA&m=liBNa6CPpplVVyZf6rbjcixCjG_XKOb9QFJD7Xr1AGvDPUtbTmfZTHMSX8h_Ulfl&s=q1jp541iZJMAmd5F5vuOa53B6GpFk-FflN-1D1HHwPU&e=>, or unsubscribe<https://urldefense.us/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_BD3K6LSBCUAZGWU6X33Y7G34WZXSDAVCNFSM6AAAAACX2JAJZ6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNRUGAZTAMA&d=DwMFaQ&c=Al8V6E3U0yBSSEuVtdZbGtsvjPA49U3WmtZAsdW0D_Q&r=_8c2GcHD0JBdjP1w8b2LPLCwqlAdjfa1QyN7RG2NOiA&m=liBNa6CPpplVVyZf6rbjcixCjG_XKOb9QFJD7Xr1AGvDPUtbTmfZTHMSX8h_Ulfl&s=TLZpwPgbtw4w7LALd8_obNu2YKBtdl8cik1_s5w1AtQ&e=>. You are receiving this because you were mentioned.Message ID: ***@***.***>