htdvisser / taiga-docker Goto Github PK

Hi for some reason data container is not loaded... someone know why?
nothing to show in docker logs...

In our case, the solution was installing the package locales and setting the default location to en_US.utf8 with this command on taiga-back:
locale-gen en_US.utf8

I noticed really recent changes that may have broken the provisioning pipeline?

I had the docker-compose htdvisser/taiga group of containers working flawlessly yesterday somewhere around 12:00pm PST but after coming home attempted to pull/run again I got failing results. Image wouldn't finish pulling and/or extracting and would simply hang.

I do see you are actively working on this now so I'm sure if it's not isolated to my system and is a real issue you'll hash this out soon enough. Thought I'd leave a snippet of the failure in my logs in-case they help narrow down the issue at all or perhaps I've made a common mistake and you've encountered this as well at some point :)

I am a developer as well so if you need anything tested or additional log entries/analysis let me know!

[.../taiga-docker.git/]:[$] docker-compose up

taigaback_1  | Copying '/usr/local/taiga/taiga-back/taiga/base/api/static/api/js/prettify-min.js'
taigaback_1  | Copying '/usr/local/taiga/taiga-back/taiga/base/api/static/api/js/jquery-1.8.1-min.js'
taigaback_1  | Copying '/usr/local/taiga/taiga-back/taiga/users/static/img/user-noimage.png'
taigaback_1  | 
taigaback_1  | 950 static files copied to '/usr/local/taiga/static'.
taigaback_1  | Waiting for Postgresql to be available...
db_1         |  done
db_1         | server started
db_1         | CREATE DATABASE
db_1         | 
db_1         | CREATE ROLE
db_1         | 
db_1         | 
db_1         | /docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
db_1         | 
db_1         | LOG:  received fast shutdown request
db_1         | LOG:  aborting any active transactions
db_1         | LOG:  autovacuum launcher shutting down
db_1         | LOG:  shutting down
db_1         | waiting for server to shut down....LOG:  database system is shut down
db_1         |  done
db_1         | server stopped
db_1         | 
db_1         | PostgreSQL init process complete; ready for start up.
db_1         | 
db_1         | LOG:  database system was shut down at 2015-09-30 14:05:23 UTC
db_1         | LOG:  MultiXact member wraparound protections are now enabled
db_1         | LOG:  database system is ready to accept connections
db_1         | LOG:  autovacuum launcher started
db_1         | LOG:  incomplete startup packet
db_1         | FATAL:  database "/taigadocker_taigaback_1/postgres" does not exist
taigaback_1  | Trying import local.py settings...
taigaback_1  | Traceback (most recent call last):
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/__init__.py", line 133, in ensure_connection
taigaback_1  |     self.connect()
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/transaction_hooks/mixin.py", line 75, in connect
taigaback_1  |     super(TransactionHooksDatabaseWrapperMixin, self).connect(*a, **kw)
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/__init__.py", line 122, in connect
taigaback_1  |     self.connection = self.get_new_connection(conn_params)
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/postgresql_psycopg2/base.py", line 130, in get_new_connection
taigaback_1  |     connection = Database.connect(**conn_params)
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/psycopg2/__init__.py", line 164, in connect
taigaback_1  |     conn = _connect(dsn, connection_factory=connection_factory, async=async)
taigaback_1  | psycopg2.OperationalError: FATAL:  database "/taigadocker_taigaback_1/postgres" does not exist
taigaback_1  | 
taigaback_1  | 
taigaback_1  | The above exception was the direct cause of the following exception:
taigaback_1  | 
taigaback_1  | Traceback (most recent call last):
taigaback_1  |   File "manage.py", line 10, in <module>
taigaback_1  |     execute_from_command_line(sys.argv)
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/core/management/__init__.py", line 385, in execute_from_command_line
taigaback_1  |     utility.execute()
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/core/management/__init__.py", line 377, in execute
taigaback_1  |     self.fetch_command(subcommand).run_from_argv(self.argv)
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/core/management/base.py", line 288, in run_from_argv
taigaback_1  |     self.execute(*args, **options.__dict__)
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/core/management/base.py", line 338, in execute
taigaback_1  |     output = self.handle(*args, **options)
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/core/management/commands/migrate.py", line 63, in handle
taigaback_1  |     executor = MigrationExecutor(connection, self.migration_progress_callback)
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/executor.py", line 17, in __init__
taigaback_1  |     self.loader = MigrationLoader(self.connection)
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/loader.py", line 48, in __init__
taigaback_1  |     self.build_graph()
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/loader.py", line 183, in build_graph
taigaback_1  |     self.applied_migrations = recorder.applied_migrations()
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/recorder.py", line 59, in applied_migrations
taigaback_1  |     self.ensure_schema()
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/recorder.py", line 49, in ensure_schema
taigaback_1  |     if self.Migration._meta.db_table in self.connection.introspection.get_table_list(self.connection.cursor()):
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/__init__.py", line 167, in cursor
taigaback_1  |     cursor = utils.CursorWrapper(self._cursor(), self)
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/__init__.py", line 138, in _cursor
taigaback_1  |     self.ensure_connection()
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/__init__.py", line 133, in ensure_connection
taigaback_1  |     self.connect()
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/db/utils.py", line 94, in __exit__
taigaback_1  |     six.reraise(dj_exc_type, dj_exc_value, traceback)
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/utils/six.py", line 658, in reraise
taigaback_1  |     raise value.with_traceback(tb)
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/__init__.py", line 133, in ensure_connection
taigaback_1  |     self.connect()
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/transaction_hooks/mixin.py", line 75, in connect
taigaback_1  |     super(TransactionHooksDatabaseWrapperMixin, self).connect(*a, **kw)
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/__init__.py", line 122, in connect
taigaback_1  |     self.connection = self.get_new_connection(conn_params)
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/postgresql_psycopg2/base.py", line 130, in get_new_connection
taigaback_1  |     connection = Database.connect(**conn_params)
taigaback_1  |   File "/usr/local/lib/python3.4/site-packages/psycopg2/__init__.py", line 164, in connect
taigaback_1  |     conn = _connect(dsn, connection_factory=connection_factory, async=async)
taigaback_1  | django.db.utils.OperationalError: FATAL:  database "/taigadocker_taigaback_1/postgres" does not exist
taigaback_1  | 
taigaback_1  | 2015-09-30 14:05:26 circus[21] [INFO] Starting master on pid 21
taigaback_1  | 2015-09-30 14:05:26 circus[21] [INFO] Arbiter now waiting for commands
taigaback_1  | 2015-09-30 14:05:26 circus[21] [INFO] taiga started
taigaback_1  | 2015-09-30 14:05:26 circus[21] [INFO] circusd-stats started
taigaback_1  | 2015-09-30 14:05:26 circus[26] [INFO] Starting the stats streamer

