-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Folder extensions #2010
Folder extensions #2010
Conversation
@@ -25,8 +25,8 @@ DELTA_JSON = { | |||
'bind': '/etc/dhcpcd.conf', | |||
'mode': 'rw' | |||
}, | |||
"/usr/blueos/userdata": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect this could cause some setups to end up with both /usr/blueos/userdata
and /usr/blueos
bindings. can you check?
6a30ba4
to
b918335
Compare
@Williangalvani you are right, it created a second bind for userdata.
|
b918335
to
8313771
Compare
@Williangalvani @patrickelectric For now, It was uptaded to just create/use a new folder extensions and related settings. Just need to validade, waiting for the blueos image. |
@RaulTrombin is there anything holding this up? It's probably not getting reviews because it's still marked as draft. I'd be keen to get it merged so we can start documenting the recommended location for extensions to store persistent data :-) |
@ES-Alexander it seems almost fine, just need to re-test it. As it also changes the docker bootstrap image/script. Did a test this morning, and it forced a reboot aparently, |
Here I used a fresh stable image, then updated to this PR image. Other than that, it's working.
|
This is expected: any modification to the |
We should probably make it restart only the container, not the host computer, though.. |
This PR able blueos-core to access /usr/blueos/extensions folder.