Repository navigation
Infra: 'iceberg-rest-fixture' Docker image not published since 2026-04-29 #18877
Description
Feature Request / Improvement
The apache/iceberg-rest-fixture Docker image has not been published since 2026-04-29.
- The workflow
publish-iceberg-rest-fixture-docker.ymlhas the statedisabled_manually. Its last run was on 2026-04-29, and that run was successful. - This workflow publishes the nightly
latesttag and the release tags. On Docker Hub,latestis from 2026-04-29, and the newest version tag is1.10.1. The releases 1.10.2, 1.11.0, and 1.12.0 have no image.
Other projects test their REST clients against this image. For example, PyIceberg runs its integration tests against apache/iceberg-rest-fixture:latest. These tests do not include the fixture changes merged since April, such as #18047 (include-labels). PyIceberg needs #18047 for a labels integration test (apache/iceberg-python#4320, apache/iceberg-python#4321).
Could a committer enable the workflow again and run it once with workflow_dispatch? If the workflow is disabled on purpose, for example because of the QEMU build failures in #15943, please tell us the reason, so that the client projects can plan their tests.
Query engine
None
Willingness to contribute
- I can contribute this improvement/feature independently
- I would be willing to contribute this improvement/feature with guidance from the Iceberg community
- I cannot contribute this improvement/feature at this time
Activity
Fokko commentedon Nov 10, 2026
@yayaha Not sure why this was disabled.
I've just enabled the workflow, triggered it: https://github.com/apache/iceberg/actions/runs/42892019527
stevenzwu commentedon Nov 10, 2026
I thought it was disabled due to license notice issue
kevinjqliu commentedon Nov 10, 2026
yea it was paused so we can update the LICENSE and NOTICE files the image carries. We should fix it up, its been on my todo list
kevinjqliu commentedon Nov 10, 2026
Found the original discussion: the Docker publishing workflow was explicitly disabled due to incorrect LICENSE documentation. The agreed follow-up plan was to update the packaging, prune dependencies, and fix LICENSE/NOTICE before re-enabling it.
I opened a follow-up PR to replace the shaded runtime JAR with staged runtime dependencies, but it was closed due to inactivity. That PR addresses the packaging change; dependency pruning and LICENSE/NOTICE corrections still need to follow.
Fokko commentedon Nov 11, 2026
Thanks for the context @stevenzwu and @kevinjqliu, let's follow up on these issues, since it would be great to have this workflow back up and running. This simplifies testing in the other implementation, and makes the tests much more robust.
raphaelauv commentedon Nov 13, 2026
duplicate of #18421