Hey!

I'm trying to install taiga on synology using your script. Unfortunately there seems no way to change the postgres port number. Tee port 5432 is already used by the Synology postgres and not usable in docker.

Is there a way to add it to the settings?

So I finally got your image up and running - thank you.

One issue I found though was that the ENV vars I am setting in the docker-compose are not copying correctly to the server dockerenv.py. I found this out sending myself an invitation and hitting reply tried to forward to http://dev/invitation/89a88866-1b3b-11e6-aeab-0242ac110002 instead of my FQDN dev.mysite.com

I went in the container and replaced those images but when I restart I guess it reads the vars from the docker image and overwrites them again.

Running docker-compose up results in this error:

taigaback_1 | tcp://172.17.0.3:5432: forward host lookup failed: Unknown host

I believe I followed all the instructions.

I could connect to the postgresql db in cntainer taigaback_1 through the psql.

Hi there, thanks so much for dockerizing taiga.io. It's super useful for a bunch of my projects that need a quick collaboration tool.

I've been having a problem with file attachments uploads though. While uploads seem to proceed, and I can add the name and save them there, they disappear upon reloading the page. This happens with uploads attached to both wiki pages and kanban stories.

Any thoughts?

i did docker-compose -f taiga.yml

taiga.yml:

data:
  image: tianon/true
  volumes:
    - /var/lib/postgresql/data
    - /usr/local/taiga/media
    - /usr/local/taiga/static
    - /usr/local/taiga/logs

