HDDS-13050. Update StartFromDockerHub.md.

[jojochuang]

HDDS-13050. Update StartFromDockerHub.md.

What changes were proposed in this pull request?

Generated-by: Copilot Agent (Preview), prompt:

1. The section "Ozone in a Single Container" is no longer valid with Ozone 2.0 and above. Remove it.
2. Replace the section "Local multi-container cluster" with the following:
Obtain the Docker Compose Configuration First, obtain Ozone's sample Docker Compose configuration:
Download the latest Docker Compose configuration file
curl -O https://raw.githubusercontent.com/apache/ozone-docker/refs/heads/latest/docker-compose.yaml
Start the Cluster Start your Ozone cluster with three Datanodes using the following command:
docker compose up -d --scale datanode=3
This command will:
Automatically pull required images from Docker Hub Create a multi-node cluster with the core Ozone services Start all components in detached mode Verify the Deployment Check the status of your Ozone cluster components:
docker compose ps
You should see output similar to this:
NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS docker-datanode-1 apache/ozone:1.4.1-rocky "/usr/local/bin/dumb…" datanode 14 seconds ago Up 13 seconds 0.0.0.0:32958->9864/tcp, :::32958->9864/tcp docker-datanode-2 apache/ozone:1.4.1-rocky "/usr/local/bin/dumb…" datanode 14 seconds ago Up 13 seconds 0.0.0.0:32957->9864/tcp, :::32957->9864/tcp docker-datanode-3 apache/ozone:1.4.1-rocky "/usr/local/bin/dumb…" datanode 14 seconds ago Up 12 seconds 0.0.0.0:32959->9864/tcp, :::32959->9864/tcp docker-om-1 apache/ozone:1.4.1-rocky "/usr/local/bin/dumb…" om 14 seconds ago Up 13 seconds 0.0.0.0:9874->9874/tcp, :::9874->9874/tcp docker-recon-1 apache/ozone:1.4.1-rocky "/usr/local/bin/dumb…" recon 14 seconds ago Up 13 seconds 0.0.0.0:9888->9888/tcp, :::9888->9888/tcp docker-s3g-1 apache/ozone:1.4.1-rocky "/usr/local/bin/dumb…" s3g 14 seconds ago Up 13 seconds 0.0.0.0:9878->9878/tcp, :::9878->9878/tcp docker-scm-1 apache/ozone:1.4.1-rocky "/usr/local/bin/dumb…" scm 14 seconds ago Up 13 seconds 0.0.0.0:9876->9876/tcp, :::9876->9876/tcp
Check the Ozone version
docker compose exec om bash ozone version
Access the Ozone Recon server, which provides monitoring and management capabilities by navigating to the Recon server home page.
Configuration You can customize your Ozone deployment by modifying the configuration parameters in the docker-compose.yaml file:
Common Configurations: Located under the x-common-config section Service-Specific Settings: Found under the environment section of individual services As an example, to update the port on which Recon listens to, append the following configuration:
x-common-config: ... OZONE-SITE.XML_ozone.recon.http-address: 0.0.0.0:9090
Refer to the Configuring Ozone For Production page for more configuration guidelines.
Next Steps Now that your Ozone cluster is up and running, you can enter any container and explore the environment.
docker compose exec om bash

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/HDDS-13050

How was this patch tested?

User doc

[Copilot]

Pull Request Overview

This PR updates the StartFromDockerHub.md guide to remove outdated single-container instructions and introduce a Docker Compose–based multi-container setup for Ozone 2.0 and above.

• Removed the obsolete “Ozone in a Single Container” section
• Added steps to obtain and use the sample docker-compose.yaml for a three-node cluster
• Included verification commands, configuration tips, and S3 client setup examples

Comments suppressed due to low confidence (2)

hadoop-hdds/docs/content/start/StartFromDockerHub.md:60

• This example block isn’t using the proper Markdown fence. Preface the output with a standalone bash line, then list each container line below, and close with .

```docker-datanode-1   apache/ozone:2.0.0   "/usr/local/bin/dumb…"   datanode   14 seconds ago   Up 13 seconds   0.0.0.0:32958->9864/tcp, :::32958->9864/tcp

hadoop-hdds/docs/content/start/StartFromDockerHub.md:39

• [nitpick] Inconsistent casing: consider using DataNodes (camel case) to match other occurrences of DataNode in the document.

Start your Ozone cluster with three Datanodes using the following command:

[Copilot]

The URL may not resolve correctly using refs/heads. Use the standard raw GitHub path, e.g., https://raw.githubusercontent.com/apache/ozone-docker/latest/docker-compose.yaml.

Suggested change

	curl -O https://raw.githubusercontent.com/apache/ozone-docker/refs/heads/latest/docker-compose.yaml
	curl -O https://raw.githubusercontent.com/apache/ozone-docker/latest/docker-compose.yaml

[chungen0126]

Thanks @jojochuang for working on this. Left some comments.

[jojochuang]

Thanks @chungen0126. Updated.

[chungen0126]

+1 LGTM

[peterxcli]

Thanks @jojochuang for this documentation! LGTM!

[peterxcli]

Thanks @jojochuang for this patch, and @chungen0126 for reviewing!

[peterxcli]

@adoroszlai I was thinking if we need to remove those ai co-authors from merge commit message?

[adoroszlai]

I was thinking if we need to remove those ai co-authors from merge commit message?

I would treat it similar to human contributions. If a significant portion of the patch is generated by AI tools, then yes. If it's just a few minor review items, I wouldn't include it.

However, simple Co-authored-by may not be enough to capture AI contribution in the first case.

See also:
https://www.apache.org/legal/generative-tooling.html