TheBlackBurrito

I've run into an issue where Docker Compose is working from Command Line for a specific service but won't launch correctly through the GUI. I’m setting up Taiga on my server, it needs multiple containers to run so I’m using Docker Compose. If I run Docker Compose from the Command line, (literally just docker compose up -d) it works fine, but if I run it from the Docker Compose GUI Plugin I get some errors. The 'compose.yml' & '.env' file are pointing to correct location in the GUI so I’m wondering what other differences there are that I might be missing. All the container spin up from the GUI then the back-end crashes with this error: (the error isn't relevant to docker compose, but I'll post it just in case) File "/opt/venv/lib/python3.11/site-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ psycopg2.errors.DuplicateColumn: column "issues_csv_uuid" of relation "projects_project" already existsOnce again this only happens when I launch it from the GUI not if I launch it via command line, so I don't think it's an issue with the project. Just that I'm missing some difference between how the plugin runs Docker-Compose. I initially thought it might be some relative path issue, and that the command-line works since I'm running from the folder that has the config.yml in, but if I run docker compose in CL from the root directory and pass in the path of the compose file it also works fine. I've attached the docker compose file in case that helps docker-compose.yml Any help would be appreciated, I've stuck on this problem for a while now