db:
  image: postgres
  environment:
    POSTGRES_USER: taiga
    POSTGRES_PASSWORD: password
  volumes_from:
    - data
  restart: always

taigaback:
  build: taiga-back
  hostname: dev.example.com
  environment:
    SECRET_KEY: examplesecretkey
    EMAIL_USE_TLS: 'True'
    EMAIL_HOST: smtp.gmail.com
    EMAIL_PORT: 587
    EMAIL_HOST_USER: [email protected]
    EMAIL_HOST_PASSWORD: mypassword
    POSTGRES_HOST: postgres
    POSTGRES_PORT: 5432
  links:
    - db:postgres
  volumes_from:
    - data
  restart: always

taigafront:
  build: taiga-front-dist
  hostname: 0.0.0.0
  links:
    - taigaback
  volumes_from:
    - data
  ports:
    - 0.0.0.0:9000:80
  restart: always

when i logged in with admin:123123 the useravatar looks like this:

What is my problem?

See https://taigaio.github.io/taiga-doc/dist/setup-production.html#_async_tasks_optional

Hi everybody,

I'm trying to get taiga-docker to run on a Synology Diskstation. I managed to get the containers for the taiga-back, taiga-front and postgres running. Also I did run

python manage.py migrate --noinput
python manage.py loaddata initial_user
python manage.py loaddata initial_project_templates
python manage.py loaddata initial_role
python manage.py compilemessages
python manage.py collectstatic --noinput

as mentioned here to create the admin user.

I can access the login page of taiga. But when I try to login as admin with password 123123 nothing happens. In the chrome developer console i can see, that I'm getting an 502 Bad Gateway for the request to /api/v1/auth

I found the following issue which looks a lot like what I'm expiriencing, but in my case the admin part is already available.

Any ideas how to fix this? Any help would be appreciated.

Might be good to add restart: always for the containers.

