monogramm / docker-taiga Goto Github PK
View Code? Open in Web Editor NEW:whale: :snake: Docker images for a full Taiga environment with additional plugins.
Home Page: https://taiga.io/
License: GNU Affero General Public License v3.0
docker-taiga's People
Contributors
Stargazers
Watchers
Forkers
springdo babisk suren2306 michidk pulmik cinco felipeolvr nuokh nvtienanh xolyu sleepergithub joel-scholl-amzdocker-taiga's Issues
LDAP Contrib Plugin do not start
Describe the bug
Upgrading from Taiga 5.0 (hub image) to Taiga 6.0 (hub image) fails on LDAP integration. LDAP Plugin do not load. Rolling back to Taiga 5.0 LDAP was working correctly.
To Reproduce
Steps to reproduce the behavior:
- Matching Taiga 5 compose file entries with the new taiga 6 compose and .env file
- docker-compose up
Expected behavior
taiga_back | Taiga contrib LDAP Auth Ext enabled
Screenshots
taiga_back | [2021-11-10T08:27:41] Compiling messages and collecting static
taiga_back | Enabling Taiga emails...
taiga_back | Enabling Taiga SSL...
taiga_back | Taiga statistics enabled
taiga_back | Taiga events enabled
taiga_back | Taiga async mode enabled
taiga_celery | [2021-11-10T08:27:43] Executing command
taiga_celery | Enabling Taiga emails...
taiga_celery | Taiga events enabled
taiga_celery | Taiga async mode enabled
taiga_back | Enabling Taiga emails...
taiga_back | Enabling Taiga SSL...
taiga_back | Taiga statistics enabled
taiga_back | Taiga events enabled
taiga_back | Taiga async mode enabled
taiga_rabbit | 2021-11-10 07:27:47.023835+00:00 [info] <0.596.0> accepting AMQP connection <0.596.0> (192.168.0.1:52294 -> 192.168.0.3:5672)
taiga_rabbit | 2021-11-10 07:27:47.028459+00:00 [info] <0.596.0> connection <0.596.0> (192.168.0.1:52294 -> 192.168.0.3:5672): user 'taiga' authenticated and granted access to vhost 'taiga'
taiga_rabbit | 2021-11-10 07:27:47.041017+00:00 [info] <0.604.0> accepting AMQP connection <0.604.0> (192.168.0.1:52296 -> 192.168.0.3:5672)
taiga_rabbit | 2021-11-10 07:27:47.044040+00:00 [info] <0.604.0> connection <0.604.0> (192.168.0.1:52296 -> 192.168.0.3:5672): user 'taiga' authenticated and granted access to vhost 'taiga'
taiga_rabbit | 2021-11-10 07:27:47.064117+00:00 [info] <0.624.0> accepting AMQP connection <0.624.0> (192.168.0.1:52298 -> 192.168.0.3:5672)
taiga_rabbit | 2021-11-10 07:27:47.068243+00:00 [info] <0.624.0> connection <0.624.0> (192.168.0.1:52298 -> 192.168.0.3:5672): user 'taiga' authenticated and granted access to vhost 'taiga'
taiga_back | [2021-11-10T08:27:47] Start gunicorn server
taiga_back | [2021-11-10 08:27:47 +0100] [1] [INFO] Starting gunicorn 19.9.0
taiga_back | [2021-11-10 08:27:47 +0100] [1] [INFO] Listening at: http://0.0.0.0:8001 (1)
taiga_back | [2021-11-10 08:27:47 +0100] [1] [INFO] Using worker: sync
taiga_back | [2021-11-10 08:27:47 +0100] [87] [INFO] Booting worker with pid: 87
taiga_back | [2021-11-10 08:27:47 +0100] [88] [INFO] Booting worker with pid: 88
taiga_back | [2021-11-10 08:27:47 +0100] [89] [INFO] Booting worker with pid: 89
taiga_back | [2021-11-10 08:27:47 +0100] [90] [INFO] Booting worker with pid: 90
taiga_back | Enabling Taiga emails...
taiga_back | Enabling Taiga SSL...
taiga_back | Taiga statistics enabled
taiga_back | Taiga events enabled
taiga_back | Taiga async mode enabled
taiga_back | Enabling Taiga emails...
taiga_back | Enabling Taiga SSL...
taiga_back | Taiga statistics enabled
taiga_back | Taiga events enabled
taiga_back | Taiga async mode enabled
taiga_back | Enabling Taiga emails...
taiga_back | Enabling Taiga SSL...
taiga_back | Taiga statistics enabled
taiga_back | Taiga events enabled
taiga_back | Taiga async mode enabled
taiga_back | Enabling Taiga emails...
taiga_back | Enabling Taiga SSL...
taiga_back | Taiga statistics enabled
taiga_back | Taiga events enabled
taiga_back | Taiga async mode enabled
Docker (please complete the following information):
Server Version: 19.03.11
docker-compose version 1.26.0, build d4451659
docker-py version: 4.2.1
CPython version: 3.7.7
Error running docker-compose up -d
Getting the following error while running docker-compose up -d for taiga 6.0
WARNING: The DOCKERFILE_PATH variable is not set. Defaulting to a blank string.
WARNING: The IMAGE_NAME variable is not set. Defaulting to a blank string.
Traceback (most recent call last):
File "bin/docker-compose", line 6, in <module>
File "compose/cli/main.py", line 71, in main
File "compose/cli/main.py", line 127, in perform_command
File "compose/cli/main.py", line 1052, in up
File "compose/cli/main.py", line 1048, in up
File "compose/project.py", line 466, in up
File "compose/service.py", line 333, in ensure_image_exists
File "compose/service.py", line 353, in image
File "site-packages/docker/utils/decorators.py", line 17, in wrapped
docker.errors.NullResource: Resource ID was not provided
[25669] Failed to execute script docker-compose
Docker Version
Client: Docker Engine - Community
Version: 19.03.13
API version: 1.40
Go version: go1.13.15
Git commit: 4484c46d9d
Built: Wed Sep 16 17:02:36 2020
OS/Arch: linux/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 19.03.13
API version: 1.40 (minimum version 1.12)
Go version: go1.13.15
Git commit: 4484c46d9d
Built: Wed Sep 16 17:01:06 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.3.7
GitCommit: 8fba4e9a7d01810a393d5d25a3621dc101981175
runc:
Version: 1.0.0-rc10
GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version: 0.18.0
GitCommit: fec3683
Docker-compose Version
docker-compose version 1.21.2, build a133471
docker-py version: 3.3.0
CPython version: 3.6.5
OpenSSL version: OpenSSL 1.0.1t 3 May 2016
taiga_front exited with code 1
Error on startup with untouched compose-file (production setup, sync mode) at taiga_front
taiga_front | 2020/07/14 06:34:58 [emerg] 51#51: host not found in upstream "taiga_events" in /etc/nginx/snippets/events.conf:2 taiga_front | nginx: [emerg] host not found in upstream "taiga_events" in /etc/nginx/snippets/events.conf:2 taiga_front | nginx: configuration file /etc/nginx/nginx.conf test failed taiga_front exited with code 1
Production Images used:
REPOSITORY TAG IMAGE ID CREATED SIZE rabbitmq 3-alpine 7465a4f31266 2 weeks ago 108MB monogramm/docker-taiga-back 5.0-alpine 1d768e3f59dd 5 weeks ago 441MB monogramm/docker-taiga-front 5.0-alpine 6730d02f8e21 6 weeks ago 51.4MB monogramm/docker-taiga-events alpine 7a48883a902c 6 weeks ago 136MB
taiga_front TAIGA_FEEDBACK_ENABLED should true not True
if TAIGA_FEEDBACK_ENABLED=True ,login error
Question: Whats the difference between sync and async mode?
Can you short explain the difference between sync and async mode?
Whats "Best Practice" for production?
Admin login error
I launched taiga using the docker-compose file under images/5.0/alpine. I am unable to login taiga admin console using the password which I provided in the .env file.
The error message found in the browser console is,
_error_message: invalid login type
_error_type: taiga.base.exceptions.BadRequest
My .env file is a follows,
[user@taiga alpine]# cat .env
# Set all your environment variables here
#########################################
## GENERAL
#########################################
HOSTNAME=taiga.test.com
# Adapt to your production domain and use a reverse proxy
#HOSTNAME=taiga.company.com
PORT=80
TAIGA_DB_PWD=password
#########################################
## SECURITY
#########################################
TAIGA_SECRET=MySecretKey
TAIGA_ADMIN_PASSWORD=123123
#########################################
## EMAIL
#########################################
TAIGA_EMAIL_DOMAIN=testdomain.com
TAIGA_SMTP_HOST=XXXXXXXXXXXXXXXXXXXX
TAIGA_SMTP_USER=XXXXXXXXXXXXXXXXXXXX
TAIGA_SMTP_PWD=XXXXXXXXXXXXXXXXXXXXX
#########################################
## GITLAB
#########################################
TAIGA_ENABLE_GITLAB_AUTH=False
#TAIGA_GITLAB_AUTH_URL=https://gitlab.company.com
# Get these from Admin -> Applications
#TAIGA_GITLAB_AUTH_CLIENT_ID=
#TAIGA_GITLAB_AUTH_CLIENT_SECRET=
#########################################
## GITHUB
#########################################
TAIGA_ENABLE_GITHUB_AUTH=False
# Get these from https://github.com/settings/developers
#TAIGA_GITHUB_AUTH_CLIENT_ID=
#TAIGA_GITHUB_AUTH_CLIENT_SECRET=
#########################################
## LDAP
#########################################
TAIGA_ENABLE_LDAP=False
# Adapt to your base domain name
#TAIGA_LDAP_DOMAIN=ldap.company.com
#TAIGA_LDAP_BASE_DN=ou=People,dc=company,dc=com
#TAIGA_LDAP_BIND_DN=
#TAIGA_LDAP_BIND_PASSWORD=
#########################################
## EVENTS
#########################################
TAIGA_RABBIT_USER=taiga
TAIGA_RABBIT_PASSWORD=password
Not able to create User story
We have cloned the code and run the docker-compose up and all containers are running.
While trying to create a User story in the Project it is not getting created. We can see the below logs.
taiga_rabbit | vhost '/' not found
taiga_events | Unhandled rejection Error: Expected ConnectionOpenOk; got
taiga_events | at /usr/src/taiga-events/node_modules/amqplib/lib/connection.js:168:14
taiga_events | at /usr/src/taiga-events/node_modules/amqplib/lib/connection.js:160:12
taiga_events | at Socket.recv (/usr/src/taiga-events/node_modules/amqplib/lib/connection.js:499:12)
taiga_events | at Object.onceWrapper (events.js:421:28)
taiga_events | at Socket.emit (events.js:315:20)
taiga_events | at emitReadable_ (_stream_readable.js:562:12)
taiga_events | at processTicksAndRejections (internal/process/task_queues.js:83:21)
- Docker / Docker-compose Version: docker-compose version 1.21.2, build a133471
- Image docker-taiga-front:5.0-alpine
Desktop (please complete the following information):
- OS: (e.g. iOS) Ubuntu 18.04
- Browser (e.g. chrome, safari) Chrome
- Version (e.g. 22) Version 83
OIDC Keycloak - Blank page unexpected token
Describe the bug
Despite Openid was configured as documentation, openid-auth contrib plugin seems not to be present in tag >= 6.0.10.
To Reproduce
Steps to reproduce the behavior:
- Add OIDC variables to both frontend and backend. (in my case OIDC provider is Keycloak).
- Spin up docker images.
- Enter Taiga
- Blank Page > Inspect Page:
Error loading plugin /plugins/openid-auth/openid-auth.json SyntaxError: Unexpected token < in JSON at position 0 - Within docker front container:
ls /usr/src/taiga-front-dist/dist/plugins/ cookie-warning github-auth gitlab-auth slack
Expected behavior
Expected behaviour would be redirection to OIDC (Keycloak).
Docker (please complete the following information):
- Docker / Docker-compose Version: (e.g. Docker version 20.10.6)
- Image docker-taiga-front:6.0.10-alpine)
Desktop (please complete the following information):
- OS: macOS
- Browser: Chromium
- Version: Version 84.0.4133.0 (Developer Build) (64-bit)
Taiga 6
Any plans to update this to Taiga 6?
400 error when SSL is enabled
After enabling SSL, the site throws 400 error The plain HTTP request was sent to HTTPS port. Tried changing SSL off in the Nginx config but the error persists. Attached the docker-compose file
Taiga_Front Logs
`[2020-12-17T10:55:52] Checking nginx configuration...
2020/12/17 10:55:52 [warn] 52#52: the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /etc/nginx/snippets/ssl.conf:4
nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /etc/nginx/snippets/ssl.conf:4
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
[2020-12-17T10:55:52] Start nginx server...
2020/12/17 10:55:52 [warn] 54#54: the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /etc/nginx/snippets/ssl.conf:4
nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /etc/nginx/snippets/ssl.conf:4
127.0.0.1 - - [17/Dec/2020:10:56:22 +0530] "GET /conf.json HTTP/1.1" 301 169 "-" "curl/7.69.1" "-"
127.0.0.1 - - [17/Dec/2020:10:57:53 +0530] "GET /conf.json HTTP/1.1" 301 169 "-" "curl/7.69.1" "-"
172.21.0.1 - - [17/Dec/2020:10:58:20 +0530] "GET / HTTP/1.1" 400 255 "-" "Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:83.0) Gecko/20100101 Firefox/83.0" "-"
172.21.0.1 - - [17/Dec/2020:10:58:20 +0530] "GET /favicon.ico HTTP/1.1" 400 255 "http://localtaiga.ragecom.com/" "Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:83.0) Gecko/20100101 Firefox/83.0" "-"
127.0.0.1 - - [17/Dec/2020:10:58:23 +0530] "GET /conf.json HTTP/1.1" 301 169 "-" "curl/7.69.1" "-"
127.0.0.1 - - [17/Dec/2020:10:58:53 +0530] "GET /conf.json HTTP/1.1" 301 169 "-" "curl/7.69.1" "-"`
[Question] Why two images?
I'm curious why there was a need for multiple images. Most taiga-docker implementations are single image, with another for the database of course. The frontend is just a simple angular app, so what is the point of an image just for that?
Is it possible for me to combine these images into one, or would that require a major rewrite?
Gravatars missing (migrating from htdvisser)
Previously I was using htdvisser/taiga-back/front that's around version 3.2 and now I'm looking to update that system to 4.0. I like how you have many of the settings as environment variables. However, setting - TAIGA_GRAVATAR=true for taiga front has no effect in my local testing environment.
After some investigation I've found this: https://groups.google.com/forum/#!searchin/taigaio/gravatar|sort:date/taigaio/BmWVToJUTvs/c3ICLIs9BgAJ but I'm not yet certain how to confirm this -- nothing related to gravatar shows up in the logs.
ModuleNotFoundError: No module named 'ldap3'
Describe the bug
In a clean installation, after setup template/docker-compose.yml and template/.env files, the taiga_celery and taiga_back containers exits with this error.
To Reproduce
Steps to reproduce the behavior:
- Edit the template/docker-compose.yml with custom parameters:
- LDAP enable, others disabled
- Custom ports
- Mail settings
- Production setup with monogramm/docker-taiga-* images, not building
- Edit the template/.env with custom values
- Execute update.sh script
- Execute (image/variant/version/)docker-compose up -d
Expected behavior
All containers up and running. The ldap3 module should be included in the image.
Screenshots
Docker:
-
docker version
Client:
Version: 18.09.1
API version: 1.39
Go version: go1.11.6
Git commit: 4c52b90
Built: Sun, 21 Feb 2021 18:18:35 +0100
OS/Arch: linux/amd64
Experimental: false -
docker-compose version
docker-compose version 1.21.0, build unknown
docker-py version: 3.4.1
CPython version: 3.7.3
OpenSSL version: OpenSSL 1.1.1d 10 Sep 2019 -
Image docker-taiga-back:6.0-alpine
Desktop:
- OS: Debian 10.10
Additional context
This is the full container taiga_celery logs:
[2021-09-14T17:16:20] Compiling messages and collecting static
Enabling Taiga emails...
Taiga events enabled
Taiga async mode enabled
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 323, in run_from_argv
self.execute(*args, **cmd_options)
File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 364, in execute
output = self.handle(*args, **options)
File "/usr/local/lib/python3.7/site-packages/django/core/management/commands/compilemessages.py", line 64, in handle
basedirs.extend(settings.LOCALE_PATHS)
File "/usr/local/lib/python3.7/site-packages/django/conf/__init__.py", line 79, in __getattr__
self._setup(name)
File "/usr/local/lib/python3.7/site-packages/django/conf/__init__.py", line 66, in _setup
self._wrapped = Settings(settings_module)
File "/usr/local/lib/python3.7/site-packages/django/conf/__init__.py", line 157, in __init__
mod = importlib.import_module(self.SETTINGS_MODULE)
File "/usr/local/lib/python3.7/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
File "<frozen importlib._bootstrap>", line 983, in _find_and_load
File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 728, in exec_module
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "/usr/src/taiga-back/settings/config.py", line 12, in <module>
from ldap3 import Tls
ModuleNotFoundError: No module named 'ldap3'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "manage.py", line 27, in <module>
execute_from_command_line(sys.argv)
File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
utility.execute()
File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 375, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 336, in run_from_argv
connections.close_all()
File "/usr/local/lib/python3.7/site-packages/django/db/utils.py", line 219, in close_all
for alias in self:
File "/usr/local/lib/python3.7/site-packages/django/db/utils.py", line 213, in __iter__
return iter(self.databases)
File "/usr/local/lib/python3.7/site-packages/django/utils/functional.py", line 80, in __get__
res = instance.__dict__[self.name] = self.func(instance)
File "/usr/local/lib/python3.7/site-packages/django/db/utils.py", line 147, in databases
self._databases = settings.DATABASES
File "/usr/local/lib/python3.7/site-packages/django/conf/__init__.py", line 79, in __getattr__
self._setup(name)
File "/usr/local/lib/python3.7/site-packages/django/conf/__init__.py", line 66, in _setup
self._wrapped = Settings(settings_module)
File "/usr/local/lib/python3.7/site-packages/django/conf/__init__.py", line 157, in __init__
mod = importlib.import_module(self.SETTINGS_MODULE)
File "/usr/local/lib/python3.7/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
File "<frozen importlib._bootstrap>", line 983, in _find_and_load
File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 728, in exec_module
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "/usr/src/taiga-back/settings/config.py", line 12, in <module>
from ldap3 import Tls
ModuleNotFoundError: No module named 'ldap3'
And this is the full taiga_back container logs:
[2021-09-14T17:16:17] Running database check
Connecting to database:
dbname='taiga' user='taiga' host='taiga_db' port='5432' password='******'
Database does not appear to be setup.
[2021-09-14T17:16:18] Execute database migrations...
Enabling Taiga emails...
Taiga feedback enabled
Taiga events enabled
Taiga async mode enabled
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 323, in run_from_argv
self.execute(*args, **cmd_options)
File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 361, in execute
self.check()
File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 390, in check
include_deployment_checks=include_deployment_checks,
File "/usr/local/lib/python3.7/site-packages/django/core/management/commands/migrate.py", line 64, in _run_checks
issues = run_checks(tags=[Tags.database])
File "/usr/local/lib/python3.7/site-packages/django/core/checks/registry.py", line 72, in run_checks
new_errors = check(app_configs=app_configs)
File "/usr/local/lib/python3.7/site-packages/django/core/checks/database.py", line 9, in check_database_backends
for conn in connections.all():
File "/usr/local/lib/python3.7/site-packages/django/db/utils.py", line 216, in all
return [self[alias] for alias in self]
File "/usr/local/lib/python3.7/site-packages/django/db/utils.py", line 213, in __iter__
return iter(self.databases)
File "/usr/local/lib/python3.7/site-packages/django/utils/functional.py", line 80, in __get__
res = instance.__dict__[self.name] = self.func(instance)
File "/usr/local/lib/python3.7/site-packages/django/db/utils.py", line 147, in databases
self._databases = settings.DATABASES
File "/usr/local/lib/python3.7/site-packages/django/conf/__init__.py", line 79, in __getattr__
self._setup(name)
File "/usr/local/lib/python3.7/site-packages/django/conf/__init__.py", line 66, in _setup
self._wrapped = Settings(settings_module)
File "/usr/local/lib/python3.7/site-packages/django/conf/__init__.py", line 157, in __init__
mod = importlib.import_module(self.SETTINGS_MODULE)
File "/usr/local/lib/python3.7/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
File "<frozen importlib._bootstrap>", line 983, in _find_and_load
File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 728, in exec_module
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "/usr/src/taiga-back/settings/config.py", line 12, in <module>
from ldap3 import Tls
ModuleNotFoundError: No module named 'ldap3'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "manage.py", line 27, in <module>
execute_from_command_line(sys.argv)
File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
utility.execute()
File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 375, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 336, in run_from_argv
connections.close_all()
File "/usr/local/lib/python3.7/site-packages/django/db/utils.py", line 219, in close_all
for alias in self:
File "/usr/local/lib/python3.7/site-packages/django/db/utils.py", line 213, in __iter__
return iter(self.databases)
File "/usr/local/lib/python3.7/site-packages/django/utils/functional.py", line 80, in __get__
res = instance.__dict__[self.name] = self.func(instance)
File "/usr/local/lib/python3.7/site-packages/django/db/utils.py", line 147, in databases
self._databases = settings.DATABASES
File "/usr/local/lib/python3.7/site-packages/django/conf/__init__.py", line 79, in __getattr__
self._setup(name)
File "/usr/local/lib/python3.7/site-packages/django/conf/__init__.py", line 66, in _setup
self._wrapped = Settings(settings_module)
File "/usr/local/lib/python3.7/site-packages/django/conf/__init__.py", line 157, in __init__
mod = importlib.import_module(self.SETTINGS_MODULE)
File "/usr/local/lib/python3.7/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
File "<frozen importlib._bootstrap>", line 983, in _find_and_load
File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 728, in exec_module
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "/usr/src/taiga-back/settings/config.py", line 12, in <module>
from ldap3 import Tls
ModuleNotFoundError: No module named 'ldap3'
It's seems like the module is not installed in the docker image.
Any help would be apreciated!
*Updated the steps to reproduce
Can't enable gitlab auth
I think have assigned all needed vars and I've restarted the full stack but I can't see any "Gitlab login button" in login section, using the same email/pass that in gitlab neither works and can't see any error on container logs nor browser console, in fact in logs seems all fine:
# Backend logs
Taiga contrib GitLab Auth enabled# Frontend lgos
Updating Taiga Front contribution plugins list: 'gitlab-auth cookie-warning'
Updating Taiga Front GitLab client id and URL: https://gitlab.****.*** - c279****25eaf# From back container
env | grep -i gitlab
TAIGA_GITLAB_AUTH_URL=https://gitlab.****.***
TAIGA_GITLAB_AUTH_CLIENT_ID=c279****25eaf
TAIGA_GITLAB_AUTH_CLIENT_SECRET=7a94****a9aa1
TAIGA_ENABLE_GITLAB_AUTH=True# From front container
env | grep -i gitlab
TAIGA_CONTRIB_PLUGINS='gitlab-auth cookie-warning'
TAIGA_GITLAB_AUTH_URL=https://gitlab.****.***
TAIGA_GITLAB_AUTH_CLIENT_ID=c279****25eafIn backend logs also appears "Taiga contrib LDAP Auth Ext enabled", despite TAIGA_ENABLE_LDAP=False, not sure if could be related or is another bug.
Using 4.2-alpine images
client unexpectedly closed TCP connection
Describe the bug
After Taiga 6 deployment, taiga_rabbit container minutely generate this log entry. Taiga celery is activated, Images pulled from hub (production).
To Reproduce
Steps to reproduce the behavior:
- pull latest taiga compose file
- modify compose and env file
- docker-compose up
Expected behavior
No errors in log files ;)
Screenshots
taiga_rabbit | 2021-11-09 06:40:36.827 [info] <0.851.0> accepting AMQP connection <0.851.0> (172.20.0.1:59914 -> 172.20.0.3:5672)
taiga_rabbit | 2021-11-09 06:40:36.831 [info] <0.851.0> connection <0.851.0> (172.20.0.1:59914 -> 172.20.0.3:5672): user 'taiga' authenticated and granted access to vhost 'taiga'
taiga_rabbit | 2021-11-09 06:40:36.846 [info] <0.867.0> accepting AMQP connection <0.867.0> (172.20.0.1:59916 -> 172.20.0.3:5672)
taiga_rabbit | 2021-11-09 06:40:36.848 [info] <0.867.0> connection <0.867.0> (172.20.0.1:59916 -> 172.20.0.3:5672): user 'taiga' authenticated and granted access to vhost 'taiga'
taiga_rabbit | 2021-11-09 06:40:37.273 [warning] <0.867.0> closing AMQP connection <0.867.0> (172.20.0.1:59916 -> 172.20.0.3:5672, vhost: 'taiga', user: 'taiga'):
taiga_rabbit | client unexpectedly closed TCP connection
taiga_rabbit | 2021-11-09 06:40:37.273 [warning] <0.851.0> closing AMQP connection <0.851.0> (172.20.0.1:59914 -> 172.20.0.3:5672, vhost: 'taiga', user: 'taiga'):
taiga_rabbit | client unexpectedly closed TCP connection
Docker (please complete the following information):
Server Version: 19.03.11
docker-compose version 1.26.0, build d4451659
docker-py version: 4.2.1
CPython version: 3.7.7
eventsUrl can be edited?
Is your feature request related to a problem? Please describe.
I know this is more a question because of ignorance than a FR.
I have builded the images and have all the containers running aparently fine. But I need to modify the eventsUrl setting in the config.json in a docker volume. I have an nginx before the taiga_front to apply ssl and other security features, and the public url for the eventsUrl is wss://TAIGA_HOST/. I can edit the setting manually in the config.json and all works fine, but when I restart the taiga_front container, the setting reset to default value (ws://TAIGA_HOST:TAIGA_EVENTS_PORT).
Describe the solution you'd like
Env variables to setup the protocol (ws/wss) and port (because is distinct from the TAIGA_EVENTS_PORT envar) or know the way to modify and make persistent the change in the docker volume.
Describe alternatives you've considered
Another way is using a template to fullfill the config.json.
Sorry, because maybe I am wrong because of unknowlege.
Invalid login type when enabling LDAP in Taiga 6.0
Describe the bug
When enabling LDAP login in the production version of Taiga 6.0, no login is possible. The browser console reports "Invalid login type". The local admin user can't be used either.
To Reproduce
Clone the repository and run update.sh.
Go to images/6.0/alpine and edit .env and docker-compose.yml to enable LDAP.
Go to back/ and edit .env and Dockerfile to reflect those changes.
Go to front/ and edit .env to reflect the same changes.
Go to your-taiga-instance/login and try to login.
Excerpts from docker-compose.yml:
- TAIGA_CONTRIB_PLUGINS=
- TAIGA_LOGIN_FORM_TYPE=ldap
...
- TAIGA_LDAP_FALLBACK=normal
TAIGA_ENABLE_LDAP=True is set in all three .env files.
ENABLE_LDAP=true and LDAP_FALLBACK=normal is set in back/Dockerfile.
I suspect this to be related to Monogramm/taiga-contrib-ldap-auth-ext#39, but I can't figure out how to access common.py.
Expected behavior
Login with both LDAP and local users should work.
Docker (please complete the following information):
- Docker / Docker-compose Version: docker-compose version 1.29.2, build 5becea4c
- docker-taiga-front/back 6.0
Desktop (please complete the following information):
- OS: Windows 10
- Browser: Edge
- Version: 93.0.961.38
Thank you for your help!
traefik as reverse proxy
Hi, I get this error from taiga-front: need extra config on nginx for use your images?
thanks in advance,
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
Start nginx server...
127.0.0.1 - - [26/Apr/2019:12:48:30 +0000] "GET /conf.json HTTP/1.1" 200 855 "-" "curl/7.64.0" "-"
127.0.0.1 - - [26/Apr/2019:12:48:30 +0000] "GET / HTTP/1.1" 200 92007 "-" "curl/7.64.0" "-"
2019/04/26 12:48:30 [error] 30#30: *3 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "GET /api/v1/ HTTP/1.1", upstream: "http://172.24.0.12:8001/api/v1/", host: "localhost"
127.0.0.1 - - [26/Apr/2019:12:48:30 +0000] "GET /api/v1/ HTTP/1.1" 502 158 "-" "curl/7.64.0" "-"
Error when creating user stories
Thanks for the docker project. Its excellent.
I have an instance of Taiga running locally following your instructions. I am running on localhost port 80. I can login and create a new project. However when I try to create a user story, I get the following:
amqp.exceptions.NotAllowed: Connection.open: (530) NOT_ALLOWED - vhost '/' not found
Any pointers on how to fix the above would be appreciated.
Thanks
SSL information
I want to configure the SSL certificate, the documentation is tricky. It would be great if you add a section in the readme file about configuring an SSL certificate
taiga_back error on clean install
after clean install, an error was breaking the docker-compose up script
taiga_back | Updating "admin" user with requested password...
taiga_back | User "admin" updated with requested password
taiga_back | [2019-07-29T12:55:08] Run contrib Slack plugin migrations to generate the new needed table
taiga_back | Trying import local.py settings...
taiga_back | Enabling Taiga emails...
taiga_back | Taiga feedback enabled
taiga_back | Taiga events enabled
taiga_back | CommandError: App 'taiga_contrib_slack' does not have migrations.
taiga_back exited with code 1
i've try to disable the contrib plugins, but on next startup was following error
taiga_back | [2019-07-29T13:06:03] Compiling messages and collecting static
taiga_back | Trying import local.py settings...
taiga_back | Enabling Taiga emails...
taiga_back | Trying import local.py settings...
taiga_back | Enabling Taiga emails...
taiga_back | [2019-07-29T13:06:06] Start gunicorn server
taiga_back |
taiga_back | Error: '' is not a valid port number.
taiga_back |
taiga_back exited with code 1
Pass TAIGA _SSL=True results nginx error on base front image
- TAIGA_SSL=True
#- TAIGA_SSL_BY_REVERSE_PROXY=True
On front and back
Results on nginx error:
taiga_taiga_front.1.6l79mzo67new@z1-taiga | 2019/04/29 06:35:59 [emerg] 29#29: a duplicate default server for 0.0.0.0:80 in /etc/nginx/snippets/main.conf:1
taiga_taiga_front.1.6l79mzo67new@z1-taiga | nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/snippets/main.conf:1
taiga_taiga_front.1.6l79mzo67new@z1-taiga | nginx: configuration file /etc/nginx/nginx.conf test failed
I was triying to mount a external volume to pass the underliying nginx the letsencrypt certifcates
- /etc/letsencrypt/live/mysite:/etc/nginx/ssl:ro
Taiga 6.5
Any upgrade plans for Taiga 6.5?
btw, please fix also brocken LDAP plugin!
Error loading contrib plugins
I've tried also with 'cookie-warning' plugin with the same result so seems not related to any particular plugin, also have tried TAIGA_CONTRIB_PLUGINS=gitlab-auth and TAIGA_CONTRIB_PLUGINS='gitlab-auth', same result.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.