Add qemu-system-aarch64 and sshpass to docker image

[lurtz]

These tools are needed to run disk images and interact with them via e.g. bazel using ssh.

[AlexanderLanin]

I can approve this, but please keep in mind that all tools should be provided by bazel.
For example CI will run via bazel and not via devcontainer.

At least that's the current approach.

[lurtz]

I can approve this, but please keep in mind that all tools should be provided by bazel. For example CI will run via bazel and not via devcontainer.

At least that's the current approach.

How do you make sure that the tools downloaded via bazel are compatible with the host / environment in which they are run?

[lurtz]

Does this also mean you oppose changes like this eclipse-score/communication#26 ?

[AlexanderLanin]

How do you make sure that the tools downloaded via bazel are compatible with the host / environment in which they are run?

We define separate executables per environment: https://github.com/eclipse-score/tooling/blob/b8e741b7a7d2cc80999eb61dff58f6abbec1319a/tools/ruff.lock.json

[AlexanderLanin]

Does this also mean you oppose changes like this eclipse-score/communication#26 ?

It's not that I oppose them, it's that we are not aligned in the project. Let's make that a dedicated topic in the infrastructure community.

Our concept so far was to use pure bazel in CI. However, due to performance reasons (and effort) we have partially abandoned that already. example