~/taiga-back$ python manage.py migrate --noinput
Trying import local.py settings...
Traceback (most recent call last):
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/backends/base/base.py", line 199, in ensure_connection
self.connect()
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/backends/base/base.py", line 171, in connect
self.connection = self.get_new_connection(conn_params)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/backends/postgresql/base.py", line 176, in get_new_connection
connection = Database.connect(**conn_params)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/psycopg2/init.py", line 130, in connect
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
psycopg2.OperationalError: FATAL: Peer authentication failed for user "taiga"

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "manage.py", line 29, in
execute_from_command_line(sys.argv)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/core/management/init.py", line 367, in execute_from_command_line
utility.execute()
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/core/management/init.py", line 359, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/core/management/base.py", line 294, in run_from_argv
self.execute(*args, **cmd_options)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/core/management/base.py", line 345, in execute
output = self.handle(*args, **options)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/core/management/commands/migrate.py", line 83, in handle
executor = MigrationExecutor(connection, self.migration_progress_callback)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/migrations/executor.py", line 20, in init
self.loader = MigrationLoader(self.connection)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/migrations/loader.py", line 52, in init
self.build_graph()
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/migrations/loader.py", line 203, in build_graph
self.applied_migrations = recorder.applied_migrations()
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/migrations/recorder.py", line 65, in applied_migrations
self.ensure_schema()
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/migrations/recorder.py", line 52, in ensure_schema
if self.Migration._meta.db_table in self.connection.introspection.table_names(self.connection.cursor()):
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/backends/base/base.py", line 231, in cursor
cursor = self.make_debug_cursor(self._cursor())
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/backends/base/base.py", line 204, in _cursor
self.ensure_connection()
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/backends/base/base.py", line 199, in ensure_connection
self.connect()
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/utils.py", line 94, in exit
six.reraise(dj_exc_type, dj_exc_value, traceback)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/utils/six.py", line 685, in reraise
raise value.with_traceback(tb)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/backends/base/base.py", line 199, in ensure_connection
self.connect()
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/backends/base/base.py", line 171, in connect
self.connection = self.get_new_connection(conn_params)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/backends/postgresql/base.py", line 176, in get_new_connection
connection = Database.connect(**conn_params)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/psycopg2/init.py", line 130, in connect
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
django.db.utils.OperationalError: FATAL: Peer authentication failed for user "taiga"~/taiga-back$ python manage.py migrate --noinput
Trying import local.py settings...
Traceback (most recent call last):
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/backends/base/base.py", line 199, in ensure_connection
self.connect()
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/backends/base/base.py", line 171, in connect
self.connection = self.get_new_connection(conn_params)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/backends/postgresql/base.py", line 176, in get_new_connection
connection = Database.connect(**conn_params)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/psycopg2/init.py", line 130, in connect
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
psycopg2.OperationalError: FATAL: Peer authentication failed for user "taiga"

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "manage.py", line 29, in
execute_from_command_line(sys.argv)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/core/management/init.py", line 367, in execute_from_command_line
utility.execute()
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/core/management/init.py", line 359, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/core/management/base.py", line 294, in run_from_argv
self.execute(*args, **cmd_options)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/core/management/base.py", line 345, in execute
output = self.handle(*args, **options)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/core/management/commands/migrate.py", line 83, in handle
executor = MigrationExecutor(connection, self.migration_progress_callback)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/migrations/executor.py", line 20, in init
self.loader = MigrationLoader(self.connection)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/migrations/loader.py", line 52, in init
self.build_graph()
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/migrations/loader.py", line 203, in build_graph
self.applied_migrations = recorder.applied_migrations()
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/migrations/recorder.py", line 65, in applied_migrations
self.ensure_schema()
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/migrations/recorder.py", line 52, in ensure_schema
if self.Migration._meta.db_table in self.connection.introspection.table_names(self.connection.cursor()):
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/backends/base/base.py", line 231, in cursor
cursor = self.make_debug_cursor(self._cursor())
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/backends/base/base.py", line 204, in _cursor
self.ensure_connection()
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/backends/base/base.py", line 199, in ensure_connection
self.connect()
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/utils.py", line 94, in exit
six.reraise(dj_exc_type, dj_exc_value, traceback)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/utils/six.py", line 685, in reraise
raise value.with_traceback(tb)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/backends/base/base.py", line 199, in ensure_connection
self.connect()
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/backends/base/base.py", line 171, in connect
self.connection = self.get_new_connection(conn_params)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/django/db/backends/postgresql/base.py", line 176, in get_new_connection
connection = Database.connect(**conn_params)
File "/home/ubuntu/.virtualenvs/taiga/lib/python3.5/site-packages/psycopg2/init.py", line 130, in connect
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
django.db.utils.OperationalError: FATAL: Peer authentication failed for user "taiga"

I had installed taigadocker on one host, but now I need migrate them to a new host, what should I do ?

Hi, someone know if possible install the new version of taiga 3.0.0 whit the taiga.yml of this repo?
https://blog.taiga.io/taiga-stellaria-borealis-release-300.html

Regards,

When using docker-compose, if your database container is named "postgres," compose will auto-create an environment variable called POSTGRES_PORT that looks like "tcp://172.x.y.z:5432". That is, unless the variable already has a value.

