MySQL error during /home/user_api/.local/bin/flask initdb

[cptfixit]

When starting up the SKF stack with docker-compose I noticed the following logging:

skf-api_container | + /home/user_api/.local/bin/flask initdb
skf-api_container | 2023-07-11 06:45:47,750 - skf.db_tools - INFO - Initializing the database
skf-api_container | 2023-07-11 06:45:48,321 - skf.db_tools - INFO - Initialized the prerequisits.
skf-api_container | 2023-07-11 06:45:49,564 - skf.db_tools - INFO - Initialized the markdown code-examples.
skf-api_container | 2023-07-11 06:45:49,600 - skf.db_tools - INFO - Initialized the markdown testing-examples.
skf-api_container | 2023-07-11 06:45:54,092 - skf.db_tools - INFO - Initialized the markdown knowledge-base.
skf-api_container | Initialized the initial data.
skf-api_container | 2023-07-11 06:46:00,382 - user_api.skf.app - INFO - Created the database.

skf-mysql_container | 2023-07-11  6:46:00 8 [Warning] Aborted connection 8 to db: 'skf' user: 'root' host: '172.27.4.6' (Got an error reading communication packets)

skf-api_container | + /home/user_api/.local/bin/gunicorn --bind 0.0.0.0:8888 --workers=6 --threads=3 wsgi:app
skf-api_container | [2023-07-11 06:46:00 +0000] [38] [INFO] Starting gunicorn 20.0.4
skf-api_container | [2023-07-11 06:46:00 +0000] [38] [INFO] Listening at: http://0.0.0.0:8888 (38)
skf-api_container | [2023-07-11 06:46:00 +0000] [38] [INFO] Using worker: threads
skf-api_container | [2023-07-11 06:46:00 +0000] [41] [INFO] Booting worker with pid: 41
skf-api_container | [2023-07-11 06:46:01 +0000] [42] [INFO] Booting worker with pid: 42
skf-api_container | [2023-07-11 06:46:01 +0000] [43] [INFO] Booting worker with pid: 43
skf-api_container | [2023-07-11 06:46:01 +0000] [44] [INFO] Booting worker with pid: 44
skf-api_container | [2023-07-11 06:46:01 +0000] [45] [INFO] Booting worker with pid: 45
skf-api_container | [2023-07-11 06:46:01 +0000] [46] [INFO] Booting worker with pid: 46

During the run of /home/user_api/.local/bin/flask initdb, something happens which causes the MySQL connection to die.

I cannot be sure if this is undesired behavior or not.

[cptfixit]

This issue persists in version 4.1.0 of the API container.