# Automatically loading extensions settings from Docker file permissions label

**URL:** <https://discuss.bluerobotics.com/t/automatically-loading-extensions-settings-from-docker-file-permissions-label/22661>\
**Category:** BlueOS\
**Tags:** blueos, extensions\
**Created:** [March 20, 2026, 11:16am UTC](https://discuss.bluerobotics.com/t/automatically-loading-extensions-settings-from-docker-file-permissions-label/22661 "2026-03-20T11:16:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rutger-seascape](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/rutger-seascape/32/17285_2.png) [@rutger-seascape](https://discuss.bluerobotics.com/u/rutger-seascape)\
**Post date:** [March 20, 2026, 11:16am UTC](https://discuss.bluerobotics.com/t/automatically-loading-extensions-settings-from-docker-file-permissions-label/22661/1 "2026-03-20T11:16:46Z")

</div>

Hey,

I was wondering if the settings should be automatically loaded based on the Dockerfile “permissions“ label or if this is not the case. When I manually set the settings in the Create Extension → Original Settings field it works but manually.

Kind regards,  
Rutger

---

<div class="post-metadata">

**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\
**Post date:** [March 20, 2026, 7:16pm UTC](https://discuss.bluerobotics.com/t/automatically-loading-extensions-settings-from-docker-file-permissions-label/22661/2 "2026-03-20T19:16:38Z")

</div>

Hi @rutger-seascape, welcome to the forum 🙂

> [@rutger-seascape](#):
>
> I was wondering if the settings should be automatically loaded based on the Dockerfile “permissions“ label or if this is not the case.

If I’m understanding your question correctly, no, BlueOS does not automatically fetch information from Docker image labels of manually installed Extensions.

For the Extensions listed on the store, settings from the `permissions` label are extracted and included in the manifest file that lists all the available Extensions, which is how BlueOS knows about them. For manual Extensions the Docker image needs to be fetched from wherever you’ve specified before any tags could be read, and that image isn’t fetched until after you’ve “created” the Extension.

I believe we could (and probably should) try to automatically fetch those details, but that is not currently being done. That would be especially relevant during installation, if the “original settings” are left blank, but ideally would also be enabled with some kind of fetch operation during setup. I’ve raised [this Issue](https://github.com/bluerobotics/BlueOS/issues/3842) to suggest that (and track progress going forward), though I’m not sure when someone will have a chance to work on it.

---

<div class="post-metadata">

**Author:** ![rutger-seascape](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/rutger-seascape/32/17285_2.png) [@rutger-seascape](https://discuss.bluerobotics.com/u/rutger-seascape)\
**Post date:** [March 23, 2026, 11:12am UTC](https://discuss.bluerobotics.com/t/automatically-loading-extensions-settings-from-docker-file-permissions-label/22661/3 "2026-03-23T11:12:06Z")

</div>

Hey Eliot,

Thanks for your reply! Yes, you understood my question perfectly. Ahh that’s good to know, thanks for your fast reply and being so proactive 😃

I tried the BlueOS 1.5 beta and the permissions label is read automatically there when you upload a .tar file, which works great for us.

Thanks again.
