Covering all things Far Cry. Discuss the Far Cry series, share your custom maps, or party up with other players!
A community for fans of the Capcom series, Resident Evil, (aka Biohazard in Japan).
A community for discussing the Hinge dating app. Request a profile review, ask for advice, get help, or share your experiences with Hinge. This subreddit is unofficial and we are not affiliated with or represent Hinge in any official capacity.
God is silent when He's not spoken. For example, in Hebrews 7:14, Paul shows that Jesus was not authorized to be a priest under the Mosaic Law because Moses had "spoke nothing" concerning priests from Judah.
God's Silence is not Permissive.Paul uses the fact that God's silence is not authoritative to show that the law had to be changed before Jesus could serve as our high priest (Heb. 7:12-14). This shows we're only permitted to do the things God has authorized -- nothing else. God's commands teach us to respect His silence, and only do the things He's authorized.
1 Pet. 4:11 We must speak, and therefore do, what God instructs in His word.
Col. 3:17 Our words and actions must be authorized.
1 Cor. 4:6 We cannot think beyond what is written. We cannot do anything that has not been authorized in God's word (cf. 2 Tim. 3:16-17; 2 Pet. 1:3; 2 Jn. 1:9).
2 Jn. 1:9 If we do not abide in the teaching of Christ, we do not have God -- we've gone "too far" (NASB).
Rev. 22:18-19 We cannot add to or take from God's word. We cannot do anything that has not been authorized in God's word (cf. Deut. 4:1-2)
It's also interesting to note that men communicate in the same way -- silence is not permissive.
Acts 15:24 The apostles and elders wrote a letter to the Gentiles, stating that false teaching regarding Christians keeping the Mosaic Law hadn't come from them. This was evidenced by the fact that they had given "no such commandment" (NKJV). They had been silent; therefore, they hadn't authorized the teaching.
For example, an employer tells his employees what to do, without listing the millions of do-nots. We understand as employees that we can only do those things authorized, and that we'll be punished for doing other things. If our employer tells us to work one place and we go home for the day, we know we'll be punished and probably fired.
Just as employees know their employer's silence is not permissive, we know God's silence is not authoritative. When God tells us to do one thing, and we do something else, we know we'll be punished for our disobedience.
In Jeremiah 7:22-31; 32:35, God condemned Israel's sacrifice of their children to Molech. This abomination hadn't been commanded by God, nor even entered His mind. Because of their sin, God brought the Babylonians upon them to destroy their cities and take them into captivity. From this event, we learn that disrespecting God's silence results in abominable sin for which we are punished.
From the Old and New Testaments, we learn God's silence is not authoritative. We are only permitted to do the things God has authorized, and nothing else.
Let’s respect the silence of God as much as we respect His Voice.
I lost my 15 year old son, and I'm personally mad as Hell as to what is expected of me in the months to come. He died on 12/15/22. I'm nearing the end of my allotted leave. And will be quitting my job when that deadline approaches. Not everyone has the luxury I do, financially after I leave my employer. I worry emotionally about those that don't have that luxury. In an era of a pandemic, fmla has not held up the status quo to death and the need for adequate leave for immediate family members. FMLA has not provided adequate protection. It's callous and inhumane, in my own experience.
Grief should be HEARD long and far. It should not be SILENCED by ignorance or LAWS. By FEAR or governing laws.
We deserve more...
Thank you everyone who helped me plan my trip from Salt Lake City to Denver. Now I need to plan my next and final leg to Dallas.
I need your suggestions on the best route from Denver to Dallas now. I have never driven in that part of US so looking for safest way. We can do it in a single day but are ok to do overnight (if overnight then a bigger city would be our preference in between)
I am inclined for route 3 so that I pass Colorado Springs but it’s not a must.
Thank you as always.
I am running the following docker compose but I am getting issues with the setup where it throws up errors.
Error: Version: '10.6.13-MariaDB-1:10.6.13+maria~ubu2004' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution 2-db-1 2023-05-28 22:00:54 4 [Warning] Aborted connection 4 to db: 'unconnected' user: 'unauthenticated' host: '172.18.0.6' (This connection closed normally without authentication)
Docker Compose: version: "3"
services:
backend:
image: frappe/erpnext:v14
deploy:
restart_policy:
condition: on-failure
volumes:
- sites:/home/frappe/frappe-bench/sites
- logs:/home/frappe/frappe-bench/logs
networks:
- erpnext
configurator:
image: frappe/erpnext:v14
deploy:
restart_policy:
condition: none
entrypoint:
- bash
- -c
command:
- >
ls -1 apps > sites/apps.txt;
bench set-config -g db_host $$DB_HOST;
bench set-config -gp db_port $$DB_PORT;
bench set-config -g redis_cache "redis://$$REDIS_CACHE";
bench set-config -g redis_queue "redis://$$REDIS_QUEUE";
bench set-config -g redis_socketio "redis://$$REDIS_SOCKETIO";
bench set-config -gp socketio_port $$SOCKETIO_PORT;
environment:
DB_HOST: db
DB_PORT: "3306"
REDIS_CACHE: redis-cache:6379
REDIS_QUEUE: redis-queue:6379
REDIS_SOCKETIO: redis-socketio:6379
SOCKETIO_PORT: "9000"
volumes:
- sites:/home/frappe/frappe-bench/sites
- logs:/home/frappe/frappe-bench/logs
networks:
- erpnext
create-site:
image: frappe/erpnext:v14
deploy:
restart_policy:
condition: none
volumes:
- sites:/home/frappe/frappe-bench/sites
- logs:/home/frappe/frappe-bench/logs
entrypoint:
- bash
- -c
command:
- >
wait-for-it -t 120 db:3306;
wait-for-it -t 120 redis-cache:6379;
wait-for-it -t 120 redis-queue:6379;
wait-for-it -t 120 redis-socketio:6379;
export start=`date +%s`;
until [[ -n `grep -hs ^ sites/common_site_config.json jq -r ".db_host // empty"` ]] && \
[[ -n `grep -hs ^ sites/common_site_config.json jq -r ".redis_cache // empty"` ]] && \
[[ -n `grep -hs ^ sites/common_site_config.json jq -r ".redis_queue // empty"` ]];
do
echo "Waiting for sites/common_site_config.json to be created";
sleep 5;
if (( `date +%s`-start > 120 )); then
echo "could not find sites/common_site_config.json with required keys";
exit 1
fi
done;
echo "sites/common_site_config.json found";
bench new-site frontend --no-mariadb-socket --admin-password=admin --db-root-password=admin --install-app erpnext --set-default;
networks:
- erpnext
db:
image: mariadb:latest
healthcheck:
test: mysqladmin ping -h localhost --password=admin
interval: 1s
retries: 15
deploy:
restart_policy:
condition: on-failure
command:
- --character-set-server=utf8mb4
- --collation-server=utf8mb4_unicode_ci
- --skip-character-set-client-handshake
- --skip-innodb-read-only-compressed # Temporary fix for MariaDB 10.6
environment:
MYSQL_ROOT_PASSWORD: admin
volumes:
- db-data:/valib/mysql
networks:
- erpnext
frontend:
image: frappe/erpnext:v14
deploy:
restart_policy:
condition: on-failure
command:
- nginx-entrypoint.sh
environment:
BACKEND: backend:8000
FRAPPE_SITE_NAME_HEADER: frontend
SOCKETIO: websocket:9000
UPSTREAM_REAL_IP_ADDRESS: 127.0.0.1
UPSTREAM_REAL_IP_HEADER: X-Forwarded-For
UPSTREAM_REAL_IP_RECURSIVE: "off"
PROXY_READ_TIMOUT: 120
CLIENT_MAX_BODY_SIZE: 50m
volumes:
- sites:/home/frappe/frappe-bench/sites
- logs:/home/frappe/frappe-bench/logs
networks:
- erpnext
- nginx
queue-default:
image: frappe/erpnext:v14
deploy:
restart_policy:
condition: on-failure
command:
- bench
- worker
- --queue
- default
volumes:
- sites:/home/frappe/frappe-bench/sites
- logs:/home/frappe/frappe-bench/logs
networks:
- erpnext
queue-long:
image: frappe/erpnext:v14
deploy:
restart_policy:
condition: on-failure
command:
- bench
- worker
- --queue
- long
volumes:
- sites:/home/frappe/frappe-bench/sites
- logs:/home/frappe/frappe-bench/logs
networks:
- erpnext
queue-short:
image: frappe/erpnext:v14
deploy:
restart_policy:
condition: on-failure
command:
- bench
- worker
- --queue
- short
volumes:
- sites:/home/frappe/frappe-bench/sites
- logs:/home/frappe/frappe-bench/logs
networks:
- erpnext
redis-queue:
image: redis:6.2-alpine
deploy:
restart_policy:
condition: on-failure
volumes:
- redis-queue-data:/data
networks:
- erpnext
redis-cache:
image: redis:6.2-alpine
deploy:
restart_policy:
condition: on-failure
volumes:
- redis-cache-data:/data
networks:
- erpnext
redis-socketio:
image: redis:6.2-alpine
deploy:
restart_policy:
condition: on-failure
volumes:
- redis-socketio-data:/data
networks:
- erpnext
scheduler:
image: frappe/erpnext:v14
deploy:
restart_policy:
condition: on-failure
command:
- bench
- schedule
volumes:
- sites:/home/frappe/frappe-bench/sites
- logs:/home/frappe/frappe-bench/logs
networks:
- erpnext
websocket:
image: frappe/erpnext:v14
deploy:
restart_policy:
condition: on-failure
command:
- node
- /home/frappe/frappe-bench/apps/frappe/socketio.js
volumes:
- sites:/home/frappe/frappe-bench/sites
- logs:/home/frappe/frappe-bench/logs
networks:
- erpnext
volumes:
db-data:
redis-queue-data:
redis-cache-data:
redis-socketio-data:
sites:
driver: local
driver_opts:
type: none
o: bind
device: /vacontainesites
logs:
driver: local
driver_opts:
type: none
o: bind
device: /vacontainelogs
networks:
nginx:
external: true
erpnext:
external: true
Log: 1-redis-queue-1 1:C 28 May 2023 23:22:20.244 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1-redis-queue-1 1:C 28 May 2023 23:22:20.244 # Redis version=6.2.12, bits=64, commit=00000000, modified=0, pid=1, just started
1-redis-queue-1 1:C 28 May 2023 23:22:20.244 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1-redis-queue-1 1:M 28 May 2023 23:22:20.244 * monotonic clock: POSIX clock_gettime
1-redis-queue-1 1:M 28 May 2023 23:22:20.245 * Running mode=standalone, port=6379.
1-redis-queue-1 1:M 28 May 2023 23:22:20.245 # Server initialized
1-redis-queue-1 1:M 28 May 2023 23:22:20.245 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see
https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1-redis-queue-1 1:M 28 May 2023 23:22:20.245 * Ready to accept connections
1-redis-cache-1 1:C 28 May 2023 23:22:20.347 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1-redis-cache-1 1:C 28 May 2023 23:22:20.348 # Redis version=6.2.12, bits=64, commit=00000000, modified=0, pid=1, just started
1-redis-cache-1 1:C 28 May 2023 23:22:20.348 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1-redis-cache-1 1:M 28 May 2023 23:22:20.348 * monotonic clock: POSIX clock_gettime
1-redis-cache-1 1:M 28 May 2023 23:22:20.348 * Running mode=standalone, port=6379.
1-redis-cache-1 1:M 28 May 2023 23:22:20.348 # Server initialized
1-redis-cache-1 1:M 28 May 2023 23:22:20.348 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see
https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1-redis-cache-1 1:M 28 May 2023 23:22:20.349 * Ready to accept connections
1-db-1 2023-05-28 23:22:20+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.11.3+maria~ubu2204 started.
1-db-1 2023-05-28 23:22:20+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
1-db-1 2023-05-28 23:22:20+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.11.3+maria~ubu2204 started.
1-db-1 2023-05-28 23:22:20+00:00 [Note] [Entrypoint]: Initializing database files
1-redis-socketio-1 1:C 28 May 2023 23:22:21.079 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1-redis-socketio-1 1:C 28 May 2023 23:22:21.079 # Redis version=6.2.12, bits=64, commit=00000000, modified=0, pid=1, just started
1-redis-socketio-1 1:C 28 May 2023 23:22:21.079 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1-redis-socketio-1 1:M 28 May 2023 23:22:21.080 * monotonic clock: POSIX clock_gettime
1-redis-socketio-1 1:M 28 May 2023 23:22:21.080 * Running mode=standalone, port=6379.
1-redis-socketio-1 1:M 28 May 2023 23:22:21.080 # Server initialized
1-redis-socketio-1 1:M 28 May 2023 23:22:21.080 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see
https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1-redis-socketio-1 1:M 28 May 2023 23:22:21.081 * Ready to accept connections
1-create-site-1 wait-for-it: waiting 120 seconds for db:3306
1-queue-long-1 2023-05-28 23:22:21,460 Worker rq:worker:6fd7cc0da35f4349b30d1e92691f3604.eab2a72870a4.1.home-frappe-frappe-bench:long: started, version 1.11.1
1-queue-long-1 2023-05-28 23:22:21,460 Subscribing to channel rq:pubsub:6fd7cc0da35f4349b30d1e92691f3604.eab2a72870a4.1.home-frappe-frappe-bench:long
1-queue-long-1 2023-05-28 23:22:21,483 *** Listening on home-frappe-frappe-bench:long...
1-queue-long-1 2023-05-28 23:22:21,483 Cleaning registries for queue: home-frappe-frappe-bench:long
1-frontend-1 PROXY_READ_TIMEOUT defaulting to 120
1-backend-1 [2023-05-28 23:22:22 +0000] [1] [INFO] Starting gunicorn 20.1.0
1-backend-1 [2023-05-28 23:22:22 +0000] [1] [INFO] Listening at:
http://0.0.0.0:8000 (1)
1-backend-1 [2023-05-28 23:22:22 +0000] [1] [INFO] Using worker: gthread
1-backend-1 [2023-05-28 23:22:22 +0000] [7] [INFO] Booting worker with pid: 7
1-queue-default-1 2023-05-28 23:22:22,020 Worker rq:worker:3d9c3e4bdabe4eb0b0912d22b2f553eb.71172abda72c.1.home-frappe-frappe-bench:default: started, version 1.11.1
1-queue-default-1 2023-05-28 23:22:22,020 Subscribing to channel rq:pubsub:3d9c3e4bdabe4eb0b0912d22b2f553eb.71172abda72c.1.home-frappe-frappe-bench:default
1-queue-default-1 2023-05-28 23:22:22,023 *** Listening on home-frappe-frappe-bench:default...
1-queue-default-1 2023-05-28 23:22:22,024 Cleaning registries for queue: home-frappe-frappe-bench:default
1-backend-1 [2023-05-28 23:22:22 +0000] [8] [INFO] Booting worker with pid: 8
1-queue-short-1 2023-05-28 23:22:22,475 Worker rq:worker:4fe42c3b1e7a4ae496c4b6d67afc5f74.3bcdcb3afc53.1.home-frappe-frappe-bench:short: started, version 1.11.1
1-queue-short-1 2023-05-28 23:22:22,476 Subscribing to channel rq:pubsub:4fe42c3b1e7a4ae496c4b6d67afc5f74.3bcdcb3afc53.1.home-frappe-frappe-bench:short
1-queue-short-1 2023-05-28 23:22:22,477 *** Listening on home-frappe-frappe-bench:short...
1-queue-short-1 2023-05-28 23:22:22,478 Cleaning registries for queue: home-frappe-frappe-bench:short
1-db-1
1-db-1
1-db-1 PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
1-db-1 To do so, start the server, then issue the following command:
1-db-1
1-db-1 '/usbin/mariadb-secure-installation'
1-db-1
1-db-1 which will also give you the option of removing the test
1-db-1 databases and anonymous user created by default. This is
1-db-1 strongly recommended for production servers.
1-db-1
1-db-1 See the MariaDB Knowledgebase at
https://mariadb.com/kb 1-db-1
1-db-1 Please report any problems at
https://mariadb.org/jira 1-db-1
1-db-1 The latest information about MariaDB is available at
https://mariadb.org/.
1-db-1
1-db-1 Consider joining MariaDB's strong and vibrant community:
1-db-1
https://mariadb.org/get-involved/ 1-db-1
1-db-1 2023-05-28 23:22:23+00:00 [Note] [Entrypoint]: Database files initialized
1-db-1 2023-05-28 23:22:23+00:00 [Note] [Entrypoint]: Starting temporary server
1-db-1 2023-05-28 23:22:23+00:00 [Note] [Entrypoint]: Waiting for server startup
1-db-1 2023-05-28 23:22:23 0 [Note] Starting MariaDB 10.11.3-MariaDB-1:10.11.3+maria~ubu2204 source revision 0bb31039f54bd6a0dc8f0fc7d40e6b58a51998b0 as process 118
1-db-1 2023-05-28 23:22:23 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
1-db-1 2023-05-28 23:22:23 0 [Note] InnoDB: Number of transaction pools: 1
1-db-1 2023-05-28 23:22:23 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
1-db-1 2023-05-28 23:22:23 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
1-db-1 2023-05-28 23:22:23 0 [Note] InnoDB: Using liburing
1-db-1 2023-05-28 23:22:23 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
1-db-1 2023-05-28 23:22:23 0 [Note] InnoDB: Completed initialization of buffer pool
1-db-1 2023-05-28 23:22:23 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
1-db-1 2023-05-28 23:22:23 0 [Note] InnoDB: 128 rollback segments are active.
1-db-1 2023-05-28 23:22:23 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
1-db-1 2023-05-28 23:22:23 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
1-db-1 2023-05-28 23:22:23 0 [Note] InnoDB: log sequence number 46590; transaction id 14
1-db-1 2023-05-28 23:22:23 0 [Note] Plugin 'FEEDBACK' is disabled.
1-db-1 2023-05-28 23:22:23 0 [Warning] 'user' entry '
[email protected]' ignored in --skip-name-resolve mode.
1-db-1 2023-05-28 23:22:23 0 [Warning] 'proxies_priv' entry '@%
[email protected]' ignored in --skip-name-resolve mode.
1-db-1 2023-05-28 23:22:23 0 [Note] mariadbd: ready for connections.
1-db-1 Version: '10.11.3-MariaDB-1:10.11.3+maria~ubu2204' socket: '/run/mysqld/mysqld.sock' port: 0 mariadb.org binary distribution
1-db-1 2023-05-28 23:22:23 3 [Warning] Access denied for user 'root'@'localhost' (using password: YES)
1-db-1 2023-05-28 23:22:24+00:00 [Note] [Entrypoint]: Temporary server started.
1-db-1 2023-05-28 23:22:24 6 [Warning] Access denied for user 'root'@'localhost' (using password: YES)
1-db-1 2023-05-28 23:22:25 7 [Warning] Access denied for user 'root'@'localhost' (using password: YES)
1-db-1 2023-05-28 23:22:26+00:00 [Note] [Entrypoint]: Securing system users (equivalent to running mysql_secure_installation)
1-db-1
1-db-1 2023-05-28 23:22:26+00:00 [Note] [Entrypoint]: Stopping temporary server
1-db-1 2023-05-28 23:22:26 0 [Note] mariadbd (initiated by: unknown): Normal shutdown
1-db-1 2023-05-28 23:22:26 0 [Note] InnoDB: FTS optimize thread exiting.
1-db-1 2023-05-28 23:22:26 0 [Note] InnoDB: Starting shutdown...
1-db-1 2023-05-28 23:22:26 0 [Note] InnoDB: Dumping buffer pool(s) to /valib/mysql/ib_buffer_pool
1-db-1 2023-05-28 23:22:26 0 [Note] InnoDB: Buffer pool(s) dump completed at 230528 23:22:26
1-db-1 2023-05-28 23:22:26 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
1-db-1 2023-05-28 23:22:26 0 [Note] InnoDB: Shutdown completed; log sequence number 46590; transaction id 15
1-db-1 2023-05-28 23:22:26 0 [Note] mariadbd: Shutdown complete
1-db-1
1-db-1 2023-05-28 23:22:26+00:00 [Note] [Entrypoint]: Temporary server stopped
1-db-1
1-db-1 2023-05-28 23:22:26+00:00 [Note] [Entrypoint]: MariaDB init process done. Ready for start up.
1-db-1
1-db-1 2023-05-28 23:22:26 0 [Note] Starting MariaDB 10.11.3-MariaDB-1:10.11.3+maria~ubu2204 source revision 0bb31039f54bd6a0dc8f0fc7d40e6b58a51998b0 as process 11-db-1 2023-05-28 23:22:26 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
1-db-1 2023-05-28 23:22:26 0 [Note] InnoDB: Number of transaction pools: 1
1-db-1 2023-05-28 23:22:26 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
1-db-1 2023-05-28 23:22:26 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
1-db-1 2023-05-28 23:22:26 0 [Note] InnoDB: Using liburing
1-db-1 2023-05-28 23:22:26 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
1-db-1 2023-05-28 23:22:26 0 [Note] InnoDB: Completed initialization of buffer pool
1-db-1 2023-05-28 23:22:26 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
1-db-1 2023-05-28 23:22:26 0 [Note] InnoDB: 128 rollback segments are active.
1-db-1 2023-05-28 23:22:26 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
1-db-1 2023-05-28 23:22:26 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
1-db-1 2023-05-28 23:22:26 0 [Note] InnoDB: log sequence number 46590; transaction id 14
1-db-1 2023-05-28 23:22:26 0 [Note] InnoDB: Loading buffer pool(s) from /valib/mysql/ib_buffer_pool
1-db-1 2023-05-28 23:22:26 0 [Note] Plugin 'FEEDBACK' is disabled.
1-db-1 2023-05-28 23:22:26 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
1-db-1 2023-05-28 23:22:26 0 [Note] Server socket created on IP: '0.0.0.0'.
1-db-1 2023-05-28 23:22:26 0 [Note] Server socket created on IP: '::'.
1-db-1 2023-05-28 23:22:26 0 [Note] InnoDB: Buffer pool(s) load completed at 230528 23:22:26
1-db-1 2023-05-28 23:22:26 0 [Note] mariadbd: ready for connections.
1-db-1 Version: '10.11.3-MariaDB-1:10.11.3+maria~ubu2204' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
1-db-1 2023-05-28 23:22:27 3 [Warning] Aborted connection 3 to db: 'unconnected' user: 'unauthenticated' host: '172.18.0.13' (This connection closed normally without authentication)
1-create-site-1 wait-for-it: db:3306 is available after 6 seconds
1-create-site-1 wait-for-it: waiting 120 seconds for redis-cache:6379
1-create-site-1 wait-for-it: redis-cache:6379 is available after 0 seconds
1-create-site-1 wait-for-it: waiting 120 seconds for redis-queue:6379
1-create-site-1 wait-for-it: redis-queue:6379 is available after 0 seconds
1-create-site-1 wait-for-it: waiting 120 seconds for redis-socketio:6379
1-create-site-1 wait-for-it: redis-socketio:6379 is available after 0 seconds
1-create-site-1 sites/common_site_config.json found
1-configurator-1 exited with code 0
1-create-site-1 Site frontend already exists
1-create-site-1 exited with code 1
1-db-1 2023-05-28 23:23:22 54 [Warning] Access denied for user '_5e5899d8398b5f7b'@'172.18.0.10' (using password: YES)
1-db-1 2023-05-28 23:24:22 108 [Warning] Access denied for user '_5e5899d8398b5f7b'@'172.18.0.10' (using password: YES)
What am I doing wrong?