Closed justintime4tea closed 8 years ago
I can reproduce this behaviour. The bug is caused by the recent changes of 4a13166897391f38ab2d1713bec4662138469d8d.
There is a conflict with the POSTGRES_NAME
environment variable. You can simply circumvent this bug by explicitly defining POSTGRES_NAME: taiga
in your docker-compose.yml
. Nonetheless I suggest to change the naming of the configuration variable to something more general like DB_NAME
.
Renamed POSTGRES_NAME
to POSTGRES_DB_NAME
. My apologies for merging PR#9 without fully testing it.
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