Hi Denis While it is a good catch and interesting question why amd64 images seem to be missing on dockerhub, in the release process, pypi and docker images are only published after the vote. Also, going back to discussions we had very early before doing our first releases, it is only the source release that is in scope for the approval by vote, the files in the pypi/ folder are often refered to as "convenience binaries". In practice, of course we would like to fix them too if any problems are found.
On the docker side however, the release doc doesn't include anything before the very last steps after the release: https://github.com/apache/otava/blob/master/docs/RELEASE.md#publish-docker-image If there's a problem that can and should be fixed before the source release, then we should, but I assume in this case it is the docs that are correct and something with Docker is wrong? There are warnings in the github action that builds docker:latest https://github.com/apache/otava/actions/runs/24409465328/job/71311592776#step:7:4582 ...but other than that, our docs mostly seem to use docker-compose. Can you be more specific about which documented example is failing? For the purpose of this thread I'd like to confirm or deny whether the problem is something that we can fix in the docs, or whether releasing a correct (x86) image after the release is all that is needed? Alex? On Sat, Apr 18, 2026 at 11:56 PM Denis Shchepakin < [email protected]> wrote: > -1 > > [x] Download links are valid. > [x] Checksums and signatures. > [x] LICENSE/NOTICE files exist. > [x] No unexpected binary files. > [x] All source files have ASF headers. > [x] Can install from source. > [] Can run examples using all supported Python versions. > > Docker examples fail on amd64 (CSV, GRAFANA, GRAPHITE, POSTGRESQL). The > image `apache/otava:latest` only provides arm64: > ``` > λ docker manifest inspect apache/otava:latest > { > "schemaVersion": 2, > "mediaType": "application/vnd.oci.image.index.v1+json", > "manifests": [ > { > "mediaType": "application/vnd.oci.image.manifest.v1+json", > "size": 2010, > "digest": > "sha256:0ebae11752f6437cc872ebd604c32d137c5e8dfbb9239dac2227e8c141eadb5c", > "platform": { > "architecture": "arm64", > "os": "linux" > } > }, > { > "mediaType": "application/vnd.oci.image.manifest.v1+json", > "size": 566, > "digest": > "sha256:c59b63ac575921f88a0edd85a00fb33be4e44dde77a5d7f9242a1b932b9b2c0d", > "platform": { > "architecture": "unknown", > "os": "unknown" > } > } > ] > } > ``` > > Best, > Denis > > On Tue, Apr 14, 2026 at 12:47 PM Henrik Ingo <[email protected]> wrote: > > > Hello everyone, > > > > Please review and vote for the releasing Apache Otava (incubating) > > 0.8.0-incubating-rc1. > > > > Changelog for this release candidate > > > > > https://github.com/apache/otava/compare/0.7.0-incubating...0.8.0-incubating-rc1 > > > > > > The official Apache source release has been deployed to > > > > > https://dist.apache.org/repos/dist/release/incubator/otava/0.8.0-incubating-rc1/release > > > > GH tag for release > > > https://github.com/apache/otava/releases/tag/0.8.0-incubating-rc1/release > > The release has been signed with a key > > 1FD435072D02D8745B0ACD15FC59E3D12243411B > > available here https://downloads.apache.org/incubator/otava/KEYS > > > > Please download, verify, and test. > > > > Please vote on releasing this candidate by replying with: > > [ ] +1 Release this package > > [ ] 0 No opinion > > [ ] -1 Do not release (please provide reason) > > > > To learn more about Apache Otava, please see https://otava.apache.org > > > > This vote will be open for at least 72 hours. > > > > Checklist for reference: > > [ ] Download links are valid. > > [ ] Checksums and signatures. > > [ ] LICENSE/NOTICE files exist. > > [ ] No unexpected binary files. > > [ ] All source files have ASF headers. > > [ ] Can install from source. > > [ ] Can run examples using all supported Python versions. > > > -- *nyrkio.com <http://nyrkio.com/>* ~ *Continuous Benchmarking as a Service* Henrik Ingo, CEO [email protected] LinkedIn: www.linkedin.com/in/heingo +358 40 569 7354 Twitter: twitter.com/h_ingo
