After an upgrade from taiga 5 to taiga 6 following guidelines documented here, the taiga-back and taiga-async does not start with following logs:
For taiga-async:
Give permission to taiga:taiga,
Starting Celery...,
error: failed switching to "taiga": operation not permitted,
For taiga-back:
Executing pending migrations,
Operations to perform:,
Apply all migrations: admin, attachments, auth, bitbucket, contact, contenttypes, custom_attributes, djmail, easy_thumbnails, epics, external_apps, feedback, github, gitlab, gogs, history, issues, likes, milestones, notifications, projects, references, sessions, settings, tasks, telemetry, timeline, users, userstorage, userstories, votes, webhooks, wiki,
Running migrations:,
No migrations to apply.,
Load default templates,
Installed 2 object(s) from 1 fixture(s),
Give permission to taiga:taiga,
Starting Taiga API...,
error: failed switching to "taiga": operation not permitted,
How can we reproduce the behavior
I use bind mounts for media, static and settings folders (attaching the modified docker-compose) and external postgres db, by simply issuing docker-compose up, brings the errors.
This is a strange behavior. Why do you have the database service commented? What docker images are you using, (oficial, custom...)?? It seems a permissions errors.
Describe the bug
After an upgrade from taiga 5 to taiga 6 following guidelines documented here, the taiga-back and taiga-async does not start with following logs:
For taiga-async:
For taiga-back:
How can we reproduce the behavior
I use bind mounts for media, static and settings folders (attaching the modified docker-compose) and external postgres db, by simply issuing
docker-compose up
, brings the errors.Workarounds
No workarounds found: cannot use Taiga.
Taiga environment
Self hosted taiga with docker.