So you’re aware, we’re planning for BlueOS to be both re-skinnable and extensible in future without needing to create a custom fork of it, which should allow for easy customisations while still maintaining the standard upgrade process, without relying on a fork author to pull updates downstream and host their own core images. Once those features are fully enabled the hope is that custom forks will not be necessary (since they fragment the code and user-base), and where possible we intend to work with interested developers to ensure the BlueOS architecture and system meets their needs.
If there are particular aspects you’re interested in being able to change, please let us know so we can take them into account as we flesh out the extension system, and/or so we can work together to make your desired changes possible
This isn’t related to docker or your code; we have the same errors. It seems one of our linters got some updates that is raising some new issues with existing code.
I’ve raised a pull request to fix it on our end, so you can either wait for that to be revised (if necessary) and merged before pulling them into your repo, or you can cherry-pick/copy those changes to your repository to at least resolve the errors for now