So if you don't specifically declare POSTGRES_PORT in docker-compose or elsewhere, the value above will be filled in for POSTGRES_PORT and taiga-back will try to use it as the port to connect to. It fails in the "waiting for postgres" stage within the start script, because nc chokes.

As a workaround, I simply declare POSTGRES_HOST=postgres and POSTGRES_PORT=5432 within docker-compose.yml. This works well if your database is linked as "postgres".

I was wondering if your Docker images are up to date? I do not see the SSL configuration taking effect.

I ran:
docker pull htdvisser/taiga-front-dist:stable
docker run htdvisser/taiga-front-dist:stable cat /usr/local/taiga/configure

The script I see does not include the ssl configuration like I see here:
https://github.com/htdvisser/taiga-docker/blob/stable/taiga-front-dist/configure

It's the bad time when I change the docker default setting to new a new machine.
And I found it have some problem to usage it and I remove the machine at time.
Then I run the taiga in default machine, and it just jump to the error page that wirte the words - Something happened and our Oompa Loompas are working on it.

And I got the message open() "/usr/local/taiga/taiga-front-dist/dist/js/conf.json" failed (2: No such file or directory) int taigafront's log.

More like this:

2016/05/22 15:48:51 [error] 12#0: *1 open() "/usr/local/taiga/taiga-front-dist/dist/js/conf.json" failed (2: No such file or directory), client: 192.168.99.1, server: localhost, request: "GET /js/conf.json HTTP/1.1", host: "192.168.99.100", referrer: "http://192.168.99.100/"

192.168.99.1 - - [22/May/2016:15:48:51 +0000] "GET /js/conf.json HTTP/1.1" 404 191 "http://192.168.99.100/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36" "-"

2016/05/22 15:48:58 [error] 12#0: *1 open() "/usr/local/taiga/taiga-front-dist/dist/js/conf.json" failed (2: No such file or directory), client: 192.168.99.1, server: localhost, request: "GET /js/conf.json HTTP/1.1", host: "192.168.99.100", referrer: "http://192.168.99.100/"

192.168.99.1 - - [22/May/2016:15:48:58 +0000] "GET /js/conf.json HTTP/1.1" 404 191 "http://192.168.99.100/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36" "-"

192.168.99.1 - - [22/May/2016:15:50:33 +0000] "GET / HTTP/1.1" 304 0 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Kitematic/0.10.2 Chrome/45.0.2454.85 Electron/0.35.4 Safari/537.36" "-"

192.168.99.1 - - [22/May/2016:15:50:33 +0000] "GET /conf.json HTTP/1.1" 200 264 "http://192.168.99.100/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Kitematic/0.10.2 Chrome/45.0.2454.85 Electron/0.35.4 Safari/537.36" "-"

