socfortress / CoPilot

SOCFortress CoPilot
https://www.socfortress.co
GNU Affero General Public License v3.0
210 stars 40 forks source link

Latest image of CoPilot backend doesn't start up, goes into restart loop #302

Closed dLoProdz closed 1 month ago

dLoProdz commented 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:

  1. docker compose pull to get the latest images
  2. docker compose up -d to start the CoPilot project
  3. See error

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
dLoProdz commented 1 month ago

Sorry, didn't see the video beforehand, was missing the minio config, closing this out.