Problem with instaling Extensions

[WST (Tomasz)]

HI, all. I’m a new user of the blueboat. This is first unit in Poland.
I have a problem installing the extensions. I use BlueOs 1.2.4, but i also tried 1.2.3 version. Still any extension are failed to instal What can be a problem. I see information from LOG: {“detail”:“[{‘loc’: (‘query’, ‘container_name’), ‘msg’: ‘field required’, ‘type’: ‘value_error.missing’}]”}.
The Extension folder is empty.

[EliotBR (Eliot)]

Hi @WST, welcome to the forum

I’ve asked internally, and am told

@williangalvani

That error means BlueOS is trying to check the logs of a non-existent container - we need to check why the actual install failed

It would be helpful if you could provide some system logs so we can take a closer look.

[WST (Tomasz)]

After couple tries, I decided to reinstall system. This was easiest way to create a working system. I think there was a problem with Linux.
I used the Navigator software Setup site, and now I can install all extensions.

There are some errors when I try to load BlueBoat parameters like: NL_ACRO_BLINKS and all group off NL_ parameters are unavailable.

[williangalvani]

Hi,

That means the navlight lua script is not loaded. I recommend setting up the boat from the wizard to setup params and script

[WST (Tomasz)]

I used BlueOS wizard, all components was mark as done (on green).
Can I restart the wizard in BlueOS to reset BB settings and parameters?

[xiaoliyu (Yu Li)]

system_logs1.zip (2.7 MB)
hi all,
I have the same problem, can you help me look at the system log? The BlueOS1.2.6 version memory card newly written the day before yesterday, multiple extensions downloaded after running are not available, has been loading. I later rolled back the version to 1.2.2 and downloaded cockpit again, but it still didn’t open, and it didn’t even show cockpit in my BlueOS sidebar.
I’ve tried downloading the extension in the past with BlueOS1.2.3 and it worked fine. Only recently have I been unable to load extensions in my latest revisions (from 1.2.2 to 1.2.6)

[xiaoliyu (Yu Li)]

[xiaoliyu (Yu Li)]

When I downloaded the extension, instead of a loaded progress bar, it looked like this

I’ve seen that extensions can’t be loaded and configured locally for ease of administration, but can only be pulled from the docker platform, but I guess maybe I’m facing a network issue? If I can install extensions on myself, please help me.

[EliotBR (Eliot)]

Hi @xiaoliyu, welcome to the forum

Sorry to hear you’re having issues with running your extensions.

@xiaoliyu

maybe I’m facing a network issue?

I took a look at your logs, and it does seem like there was some issue with installing Cockpit, or at least with finding it on your system

@system-logs1/kraken/logfile_06-20-2024_01/38/07.log

2024-06-20 01:38:12.587 | INFO     | kraken:start_extension:52 - Going to start {
  "docker": "bluerobotics/cockpit",
  "enabled": true,
  "identifier": "bluerobotics.cockpit",
  "name": "Cockpit",
  "permissions": "{\"ExposedPorts\": {\"8000/tcp\": {}}, \"HostConfig\": {\"PortBindings\": {\"8000/tcp\": [{\"HostPort\": \"\"}]}}}",
  "tag": "v1.0.0-beta.20",
  "user_permissions": ""
}.
2024-06-20 01:38:12.588 | INFO     | kraken:start_extension:55 - Starting extension 'bluerobotics/cockpit:v1.0.0-beta.20'.
2024-06-20 01:38:27.308 | INFO     | kraken:start_extension:59 - Unable to pull a new image, attempting to continue with a local one.
2024-06-20 01:38:27.315 | ERROR    | logging:callHandlers:1706 - Task exception was never retrieved
future: <Task finished name='Task-1' coro=<Kraken.run() done, defined at /home/pi/services/kraken/kraken.py:37> exception=DockerError(404, 'No such image: bluerobotics/cockpit:v1.0.0-beta.20')>

It’s unclear to me whether that’s due to network/server issues or something else, so to confirm:

1. Are you able to install a different BlueOS version through the BlueOS Versions page?
   • If you turn on Pirate Mode you can select from all the available versions - I recommend trying to install the latest beta image (1.3.0-beta.6)
   • It’s fine to turn Pirate Mode off again once the installation is complete - it only affects the visual interface
2. If that does work, can you then run / install your extensions from that version?

@xiaoliyu

If I can install extensions on myself, please help me

This is technically possible, but we haven’t made any kind of visual interface or streamlined process for it yet.

If you’d like to try doing so I’ve written some quick instructions for a workaround in this comment, but I unfortunately don’t have time to test or flesh them out at the moment, so it might require some online searching and trial and error to get working, especially if you’re unfamiliar with Docker.

[xiaoliyu (Yu Li)]

Thank you very much for your patient reply, I have solved the problem by executing the following steps in the tmux command line in BlueOS: Go to the Raspberry PI home directory (exit docker), then list all Dockers currently, and you will find that cockpit is not running. run the cockpit with the run command, then this problem should not occur. And the effect is sustained, there is no need to repeat the manual operation the next time.