When we set a template for custom device type with
"lavacli device-types template set" command, it ends up in one container
on docker-compose system, but actually also expected in others. This is
a known upstream issue tracked as
https://git.lavasoftware.org/lava/pkg/docker-compose/-/issues/4.
We work it around for now by pushing the file manually to "another"
container. Currently, this applies to "musca_a" device type, but care
should be taken to apply the same workaround to other introduced custom
device types.
When we set a template for custom device type with "lavacli device-types template set" command, it ends up in one container on docker-compose system, but actually also expected in others. This is a known upstream issue tracked as https://git.lavasoftware.org/lava/pkg/docker-compose/-/issues/4.
We work it around for now by pushing the file manually to "another" container. Currently, this applies to "musca_a" device type, but care should be taken to apply the same workaround to other introduced custom device types.
Signed-off-by: Paul Sokolovsky paul.sokolovsky@linaro.org