You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to setup a fresh Leda installation for my specific use case. This involves adding further files which should be mounted by some of the executed containers. One example would be an JSON-file with an extended vehicle model to by mounted by the Kuksa.Val databroker container.
Or is there another "Leda-way" to get such files to the Leda host-system without the need to build a new custom Leda image and apply it through the VUM and Self-Update-Agent?
The text was updated successfully, but these errors were encountered:
Hi, @eriksven
As mentioned in #42, we are still waiting on the updated version of VUM to get an OSS release and such updates should ideally be handled through the desired state manifest.
That said, the Leda Distro Quickstart Images (esp. the 0.1.0+ releases) are supposed to be a development environment, so from my point of view it is okay to ssh/scp files to the /data partition as needed. For example you can add your extended vehicle model JSON inside a custom directory under /data and then update the databroker manifest accordingly (should be automatically picked-up and re-deployed on change).
Hello,
I would like to setup a fresh Leda installation for my specific use case. This involves adding further files which should be mounted by some of the executed containers. One example would be an JSON-file with an extended vehicle model to by mounted by the Kuksa.Val databroker container.
Is there a way to include such files or the download of such files in the desired state configuration one can send to the VUM (https://eclipse-leda.github.io/leda/docs/device-provisioning/vehicle-update-manager/)?
Or is there another "Leda-way" to get such files to the Leda host-system without the need to build a new custom Leda image and apply it through the VUM and Self-Update-Agent?
The text was updated successfully, but these errors were encountered: