Petr Fedchenkov

> I have no issues with that. _what_ we build can be distinct from _where_ we build it. We can have separate tasks, and even use the matrix to run...

I think this is a good enough approach to provide predictable behavior, and we have the same approach now. >it will update the index after each push. But this must...

> 3. `--docker` - did we have any resolution on it? We can try to go with `--docker` for all cases as the first approach. We need this option for...

> > any idea why the build is failing? > > @eriknordmark yes, I do now. It is the very "build dependency" problem that delayed us from moving to this...

> Build is failing, but not where I expected. Didn't you see [this error](https://github.com/lf-edge/eve/runs/8036546626?check_suite_focus=true#step:7:486) before @giggsoff and @rvs ? I see that we are failing on build of arm64 EVE,...

Should we also enable `CONFIG_ARM_RASPBERRYPI_CPUFREQ` to support frequency adjustment?

> Looks like you removed all pushing for release branches. Is that the case? Or does the release branch push happen somewhere else? We will not push non-tagged versions from...

I reworked the PR to not prepare assets on release branch update. We still will make them on tag push event on release branch, it is separate trigger.

As I can see in [domainmgr.go](https://github.com/lf-edge/eve/blob/8e65a16ff2ebd7ef5d88c03bc395e006e707bcb4/pkg/pillar/cmd/domainmgr/domainmgr.go#L1721) it is disagreement between the container configuration (loaded from dockerhub) and the configuration loaded through zedcloud in the number of mounted drives. As a...

@zededa-yuri thanks for recommendations, modified.