damondouglas commented on issue #33744: URL: https://github.com/apache/beam/issues/33744#issuecomment-2611007478
> Hey [@damondouglas](https://github.com/damondouglas), I see [#33703](https://github.com/apache/beam/pull/33703) was for Java. Is this Python failure related in any way? The source of the error is with [sdks/python/container/Dockerfile](https://github.com/apache/beam/blob/master/sdks/python/container/Dockerfile) as [sdks/python/container/distroless/common.gradle](https://github.com/apache/beam/blob/b82bde87572b5e2b8f5cebe09aec6373de22b818/sdks/python/container/distroless/common.gradle) configures [`dockerPrepare.dependsOn ":sdks:python:container:py${pythonVersionSuffix}:docker"`](https://github.com/apache/beam/blob/b82bde87572b5e2b8f5cebe09aec6373de22b818/sdks/python/container/distroless/common.gradle#L52). The fact that switching GitHub hosted vs the self-hosted runner suggests that there might be something with the underlying architecture of the machine types. The fact that we see `buildkit_qemu_emulator` in the https://github.com/apache/beam/actions/runs/12933159540/job/36071120448 logs suggests that this might be the case. Long term, I suggest we perform all of our container image builds using Google Cloud Build, triggered by GitHub actions for the following reasons: 1) Cloud Build triggers may be manually triggered outside the context of a GitHub action making this process easier to test and troubleshoot 2) We can assume a consistent underlying architecture within which container images are built. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
