Docker Hub images not updated since v0.56.2 (~3 weeks ago)

[angelsocastro]

Docker Hub images for inkeep/agents-api, inkeep/agents-manage-ui, and inkeep/agents-migrate haven't been updated since v0.56.2, while GitHub releases are now at v0.59.2.

It looks like PR #2477 was meant to automate Docker image publishing as part of the release workflow, but it was automatically closed as stale last week without being merged.

For those self-hosting via Docker Compose, this means we're stuck 3 minor versions behind and can't get recent fixes (security patches, bug fixes, etc.).

Could you reopen/merge #2477 or do a manual publish of the latest images to Docker Hub?

Thanks!

[pullfrog]

  ^{｜ Build this ➔ ｜ Make a plan ➔}

[robert-inkeep]

hi @angelsocastro i will do a manual update today, but i've been working on automating the docker publish step

[angelsocastro]

Hi @robert-inkeep, thanks for the quick update!

However, inkeep/agents-manage-ui:0.59.4 is missing the linux/amd64 manifest — it only has linux/arm64. This breaks deployments on amd64 servers with:

no matching manifest for linux/amd64 in the manifest list entries

Could you republish with multi-arch (amd64 + arm64)? The PR #2477 had this covered with QEMU + Buildx.

Thanks!

[JiwaniZakir]

The root cause here is straightforward: the Docker Hub publish step was gated behind PR #2477 (likely adding it to the release CI workflow), and since that PR was closed as stale without merging, the automated image push never runs on new releases. Worth checking .github/workflows/release.yml (or equivalent) to confirm there's no docker push step present — if the workflow only builds/tags the GitHub release but never calls docker buildx push, images will silently fall behind regardless of how many releases get cut. A manual docker buildx build --push targeting v0.59.2 for each of the three images would unblock self-hosters in the short term while the workflow fix is re-evaluated.