search

taigaio / taiga-docker

Mozilla Public License 2.0
1.22k stars 305 forks source link

[BUG] Env variables deprecation in latest RabbitMQ version #34

Closed Muarline closed 3 years ago

Muarline commented 3 years ago

Describe the bug

RabbitMQ deprecated in the 3.9 release a bunch of environment variables that were used by the taiga-docker repository. Containers taiga-async-rabbitmq and taiga-events-rabbitmq fail to start because of this change. Both stable and main branches are affected.

How can we reproduce the behavior

Clone the repo from stable or main branch. Run ./launch-taiga.sh. Both containers will exit with an error.

Workarounds

Specify a concrete RabbitMQ version in the image tag (e.g. rabbitmq:3-management-alpine -> rabbitmq:3.8-management-alpine).

Desktop (please complete the following information):

curiv commented 3 years ago

Muarline's workaround worked for me.

But still on /discover page I see: Something happened and the Taiga has captured the error to be able to work on it.

And no logs after it

regzon commented 3 years ago

@hesoyamimi Strange, we've applied this fix and Taiga works fine now on every page. Are other containers alive? What do you mean by "no logs"? Like, no logs in the browser client, or in all docker containers?

curiv commented 3 years ago

@hesoyamimi Strange, we've applied this fix and Taiga works fine now on every page. Are other containers alive? What do you mean by "no logs"? Like, no logs in the browser client, or in all docker containers?

I just figured that out. Previously there were no logs in docker. Before the first launch I had an error about docker-compose version. I downgraded it to 2.2 and it worked untill web app started.

After It I decided to update docker-compose package to the latest version (current was pretty old). After it I received no errors and http interface just loaded fine.