192.168.99.1 - - [22/May/2016:15:50:35 +0000] "GET /v-1461931321319/locales/taiga/locale-en.json HTTP/1.1" 304 0 "http://192.168.99.100/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Kitematic/0.10.2 Chrome/45.0.2454.85 Electron/0.35.4 Safari/537.36" "-"`

The version 1.7.0 of TaigaIO has been released. An update would be lovely :)

It appears the following commands need to be executed manually from inside the container, after starting up with docker-compose:

cd /usr/local/taiga/taiga-back
python manage.py migrate --noinput
python manage.py loaddata initial_user
python manage.py loaddata initial_project_templates
python manage.py loaddata initial_role
python manage.py collectstatic --noinput

i did docker-compose -f taiga.yml

taiga.yml:

data:
  image: tianon/true
  volumes:
    - /var/lib/postgresql/data
    - /usr/local/taiga/media
    - /usr/local/taiga/static
    - /usr/local/taiga/logs

db:
  image: postgres
  environment:
    POSTGRES_USER: taiga
    POSTGRES_PASSWORD: password
  volumes_from:
    - data
  restart: always

taigaback:
  build: taiga-back
  hostname: dev.example.com
  environment:
    SECRET_KEY: examplesecretkey
    EMAIL_USE_TLS: 'True'
    EMAIL_HOST: smtp.gmail.com
    EMAIL_PORT: 587
    EMAIL_HOST_USER: [email protected]
    EMAIL_HOST_PASSWORD: mypassword
    POSTGRES_HOST: postgres
    POSTGRES_PORT: 5432
  links:
    - db:postgres
  volumes_from:
    - data
  restart: always

taigafront:
  build: taiga-front-dist
  hostname: 0.0.0.0
  links:
    - taigaback
  volumes_from:
    - data
  ports:
    - 0.0.0.0:9000:80
  restart: always

root@ds:/usr/local/taiga/taiga-back# python manage.py loaddata initial_role
Trying import local.py settings...
CommandError: No fixture named 'initial_role' found.

When trying to install using docker-compose, process hangs at:
taigaback_1 | 2016-08-14 17:02:33 circus[67] [INFO] Starting the stats streamer

Compose Log
http://pastebin.com/FQCQTMLL

Contents of docker-compose.yml
data:
image: tianon/true
volumes:
- /var/lib/postgresql/data
- /usr/local/taiga/media
- /usr/local/taiga/static
- /usr/local/taiga/logs
db:
image: postgres
environment:
POSTGRES_USER: taiga
POSTGRES_PASSWORD: redacted
volumes_from:
- data
taigaback:
build: taiga-back
hostname: redacted
environment:
EMAIL_USE_TLS: 'False'
EMAIL_HOST: redacted
EMAIL_PORT: 587
EMAIL_HOST_USER: redacted
EMAIL_HOST_PASSWORD: redacted
links:
- db:postgres
volumes_from:
- data
taigafront:
build: taiga-front-dist
hostname: redacted
links:
- taigaback
volumes_from:
- data
ports:
- 0.0.0.0:20080:20080

I may be wrong but it appears none of the local changes to files are respected/used during the docker-compose "up" process?

I say this because in your Dockerfiles you do not copy local files you instead pull from github each time. Is this the case? Are local changes not being copied into the containers and instead the same Github-repo files used everytime? Then what's the point of local env settings? (please let me know if I'm wrong, just going off dockerfile and observation) Should I fork your repo, commit my changes to my fork, replace your repo in Dockerfiles with my fork and THEN my env-conf will be pulled during container creation?

Maybe I'm wrong but I cannot for the LIFE of me seem to change the DB name and it keeps failing looking for a DB that does not exist. The file "dockerenv.py" never gets ANY of the env-vars I set in either the docker-compose.yml(taiga.yml) or the individual Dockerfiles within taiga-back.

I'm not new to working with pre-built images (can build my own fine as well) I'm simply trying to weed through all of the different BASH scripts and things your team has built to "auto-magic" setup these containers and cannot figure out to "force" my env-vars to be used.

I'm not trying to bash anyone (no pun intended) I am just trying to provide feedback and figure out where the heck I am going wrong. Sometimes Dockerfiles and pre-built images can be a rat maze >_<

If anyone has even just 10 minutes to help me hash this out it would be much appreciated. I am a seasoned enterprise developer so it's not like helping some uber newb ;) Apologies if this issue is isolated to my system and I am out-of-line. I will gladly remove issue if this is the case.

I'm not working with Taiga anymore, and therefore looking for maintainers for this project. Please comment on this issue if you're interested.

Hi,

First, thank's for your work. I installed taiga using your docker-compose and I am unable to create a new user. I get 502 (Bad Gateway) on api/v1/auth/register.
I found this issue that may be related taigaio/taiga-back/#244.
So I looked at my /usr/local/taiga/taiga-back/settings/local.py as mentioned in the taiga documentation and found there is nothing in it about email configuration whereas I set all EMAIL_ environments variables in docker-compose.yml
Is it an error or did I miss something ?