-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kong don't work on Docker Cloud #1836
Comments
What I see that you setting wrong Environment, You would need to prefix |
So the issue appears to be with Cassandra 2.2 and It also appears to be resolved in Docker itself here: moby/moby#26659 The only issue appears to be getting the Docker Host (node) updated. 😞 There is a suggestion in docker-library/cassandra#56 that setting an environment variable pointing to the name of the container would solve things but haven't gotten it to work yet: |
@gfamorimo - Got it working! Here's my stack config below. Note that the The important part is:
Here's the full config...
|
You shouldn't startup like this in compose. You need a
And my Dockerfile for kong
And my compose file for kong(I build the Docker image and stored it to my private docker registry)
|
Closing this, as it looks like there's no actionable work to take, and a solution has been posted. |
Hi guys, I've spended all day trying make Kong work on Docker Cloud, but without success.
I've tried with cassandra and postgresql, without success for both.
I've tried with stack(similar docker-compose) and with one container for each part(Kong and Cassandra).
For both, I received the error bellow.
Steps To Reproduce
1.Stack
Additional Details & Logs
[kong-database-1]2016-11-20T02:08:04.334023633Z Unknown listen_address '172.17.0.11 10.7.0.12'
[kong-database-1]2016-11-20T02:08:04.334489365Z ERROR 02:08:04 Exception encountered during startup: Unknown listen_address '172.17.0.11 10.7.0.12'
[kong-1]2016-11-20T02:08:56.579175542Z Error: /usr/local/share/lua/5.1/kong/cmd/start.lua:18: [cassandra error] All hosts tried for query failed. 127.0.0.1: connection refused for socket with peer 127.0.0.1.
So, someone had success trying put Kong on Docker-Cloud?
The text was updated successfully, but these errors were encountered: