[docs] Refactor the document of deploying-with-docker.md to use advertised.listeners (#1075)

Author: loserwang1024

website/docs/install-deploy/deploying-with-docker.md

@@ -81,7 +81,9 @@ docker run \
     --name coordinator-server \
     --network=fluss-demo \
     --env FLUSS_PROPERTIES="zookeeper.address: zookeeper:2181
-bind.listeners: FLUSS://coordinator-server:9123" \
+bind.listeners: FLUSS://coordinator-server:9123
+advertised.listeners: FLUSS://localhost:9123
+" \
     -p 9123:9123 \
     -d fluss/fluss:$FLUSS_VERSION$ coordinatorServer
 ```
@@ -101,6 +103,7 @@ docker run \
     --network=fluss-demo \
     --env FLUSS_PROPERTIES="zookeeper.address: zookeeper:2181
 bind.listeners: FLUSS://tablet-server:9124
+advertised.listeners: FLUSS://localhost:9124
 tablet-server.id: 0
 data.dir: /tmp/fluss/data
 remote.data.dir: /tmp/fluss/remote-data" \
@@ -121,6 +124,7 @@ docker run \
     --network=fluss-demo \
     --env FLUSS_PROPERTIES="zookeeper.address: zookeeper:2181
 bind.listeners: FLUSS://tablet-server-0:9124
+advertised.listeners: FLUSS://localhost:9124
 tablet-server.id: 0
 data.dir: /tmp/fluss/data/tablet-server-0
 remote.data.dir: /tmp/fluss/remote-data" \
@@ -136,6 +140,7 @@ docker run \
     --network=fluss-demo \
     --env FLUSS_PROPERTIES="zookeeper.address: zookeeper:2181
 bind.listeners: FLUSS://tablet-server-1:9125
+advertised.listeners: FLUSS://localhost:9125
 tablet-server.id: 1
 data.dir: /tmp/fluss/data/tablet-server-1
 remote.data.dir: /tmp/fluss/remote-data" \
@@ -151,6 +156,7 @@ docker run \
     --network=fluss-demo \
     --env FLUSS_PROPERTIES="zookeeper.address: zookeeper:2181
 bind.listeners: FLUSS://tablet-server-2:9126
+advertised.listeners: FLUSS://localhost:9126
 tablet-server.id: 2
 data.dir: /tmp/fluss/data/tablet-server-2
 remote.data.dir: /tmp/fluss/remote-data" \
@@ -167,67 +173,6 @@ Run the below command to check the Fluss cluster status:
 docker container ls -a
 ```
 
-### Interacting with Fluss
-
-After the Fluss cluster is started, you can use **Fluss Client** (e.g., Flink SQL Client) to interact with Fluss.
-The following subsections will show you how to use 'Docker' to build a Flink cluster and use **Flink SQL Client**
-to interact with Fluss.
-
-#### Start Flink Cluster
-
-1. Start jobManager
-
-```bash
-docker run \
-    --name jobmanager \
-    --network=fluss-demo \
-    --env FLINK_PROPERTIES=" jobmanager.rpc.address: jobmanager" \
-    -p 8083:8081 \
-    --volume shared-tmpfs:/tmp/fluss \
-    -d fluss/quickstart-flink:1.20-$FLUSS_VERSION_SHORT$ jobmanager
-```
-
-2. Start taskManager
-
-```bash
-docker run \
-    --name taskmanager \
-    --network=fluss-demo \
-    --env FLINK_PROPERTIES=" jobmanager.rpc.address: jobmanager" \
-    --volume shared-tmpfs:/tmp/fluss \
-    -d fluss/quickstart-flink:1.20-$FLUSS_VERSION_SHORT$ taskmanager
-```
-
-#### Enter into SQL-Client
-First, use the following command to enter pod:
-```shell
-docker exec -it jobmanager /bin/bash
-```
-
-Then, use the following command to enter the Flink SQL CLI Container:
-```shell
-./sql-client
-```
-
-#### Create Fluss Catalog
-
-Use the following SQL to create a Fluss catalog:
-```sql title="Flink SQL"
-CREATE CATALOG fluss_catalog WITH (
-    'type' = 'fluss',
-    'bootstrap.servers' = 'coordinator-server:9123'
-);
-```
-
-```sql title="Flink SQL"
-USE CATALOG fluss_catalog;
-```
-
-#### Do more with Fluss
-
-After the catalog is created, you can use Flink SQL Client to do more with Fluss, for example, create a table, insert data, query data, etc.
-More details please refer to [Flink Getting started](engine-flink/getting-started.md)
-
 ## Deploy with Docker Compose
 
 The following is a brief overview of how to quickly create a complete Fluss testing cluster
@@ -249,8 +194,12 @@ services:
       - |
         FLUSS_PROPERTIES=
         zookeeper.address: zookeeper:2181
-        bind.listeners: FLUSS://coordinator-server:9123
+        bind.listeners: INTERNAL://coordinator-server:0, CLIENT://coordinator-server:9123
+        advertised.listeners: CLIENT://localhost:9123
+        internal.listener.name: INTERNAL
         remote.data.dir: /tmp/fluss/remote-data
+    ports:
+      - "9123:9123"
   tablet-server:
     image: fluss/fluss:$FLUSS_VERSION$
     command: tabletServer
@@ -260,11 +209,15 @@ services:
       - |
         FLUSS_PROPERTIES=
         zookeeper.address: zookeeper:2181
-        bind.listeners: FLUSS://tablet-server:9123
+        bind.listeners: INTERNAL://tablet-server:0, CLIENT://tablet-server:9123
+        advertised.listeners: CLIENT://localhost:9124
+        internal.listener.name: INTERNAL
         tablet-server.id: 0
         kv.snapshot.interval: 0s
         data.dir: /tmp/fluss/data
         remote.data.dir: /tmp/fluss/remote-data
+    ports:
+        - "9124:9123"
     volumes:
       - shared-tmpfs:/tmp/fluss
   zookeeper:
@@ -294,8 +247,12 @@ services:
       - |
         FLUSS_PROPERTIES=
         zookeeper.address: zookeeper:2181
-        bind.listeners: FLUSS://coordinator-server:9123
+        bind.listeners: INTERNAL://coordinator-server:0, CLIENT://coordinator-server:9123
+        advertised.listeners: CLIENT://localhost:9123
+        internal.listener.name: INTERNAL
         remote.data.dir: /tmp/fluss/remote-data
+    ports:
+      - "9123:9123"
   tablet-server-0:
     image: fluss/fluss:$FLUSS_VERSION$
     command: tabletServer
@@ -305,11 +262,15 @@ services:
       - |
         FLUSS_PROPERTIES=
         zookeeper.address: zookeeper:2181
-        bind.listeners: FLUSS://tablet-server-0:9123
+        bind.listeners: INTERNAL://tablet-server-0:0, CLIENT://tablet-server-0:9123
+        advertised.listeners: CLIENT://localhost:9124
+        internal.listener.name: INTERNAL
         tablet-server.id: 0
         kv.snapshot.interval: 0s
         data.dir: /tmp/fluss/data/tablet-server-0
         remote.data.dir: /tmp/fluss/remote-data
+    ports:
+      - "9124:9123"
     volumes:
       - shared-tmpfs:/tmp/fluss
   tablet-server-1:
@@ -321,11 +282,15 @@ services:
       - |
         FLUSS_PROPERTIES=
         zookeeper.address: zookeeper:2181
-        bind.listeners: FLUSS://tablet-server-1:9123
+        bind.listeners: INTERNAL://tablet-server-1:0, CLIENT://tablet-server-1:9123
+        advertised.listeners: CLIENT://localhost:9125
+        internal.listener.name: INTERNAL
         tablet-server.id: 1
         kv.snapshot.interval: 0s
         data.dir: /tmp/fluss/data/tablet-server-1
         remote.data.dir: /tmp/fluss/remote-data
+    ports:
+      - "9125:9123"
     volumes:
       - shared-tmpfs:/tmp/fluss
   tablet-server-2:
@@ -337,11 +302,15 @@ services:
       - |
         FLUSS_PROPERTIES=
         zookeeper.address: zookeeper:2181
-        bind.listeners: FLUSS://tablet-server-2:9123
+        bind.listeners: INTERNAL://tablet-server-2:0, CLIENT://tablet-server-2:9123
+        advertised.listeners: CLIENT://localhost:9126
+        internal.listener.name: INTERNAL
         tablet-server.id: 2
         kv.snapshot.interval: 0s
         data.dir: /tmp/fluss/data/tablet-server-2
         remote.data.dir: /tmp/fluss/remote-data
+    ports:
+      - "9126:9123"
     volumes:
       - shared-tmpfs:/tmp/fluss
   zookeeper:
@@ -367,127 +336,42 @@ Run the below command to check the container status:
 docker container ls -a
 ```
 
-### Interacting with Fluss
+## Interacting with Fluss
 
-If you want to interact with this Fluss cluster, you can change the `docker-compose.yml` file to add a Flink cluster.
-The changed `docker-compose.yml` file is as follows:
+After the Fluss cluster is started, you can use **Fluss Client** (e.g., Flink SQL Client) to interact with Fluss.
+The following subsections will show you how to use 'Docker' to build a Flink cluster and use **Flink SQL Client**
+to interact with Fluss.
 
-```yaml
-services:
-  coordinator-server:
-    image: fluss/fluss:$FLUSS_VERSION$
-    command: coordinatorServer
-    depends_on:
-      - zookeeper
-    environment:
-      - |
-        FLUSS_PROPERTIES=
-        zookeeper.address: zookeeper:2181
-        bind.listeners: FLUSS://coordinator-server:9123
-        remote.data.dir: /tmp/fluss/remote-data
-  tablet-server-0:
-    image: fluss/fluss:$FLUSS_VERSION$
-    command: tabletServer
-    depends_on:
-      - coordinator-server
-    environment:
-      - |
-        FLUSS_PROPERTIES=
-        zookeeper.address: zookeeper:2181
-        bind.listeners: FLUSS://tablet-server-0:9123
-        tablet-server.id: 0
-        kv.snapshot.interval: 0s
-        data.dir: /tmp/fluss/data/tablet-server-0
-        remote.data.dir: /tmp/fluss/remote-data
-    volumes:
-      - shared-tmpfs:/tmp/fluss
-  tablet-server-1:
-    image: fluss/fluss:$FLUSS_VERSION$
-    command: tabletServer
-    depends_on:
-      - coordinator-server
-    environment:
-      - |
-        FLUSS_PROPERTIES=
-        zookeeper.address: zookeeper:2181
-        bind.listeners: FLUSS://tablet-server-1:9123
-        tablet-server.id: 1
-        kv.snapshot.interval: 0s
-        data.dir: /tmp/fluss/data/tablet-server-1
-        remote.data.dir: /tmp/fluss/remote-data
-    volumes:
-      - shared-tmpfs:/tmp/fluss
-  tablet-server-2:
-    image: fluss/fluss:$FLUSS_VERSION$
-    command: tabletServer
-    depends_on:
-      - coordinator-server
-    environment:
-      - |
-        FLUSS_PROPERTIES=
-        zookeeper.address: zookeeper:2181
-        bind.listeners: FLUSS://tablet-server-2:9123
-        tablet-server.id: 2
-        kv.snapshot.interval: 0s
-        data.dir: /tmp/fluss/data/tablet-server-2
-        remote.data.dir: /tmp/fluss/remote-data
-    volumes:
-      - shared-tmpfs:/tmp/fluss
-  zookeeper:
-    restart: always
-    image: zookeeper:3.9.2
-  jobmanager:
-    image: fluss/quickstart-flink:1.20-$FLUSS_VERSION_SHORT$
-    ports:
-      - "8083:8081"
-    command: jobmanager
-    environment:
-      - |
-        FLINK_PROPERTIES=
-        jobmanager.rpc.address: jobmanager
-    volumes:
-      - shared-tmpfs:/tmp/fluss
-  taskmanager:
-    image: fluss/quickstart-flink:1.20-$FLUSS_VERSION_SHORT$
-    depends_on:
-      - jobmanager
-    command: taskmanager
-    environment:
-      - |
-        FLINK_PROPERTIES=
-        jobmanager.rpc.address: jobmanager
-    volumes:
-      - shared-tmpfs:/tmp/fluss
+#### Start Flink Cluster
+You can start a Flink standalone cluster refer to [Flink Environment Preparation](engine-flink/getting-started.md#preparation-when-using-flink-sql-client)
 
-volumes:
-  shared-tmpfs:
-    driver: local
-    driver_opts:
-      type: "tmpfs"
-      device: "tmpfs"
+**Note**: Make sure the [Fluss connector jar](/downloads/) already has copied to the `lib` directory of your Flink home.
+```shell
+bin/start-cluster.sh 
 ```
-Save the `docker-compose.yaml` script and execute the `docker-compose up -d` command in the same directory to create the cluster.
 
-#### Enter into SQL-Client
-First, use the following command to enter the Flink SQL CLI Container:
+
+### Enter into SQL-Client
+Use the following command to enter the Flink SQL CLI Container:
 ```shell
-docker compose exec jobmanager ./sql-client
+./sql-client
 ```
 
-#### Create Fluss Catalog
+### Create Fluss Catalog
+
 Use the following SQL to create a Fluss catalog:
 ```sql title="Flink SQL"
 CREATE CATALOG fluss_catalog WITH (
     'type' = 'fluss',
-    'bootstrap.servers' = 'coordinator-server:9123'
+    'bootstrap.servers' = 'localhost:9123'
 );
 ```
 
 ```sql title="Flink SQL"
 USE CATALOG fluss_catalog;
 ```
 
-#### Do more with Fluss
+### Do more with Fluss
 
 After the catalog is created, you can use Flink SQL Client to do more with Fluss, for example, create a table, insert data, query data, etc.
-More details please refer to [Flink Getting started](engine-flink/getting-started.md)
+More details please refer to [Flink Getting started](engine-flink/getting-started.md)