Merge pull request #46159 from ClickHouse/docker-server-readme

Fix clickhouse/clickhouse-server description to make it in sync

docker/server/README.md

@@ -2,23 +2,30 @@
 
 ## What is ClickHouse?
 
-We are the creators of the popular open-source column-oriented DBMS (columnar database management system) for online analytical processing (OLAP) which allows users to generate analytical reports using SQL queries in real-time.
+ClickHouse is an open-source column-oriented DBMS (columnar database management system) for online analytical processing (OLAP) that allows users to generate analytical reports using SQL queries in real-time.
 
 ClickHouse works 100-1000x faster than traditional database management systems, and processes hundreds of millions to over a billion rows and tens of gigabytes of data per server per second.  With a widespread user base around the globe, the technology has received praise for its reliability, ease of use, and fault tolerance.
 
 For more information and documentation see https://clickhouse.com/.
 
+## Versions
+
+- The `latest` tag points to the latest release of the latest stable branch.
+- Branch tags like `22.2` point to the latest release of the corresponding branch.
+- Full version tags like `22.2.3.5` point to the corresponding release.
+- The tag `head` is built from the latest commit to the default branch.
+- Each tag has optional `-alpine` suffix to reflect that it's built on top of `alpine`.
+
 ## How to use this image
 
 ### start server instance
-
 ```bash
 docker run -d --name some-clickhouse-server --ulimit nofile=262144:262144 clickhouse/clickhouse-server
 ```
 
 By default, ClickHouse will be accessible only via the Docker network. See the [networking section below](#networking).
 
-By default, starting above server instance will be run as the `default` user without a password.
+By default, starting above server instance will be run as the `default` user without  password.
 
 ### connect to it from a native client
 
@@ -36,7 +43,7 @@ More information about the [ClickHouse client](https://clickhouse.com/docs/en/in
 echo "SELECT 'Hello, ClickHouse!'" | docker run -i --rm --link some-clickhouse-server:clickhouse-server curlimages/curl 'http://clickhouse-server:8123/?query=' -s --data-binary @-
 ```
 
-More information about [ClickHouse HTTP Interface](https://clickhouse.com/docs/en/interfaces/http/).
+More information about the [ClickHouse HTTP Interface](https://clickhouse.com/docs/en/interfaces/http/).
 
 ### stopping / removing the container
 
@@ -54,7 +61,7 @@ docker run -d -p 18123:8123 -p19000:9000 --name some-clickhouse-server --ulimit
 echo 'SELECT version()' | curl 'http://localhost:18123/' --data-binary @-
 ```
 
-```response
+```
 22.6.3.35
 ```
 
@@ -65,7 +72,7 @@ docker run -d --network=host --name some-clickhouse-server --ulimit nofile=26214
 echo 'SELECT version()' | curl 'http://localhost:8123/' --data-binary @-
 ```
 
-```response
+```
 22.6.3.35
 ```
 
@@ -93,7 +100,7 @@ You may also want to mount:
 
 ClickHouse has some advanced functionality, which requires enabling several [Linux capabilities](https://man7.org/linux/man-pages/man7/capabilities.7.html).
 
-These are optional and can be enabled using the following [docker command-line arguments](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities):
+They are optional and can be enabled using the following [docker command-line arguments](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities):
 
 ```bash
 docker run -d \
@@ -113,7 +120,7 @@ ClickHouse configuration is represented with a file "config.xml" ([documentation
 docker run -d --name some-clickhouse-server --ulimit nofile=262144:262144 -v /path/to/your/config.xml:/etc/clickhouse-server/config.xml clickhouse/clickhouse-server
 ```
 
-### Start server as a custom user
+### Start server as custom user
 
 ```bash
 # $(pwd)/data/clickhouse should exist and be owned by current user
@@ -122,7 +129,7 @@ docker run --rm --user ${UID}:${GID} --name some-clickhouse-server --ulimit nofi
 
 When you use the image with local directories mounted, you probably want to specify the user to maintain the proper file ownership. Use the `--user` argument and mount `/var/lib/clickhouse` and `/var/log/clickhouse-server` inside the container. Otherwise, the image will complain and not start.
 
-### Start server from root (useful in case of userns enabled)
+### Start server from root (useful in case of enabled user namespace)
 
 ```bash
 docker run --rm -e CLICKHOUSE_UID=0 -e CLICKHOUSE_GID=0 --name clickhouse-server-userns -v "$(pwd)/logs/clickhouse:/var/log/clickhouse-server" -v "$(pwd)/data/clickhouse:/var/lib/clickhouse" clickhouse/clickhouse-server
@@ -130,7 +137,7 @@ docker run --rm -e CLICKHOUSE_UID=0 -e CLICKHOUSE_GID=0 --name clickhouse-server
 
 ### How to create default database and user on starting
 
-Sometimes you may want to create a user (user named `default` is used by default) and database on image start. You can do it using environment variables `CLICKHOUSE_DB`, `CLICKHOUSE_USER`, `CLICKHOUSE_DEFAULT_ACCESS_MANAGEMENT` and `CLICKHOUSE_PASSWORD`:
+Sometimes you may want to create a user (user named `default` is used by default) and database on a container start. You can do it using environment variables `CLICKHOUSE_DB`, `CLICKHOUSE_USER`, `CLICKHOUSE_DEFAULT_ACCESS_MANAGEMENT` and `CLICKHOUSE_PASSWORD`:
 
 ```bash
 docker run --rm -e CLICKHOUSE_DB=my_database -e CLICKHOUSE_USER=username -e CLICKHOUSE_DEFAULT_ACCESS_MANAGEMENT=1 -e CLICKHOUSE_PASSWORD=password -p 9000:9000/tcp clickhouse/clickhouse-server
@@ -156,4 +163,3 @@ EOSQL
 ## License
 
 View [license information](https://github.com/ClickHouse/ClickHouse/blob/master/LICENSE) for the software contained in this image.
-