You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
misp_db exited with code 1
misp_db | [Entrypoint] Initializing database
misp_db | 2023-08-02T12:56:10.518956Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
misp_db | 2023-08-02T12:56:10.523378Z 0 [ERROR] --initialize specified but the data directory has files in it. Aborting.
misp_db | 2023-08-02T12:56:10.523444Z 0 [ERROR] Aborting
misp_db |
this can be solved if you change docker-compose.yml
volumes:
- ${DATA_DIR:-./data}/db:/var/lib/mysql
to something like
${DATA_DIR:-./data}/db:/var/lib/minesql
then it starts correctly
The text was updated successfully, but these errors were encountered:
misp_db exited with code 1
misp_db | [Entrypoint] Initializing database
misp_db | 2023-08-02T12:56:10.518956Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
misp_db | 2023-08-02T12:56:10.523378Z 0 [ERROR] --initialize specified but the data directory has files in it. Aborting.
misp_db | 2023-08-02T12:56:10.523444Z 0 [ERROR] Aborting
misp_db |
this can be solved if you change docker-compose.yml
volumes:
- ${DATA_DIR:-./data}/db:/var/lib/mysql
to something like
then it starts correctly
The text was updated successfully, but these errors were encountered: