Error at startup

[credo99]

Hi, these are the following errors that I encountered when running the docker-compose om Docker Desktop on win10":

1. Changed the cpus: XXX to cpus: 'XXX" syntax to prevent the lastest Docker engine datatype error
2. Some of the trino-hive-superset nodes are not starting

postgres_1           | The files belonging to this database system will be owned by user "postgres".
postgres_1           | This user must also own the server process.
postgres_1           | 
postgres_1           | The database cluster will be initialized with locale "en_US.utf8".
postgres_1           | The default database encoding has accordingly been set to "UTF8".
postgres_1           | The default text search configuration will be set to "english".
postgres_1           | 
postgres_1           | Data page checksums are disabled.
postgres_1           | 
postgres_1           | fixing permissions on existing directory /var/lib/postgresql/data ... ok
postgres_1           | creating subdirectories ... ok
postgres_1           | selecting dynamic shared memory implementation ... posix
postgres_1           | selecting default max_connections ... 100
postgres_1           | selecting default shared_buffers ... 128MB
postgres_1           | selecting default time zone ... Etc/UTC
postgres_1           | creating configuration files ... ok
postgres_1           | running bootstrap script ... ok
postgres_1           | performing post-bootstrap initialization ... ok
postgres_1           | initdb: warning: enabling "trust" authentication for local connections
postgres_1           | You can change this by editing pg_hba.conf or using the option -A, or
postgres_1           | --auth-local and --auth-host, the next time you run initdb.
postgres_1           | syncing data to disk ... ok
postgres_1           | 
postgres_1           | 
postgres_1           | Success. You can now start the database server using:
postgres_1           | 
postgres_1           |     pg_ctl -D /var/lib/postgresql/data -l logfile start
postgres_1           | 
postgres_1           | waiting for server to start....2022-05-23 14:03:22.027 UTC [49] LOG:  starting PostgreSQL 14.3 (Debian 14.3-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
postgres_1           | 2022-05-23 14:03:22.041 UTC [49] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1           | 2022-05-23 14:03:22.051 UTC [50] LOG:  database system was shut down at 2022-05-23 14:03:21 UTC
postgres_1           | 2022-05-23 14:03:22.060 UTC [49] LOG:  database system is ready to accept connections
postgres_1           |  done
postgres_1           | server started
postgres_1           | CREATE DATABASE
postgres_1           | 
postgres_1           | 
postgres_1           | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
postgres_1           | 
postgres_1           | 2022-05-23 14:03:22.456 UTC [49] LOG:  received fast shutdown request
postgres_1           | waiting for server to shut down....2022-05-23 14:03:22.459 UTC [49] LOG:  aborting any active transactions
postgres_1           | 2022-05-23 14:03:22.461 UTC [49] LOG:  background worker "logical replication launcher" (PID 56) exited with exit code 1
postgres_1           | 2022-05-23 14:03:22.462 UTC [51] LOG:  shutting down
postgres_1           | 2022-05-23 14:03:22.518 UTC [49] LOG:  database system is shut down
postgres_1           |  done
postgres_1           | server stopped
postgres_1           | 
postgres_1           | PostgreSQL init process complete; ready for start up.
postgres_1           | 
postgres_1           | 2022-05-23 14:03:22.644 UTC [1] LOG:  starting PostgreSQL 14.3 (Debian 14.3-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
postgres_1           | 2022-05-23 14:03:22.644 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
postgres_1           | 2022-05-23 14:03:22.644 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres_1           | 2022-05-23 14:03:22.654 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1           | 2022-05-23 14:03:22.662 UTC [63] LOG:  database system was shut down at 2022-05-23 14:03:22 UTC
postgres_1           | 2022-05-23 14:03:22.671 UTC [1] LOG:  database system is ready to accept connections
trino-coordinator_1  | + set +e
trino-coordinator_1  | + grep -s -q node.id /etc/trino/node.properties
trino-coordinator_1  | + NODE_ID_EXISTS=0
trino-coordinator_1  | + set -e
trino-coordinator_1  | + NODE_ID=
trino-coordinator_1  | + [[ 0 != 0 ]]
trino-coordinator_1  | + exec /usr/lib/trino/bin/launcher run --etc-dir /etc/trino
trino-coordinator_1  | May 23, 2022 2:03:28 PM io.airlift.log.Logger info
trino-coordinator_1  | INFO: Java version: 11.0.15
trino-coordinator_1  | 2022-05-23T14:03:28.719Z INFO main io.airlift.log.Logging Logging to stderr
trino-coordinator_1  | 2022-05-23T14:03:28.721Z INFO main Bootstrap Loading configuration
trino-coordinator_1  | 2022-05-23T14:03:29.276Z INFO main Bootstrap Initializing logging
trino-coordinator_1  | 2022-05-23T14:03:30.720Z ERROR main io.trino.server.Server Configuration is invalid
trino-coordinator_1  | ==========
trino-coordinator_1  | 
trino-coordinator_1  | Errors:
trino-coordinator_1  | 
trino-coordinator_1  | 1) Defunct property 'query.max-total-memory-per-node' (class [class io.trino.memory.NodeMemoryConfig]) cannot be configured.
trino-coordinator_1  | 2) Configuration property 'query.max-total-memory-per-node' was not used
trino-coordinator_1  | 
trino-coordinator_1  | ==========
trino-worker_2       | + set +e
trino-worker_2       | + grep -s -q node.id /etc/trino/node.properties
trino-worker_2       | + NODE_ID_EXISTS=1
trino-worker_2       | + set -e
trino-worker_2       | + NODE_ID=
trino-worker_2       | + [[ 1 != 0 ]]
trino-worker_2       | + NODE_ID=-Dnode.id=f2d6d7fdf5f3
trino-worker_2       | + exec /usr/lib/trino/bin/launcher run --etc-dir /etc/trino -Dnode.id=f2d6d7fdf5f3
trino-worker_2       | May 23, 2022 2:03:26 PM io.airlift.log.Logger info
trino-worker_2       | INFO: Java version: 11.0.15
trino-worker_2       | 2022-05-23T14:03:26.918Z INFO main io.airlift.log.Logging Logging to stderr
trino-worker_2       | 2022-05-23T14:03:26.920Z INFO main Bootstrap Loading configuration
trino-worker_2       | 2022-05-23T14:03:27.300Z INFO main Bootstrap Initializing logging
trino-worker_2       | 2022-05-23T14:03:29.151Z ERROR main io.trino.server.Server Configuration is invalid
trino-worker_2       | ==========
trino-worker_2       | 
trino-worker_2       | Errors:
trino-worker_2       | 
trino-worker_2       | 1) Defunct property 'query.max-total-memory-per-node' (class [class io.trino.memory.NodeMemoryConfig]) cannot be configured.
trino-worker_2       | 2) Configuration property 'query.max-total-memory-per-node' was not used
trino-worker_2       | 
trino-worker_2       | ==========
superset_1           | [2022-05-23 14:03:21 +0000] [9] [INFO] Starting gunicorn 20.1.0
superset_1           | [2022-05-23 14:03:21 +0000] [9] [INFO] Listening at: http://0.0.0.0:8088 (9)
superset_1           | [2022-05-23 14:03:21 +0000] [9] [INFO] Using worker: gthread
superset_1           | [2022-05-23 14:03:21 +0000] [11] [INFO] Booting worker with pid: 11
superset_1           | --------------------------------------------------------------------------------
superset_1           |                                     WARNING
superset_1           | --------------------------------------------------------------------------------
superset_1           | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_1           | Use a strong complex alphanumeric string and use a tool to help you generate 
superset_1           | a sufficiently random sequence, ex: openssl rand -base64 42
superset_1           | --------------------------------------------------------------------------------
superset_1           | --------------------------------------------------------------------------------
superset_1           | logging was configured successfully
superset_1           | 2022-05-23 14:03:23,229:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_1           | 2022-05-23 14:03:23,244:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_1           | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: FILTER_STATE_CACHE_CONFIG. It is recommended to use RedisCache, MemcachedCache or another dedicated caching backend for production deployments
superset_1           | 2022-05-23 14:03:23,250:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: FILTER_STATE_CACHE_CONFIG. It is recommended to use RedisCache, MemcachedCache or another dedicated caching backend for production deployments
superset_1           | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: EXPLORE_FORM_DATA_CACHE_CONFIG. It is recommended to use RedisCache, MemcachedCache or another dedicated caching backend for production deployments
superset_1           | 2022-05-23 14:03:23,258:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: EXPLORE_FORM_DATA_CACHE_CONFIG. It is recommended to use RedisCache, MemcachedCache or another dedicated caching backend for production deployments
superset_1           | 127.0.0.1 - - [23/May/2022:14:03:51 +0000] "GET /health HTTP/1.1" 200 2 "-" "curl/7.74.0"
superset_1           | 127.0.0.1 - - [23/May/2022:14:04:21 +0000] "GET /health HTTP/1.1" 200 2 "-" "curl/7.74.0"
superset_1           | 127.0.0.1 - - [23/May/2022:14:04:51 +0000] "GET /health HTTP/1.1" 200 2 "-" "curl/7.74.0"
superset_1           | 127.0.0.1 - - [23/May/2022:14:05:21 +0000] "GET /health HTTP/1.1" 200 2 "-" "curl/7.74.0"
superset_1           | 127.0.0.1 - - [23/May/2022:14:05:51 +0000] "GET /health HTTP/1.1" 200 2 "-" "curl/7.74.0"
hive_1               | standard_init_linux.go:228: exec user process caused: no such file or directory
minio_1              | WARNING: MINIO_ACCESS_KEY and MINIO_SECRET_KEY are deprecated.
minio_1              |          Please use MINIO_ROOT_USER and MINIO_ROOT_PASSWORD
minio_1              | API: http://172.19.0.4:9000  http://127.0.0.1:9000 
minio_1              | Finished loading IAM sub-system (took 0.0s of 0.0s to load data).
minio_1              | 
minio_1              | Console: http://172.19.0.4:9001 http://127.0.0.1:9001 
minio_1              | 
minio_1              | Documentation: https://docs.min.io
trino-worker_1       | + set +e
trino-worker_1       | + grep -s -q node.id /etc/trino/node.properties
trino-worker_1       | + NODE_ID_EXISTS=1
trino-worker_1       | + set -e
trino-worker_1       | + NODE_ID=
trino-worker_1       | + [[ 1 != 0 ]]
trino-worker_1       | + NODE_ID=-Dnode.id=1ba249e07af7
trino-worker_1       | + exec /usr/lib/trino/bin/launcher run --etc-dir /etc/trino -Dnode.id=1ba249e07af7
trino-worker_1       | May 23, 2022 2:03:26 PM io.airlift.log.Logger info
trino-worker_1       | INFO: Java version: 11.0.15
trino-worker_1       | 2022-05-23T14:03:26.928Z INFO main io.airlift.log.Logging Logging to stderr
trino-worker_1       | 2022-05-23T14:03:26.930Z INFO main Bootstrap Loading configuration
trino-worker_1       | 2022-05-23T14:03:27.299Z INFO main Bootstrap Initializing logging
trino-worker_1       | 2022-05-23T14:03:29.259Z ERROR main io.trino.server.Server Configuration is invalid
trino-worker_1       | ==========
trino-worker_1       | 
trino-worker_1       | Errors:
trino-worker_1       | 
trino-worker_1       | 1) Defunct property 'query.max-total-memory-per-node' (class [class io.trino.memory.NodeMemoryConfig]) cannot be configured.
trino-worker_1       | 2) Configuration property 'query.max-total-memory-per-node' was not used
trino-worker_1       | 
trino-worker_1       | ==========

Thanks