docker-compose results in broken application

[frodopwns]

I am attempting to run the development environment described here:
http://lyft.github.io/confidant/advanced/contributing/#quickstart-for-testing-or-development

I clone the confidant repo, copy the dev config to a service.env (sourced it for good measure) then I ran docker-compose up which resulted in running containers but no functioning app at http://localhost:80

confidant_1 | [2015-11-09 15:56:14 +0000] [1] [INFO] Starting gunicorn 19.3.0
confidant_1 | [2015-11-09 15:56:14 +0000] [1] [INFO] Listening at: http://0.0.0.0:80 (1)
confidant_1 | [2015-11-09 15:56:14 +0000] [1] [INFO] Using worker: gevent
confidant_1 | [2015-11-09 15:56:14 +0000] [12] [INFO] Booting worker with pid: 12
confidant_1 | [2015-11-09 15:56:14 +0000] [15] [INFO] Booting worker with pid: 15
confidant_1 | [2015-11-09 15:56:44 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:12)
confidant_1 | [2015-11-09 15:56:44 +0000] [12] [INFO] Worker exiting (pid: 12)
confidant_1 | [2015-11-09 15:56:44 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:15)

This is inside a Ubuntu 14.04 VM

[ryan-lane]

I just checked with an Ubuntu 14.04 VM, after deleting all containers and images in docker. When I did a docker-compose up it downloaded everything from docker hub and started, then I was able to connect successfully to 127.0.0.1:80.

Do you have something else running on port 80? Was dynamodb able to write into /mnt/dynamo? If confidant can't write to dynamo, it may hang forever, giving you the timeouts. It's a bit odd that you didn't get a stacktrace there.

[frodopwns]

Following the instructions here: http://lyft.github.io/confidant/advanced/contributing/#quickstart-for-testing-or-development

Created the service.env, added my AWS credentials.

This is a Ubuntu 14.04 VM on Vagrant/Virtualbox

$ docker version Client: Version: 1.9.0

/mnt/dynamodb exists but there doesn't appear to be anything in it...no complaints from dynamo in output.

[ryan-lane]

Hey, sorry about the late reply. It sounds like dynamo isn't creating your database. You should definitely get a stacktrace now if you make sure to do a docker pull on lyft/confidant

[ryan-lane]

Hey. Just checking in to see if you're still having an issue with this. Did you get this working?

[ryan-lane]

I'll close this out since there's no response. If you're still having issues let me know and I'll reopen the issue.