Getting internal server error when running Dockerized dev environment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Poppy |
Fix Released
|
Low
|
Amit Gandhi |
Bug Description
I have setup the Dockerized development environment by running "./dev up" from the "docker/fig/" directory. The Docker images are built just fine and containers are spun up just fine as well. When I try to make an API request, however, I get a 500 Internal Server Error response:
$ curl -v 'http://
* About to connect() to 192.168.59.103 port 81 (#0)
* Trying 192.168.59.103...
* Adding handle: conn: 0x7f8c1a004400
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleT
* - Conn 0 (0x7f8c1a004400) send_pipe: 1, recv_pipe: 0
* Connected to 192.168.59.103 (192.168.59.103) port 81 (#0)
> GET /v1.0/services HTTP/1.1
> User-Agent: curl/7.30.0
> Host: 192.168.59.103:81
> Accept: */*
>
< HTTP/1.1 500 Internal Server Error
< Connection: close
< Content-Type: text/plain
<
* Closing connection 0
Internal Server Error
The docker log for the poppy dev container (poppydev_1) shows these error messages:
poppydev_1 | --- no python application found, check your startup logs for errors ---
poppydev_1 | [pid: 16|app: -1|req: -1/1] 192.168.59.3 () {36 vars in 670 bytes} [Mon Dec 8 11:58:51 2014] GET /v1.0/services => generated 21 bytes in 0 msecs (HTTP/1.1 500) 2 headers in 83 bytes (0 switches on core 0)
I'm working off git commit sha d6d5b95f6f7c4a3
description: | updated |
description: | updated |
Changed in poppy: | |
status: | Incomplete → In Progress |
assignee: | nobody → Amit Gandhi (amit-gandhi) |
milestone: | ongoing → kilo-2 |
importance: | Undecided → Low |
Changed in poppy: | |
status: | Fix Committed → Fix Released |
I made a few changes to the Docker Fig setup in git commit ha 92b8e6994222643 48836a371474660 191779d7b2 that may fix this issue.
Can you please try again. Be sure to read the updated Readme file as there are changes due to adding support for Rackspace Cloud DNS.
Let me know if you are still having issues.