cc @Yikun , @dongjoon-hyun

From my side, it's a little weird that Docker Hub requires us to change our repo. Both images are independent basically, aren't they? Given that (1) exists without (2), I prefer to change (1) only because it's a breaking change to change underlying OSes.

1. https://hub.docker.com/_/spark/tags
2. https://hub.docker.com/r/apache/spark/

I'm ok with this proposal as well. We could add -jammy versions of https://github.com/apache/spark-docker/tree/master/3.5.7 to the repo and publish only those to docker library.

@Yikun, @HyukjinKwon , I wonder if you have any idea how to publish 3.5.7 and future 3.5 releases to docker library?

I think we can:

For 3.5.7:

1. Change the base image in codebase (3.5.7 and future release).

2. apache image no need to publish again (which @dongjoon-hyun mentioned) I'm also OK.

3. Publish Docker hub official image via submit PR.

For future release:

We can publish both two image from new code.

Allright, thanks for the feedback @dongjoon-hyun and @Yikun.

In that case is there anything I need to change in this PR? Once this PR is merged I can update https://github.com/docker-library/official-images/pull/19948/files with the new commit hash. But we will not rerun Publish action for 3.5.7 here. Actually shall I increase the version in https://github.com/apache/spark-docker/blob/master/.github/workflows/publish.yml#L28-L31 now to prevent accidental 3.5.7 republish to Apache?

Publish image action is triggered by manually. so I think this PR is OK to go, and do doi refresh after PR merged.

And better to see is there any other comments from @dongjoon-hyun

Thanks for the review @dongjoon-hyun , @Yikun !

Merged to master.