@@ -72,7 +72,7 @@ $ docker-compose --profile all up -d
...
@@ -72,7 +72,7 @@ $ docker-compose --profile all up -d
container when it up. You could start DolphinScheduler server separately if you want to reuse your exists services.
container when it up. You could start DolphinScheduler server separately if you want to reuse your exists services.
```shell
```shell
$ DOLPHINSCHEDULER_VERSION=3.1.0
$ DOLPHINSCHEDULER_VERSION=3.1.1
# Initialize the database, make sure database <DATABASE> already exists
# Initialize the database, make sure database <DATABASE> already exists
$ docker run -d--name dolphinscheduler-tools \
$ docker run -d--name dolphinscheduler-tools \
-eDATABASE="postgresql"\
-eDATABASE="postgresql"\
...
@@ -133,5 +133,5 @@ and use `admin` and `dolphinscheduler123` as default username and password in th
...
@@ -133,5 +133,5 @@ and use `admin` and `dolphinscheduler123` as default username and password in th
You can modify some environment variables to change configurations when you are starting servers through Docker. We have
You can modify some environment variables to change configurations when you are starting servers through Docker. We have
an example in [using exists PostgreSQL ZooKeeper](#using-exists-postgresql-zookeeper) to change database and ZooKeeper configurations,
an example in [using exists PostgreSQL ZooKeeper](#using-exists-postgresql-zookeeper) to change database and ZooKeeper configurations,
and you could find all environment variables in [all environment variables](https://github.com/apache/dolphinscheduler/blob/3.1.0/script/env/dolphinscheduler_env.sh)<!-- markdown-link-check-disable-line -->
and you could find all environment variables in [all environment variables](https://github.com/apache/dolphinscheduler/blob/3.1.1/script/env/dolphinscheduler_env.sh)<!-- markdown-link-check-disable-line -->