Description

When using upstream' main, podvm-image is failing on s390x when building attestation-agent

Steps to reproduce

Trigger the build pipeline for 0.0 version.

Expected result

No errors.

Actual result

2024-06-21 16:08:25,700 - atomic_reactor.tasks.binary_container_build - INFO - error: failed to run custom build command for `tss-esapi-sys v0.5.0`
2024-06-21 16:08:25,701 - atomic_reactor.tasks.binary_container_build - INFO - 
2024-06-21 16:08:25,701 - atomic_reactor.tasks.binary_container_build - INFO - Caused by:
2024-06-21 16:08:25,701 - atomic_reactor.tasks.binary_container_build - INFO -   process didn't exit successfully: `/remote-source/guest-components/app/guest-components/target/release/build/tss-esapi-sys-8f87f3733c0234a7/build-script-build` (exit status: 101)
2024-06-21 16:08:25,701 - atomic_reactor.tasks.binary_container_build - INFO -   — stderr
2024-06-21 16:09:10,927 - atomic_reactor.tasks.binary_container_build - INFO -   thread 'main' panicked at /remote-source/guest-components/app/vendor/tss-esapi-sys/build.rs:35:17:
2024-06-21 16:09:10,927 - atomic_reactor.tasks.binary_container_build - INFO -   Compilation target (architecture, OS) tuple (s390x, linux) is not part of the supported tuples. Please compile with the "generate-bindings" feature or add support for your platform
2024-06-21 16:09:10,930 - atomic_reactor.tasks.binary_container_build - INFO -   note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2024-06-21 16:09:10,930 - atomic_reactor.tasks.binary_container_build - INFO - warning: build failed, waiting for other jobs to finish...
2024-06-21 16:09:10,930 - atomic_reactor.tasks.binary_container_build - INFO - 
2024-06-21 16:09:10,930 - atomic_reactor.tasks.binary_container_build - ERROR - Error: building at STEP "RUN cargo build --verbose --offline --frozen --release --no-default-features --features "${FEATURES}"": while running runtime: exit status 101 

Impact

This will impact both 0.0 builds but specially 1.7 release.

Additional helpful info

The solution it might be easy, according to stevehorsman, "az-snp-vtpm-attester,az-tdx-vtpm-attester" is not supported in s390x and we could use only "se-attester".

We need to adapt the Dockerfile to modify the features depending on the arch.