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
In boards.yml file, a "name" needs to be assigned to each master node. This name does not need to contain "master" string in it to work. However, the backup.sh script actually expects the docker container to contain "master" string in it: https://github.com/kernelci/lava-docker/blob/master/backup.sh#L13
One could use yq to parse the boards.yaml file and return the name used for each master node. e.g.:
podman run --rm -i -v "${PWD}":/workdir:rw,Z mikefarah/yq '.masters[].name' < boards.yaml
Would that be something acceptable to run a container inside backup.sh to parse the yaml file?
Ideally we could use docker-compose to run commands for one of the master containers running but I still think we need the name of the container anyways.
Also, this wouldn't work with multiple master nodes but that's a different topic.
The text was updated successfully, but these errors were encountered:
In boards.yml file, a "name" needs to be assigned to each master node. This name does not need to contain "master" string in it to work. However, the backup.sh script actually expects the docker container to contain "master" string in it: https://github.com/kernelci/lava-docker/blob/master/backup.sh#L13
One could use
yq
to parse the boards.yaml file and return the name used for each master node. e.g.:Would that be something acceptable to run a container inside backup.sh to parse the yaml file?
Ideally we could use docker-compose to run commands for one of the master containers running but I still think we need the name of the container anyways.
Also, this wouldn't work with multiple master nodes but that's a different topic.
The text was updated successfully, but these errors were encountered: