Closed dLoProdz closed 1 month ago
Describe the bug After pulling the latest images and starting CoPilot the backend container goes into a restart loop, exiting with code 3
To Reproduce Steps to reproduce the behavior:
Expected behavior CoPilot should start normally
**Container Logs
copilot-backend | 2024-09-23 12:01:09.281 | INFO | __main__:init_db:166 - Initializing database copilot-backend | 2024-09-23 12:01:09.288 | INFO | app.db.db_setup:create_database_if_not_exists:50 - Database '[db-name]' already exists. copilot-backend | 2024-09-23 12:01:09.294 | INFO | app.db.db_setup:create_copilot_user_if_not_exists:81 - User '[db-user]' already exists. copilot-backend | 2024-09-23 12:01:09.294 | INFO | app.db.db_setup:apply_migrations:90 - Applying migrations copilot-backend | 2024-09-23 12:01:09.294 | INFO | app.db.db_setup:apply_migrations:96 - base_dir: /opt/copilot/backend copilot-backend | 2024-09-23 12:01:09.294 | INFO | app.db.db_setup:apply_migrations:97 - Alembic directory: /opt/copilot/backend/alembic copilot-backend | INFO [alembic.runtime.migration] Context impl MySQLImpl. copilot-backend | INFO [alembic.runtime.migration] Will assume non-transactional DDL. copilot-backend exited with code 3
Sorry, didn't see the video beforehand, was missing the minio config, closing this out.
Describe the bug After pulling the latest images and starting CoPilot the backend container goes into a restart loop, exiting with code 3
To Reproduce Steps to reproduce the behavior:
Expected behavior CoPilot should start normally
**Container Logs