Add Dockerfile and docs for building Cloudberry Docker Images

[tuhaihe]

Fixes #ISSUE_Number

What does this PR do?

Type of Change

• Bug fix (non-breaking change)
• New feature (non-breaking change)
• Breaking change (fix or feature with breaking changes)
• Documentation update

Breaking Changes

Test Plan

• Unit tests added/updated
• Integration tests added/updated
• Passed make installcheck
• Passed make -C src/test installcheck-cbdb-parallel

Impact

Performance:

User-facing changes:

Dependencies:

Checklist

• Followed contribution guide
• Added/updated documentation
• Reviewed code for security implications
• Requested review from cloudberry committers

Additional Context

CI Skip Instructions

---

[tuhaihe]

Try:

docker build -f devops/build/packaging/docker/Dockerfile.rocky9 -t apache/cloudberry:2.1 .

docker run --rm -it \
  --name cloudberry-db \
  -p 5432:5432 \
  apache/cloudberry:2.1

[tuhaihe]

Hi @leborchuk Could you take a look at this when you have time?

For the 2.1 release, I'm thinking it might be helpful if we provide a single-node Docker image for quick testing and evaluation other than DEB/RPM. In this PR, I added a Dockerfile to build a Cloudberry image based on Rocky Linux 9.

Would love to hear your thoughts on whether this approach makes sense, and if you have any suggestions for improvement.

[leborchuk]

Checked, looks great, I built container on my dev environment and could execute simple queries. That's enough for the simple test )

The only issue I see that my container build ~30 minutes, because of long repository copying and package installations. But the overall approach is good for unexperienced user - just execute commands 1 - by - 1.

I even think we could publish containers like these together with release binaries (in docker registry), so users could just use image with name like apache/incubator-cloudberry:cbdb-simple-rocky9-2.1 and skip a long build stage. But it's just an idea ))

[leborchuk]

cd root directory of cloned main repo, my first launch was from devops/build/packaging/docker/ directory and it of course does not work

[tuhaihe]

I even think we could publish containers like these together with release binaries (in docker registry), so users could just use image with name like apache/incubator-cloudberry:cbdb-simple-rocky9-2.1 and skip a long build stage. But it's just an idea ))

Agree. There is no need for Users to build the image from scratch.