During the release process, 4.x needs a new docker image created tika-grpc

[Nicholas DiPiazza <ni...@gmail.com>]

When tika is released, we will need to do all the usual, but then there's a
new image:

https://github.com/apache/tika-grpc-docker

@lewis john mcgibbney <le...@apache.org>  i saw you were doing docker
things.

Re: During the release process, 4.x needs a new docker image created tika-grpc

[Nicholas DiPiazza <ni...@gmail.com>]

Sorry Sent that too fast let me try again.

When tika is released, we will need to do all the usual, but then there's a
new image:

https://github.com/apache/tika-grpc-docker

@lewis john mcgibbney <le...@apache.org> I saw you were doing docker
things.

If we can guarantee the images are repeatable with respect to
https://issues.apache.org/jira/browse/TIKA-4590
then I believe we can deprecate the separate docker github repositories and
replace them with typical Dockerfile content within the Java application.
This allows the build process to create and publish Docker images tagged
with the release during the deploy phase, using common libraries.

Should I start making changes to switch to the github actions triggering
the docker images to be built?

On Wed, Mar 11, 2026 at 11:30 AM Nicholas DiPiazza <
nicholas.dipiazza@gmail.com> wrote:

> When tika is released, we will need to do all the usual, but then there's
> a new image:
>
> https://github.com/apache/tika-grpc-docker
>
> @lewis john mcgibbney <le...@apache.org>  i saw you were doing docker
> things.
>
>
>