-
Notifications
You must be signed in to change notification settings - Fork 832
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
serf and 0.6.0 #19
Comments
Just checking if something like the following needs to be added to the Dockerfile:
(the yum bit before the existing |
exact same issue here... did you manage to solve it ? |
This output is correct, I am not seeing anything wrong with it. The warning is just to tell the user that no nodes were found. |
But when i try to do http get to Kong API it never responds. If i try a curl http://127.0.0.1:8001/apis within the container bash it never returns anything, it looks like the http request gets hanged somewhere... and i cant ser anything wrong in the log files. |
I'm seeing the same behavior with frozen curl requests. Also, not being able to connect to serf caused disk space issues #23 |
Yeah I'm getting the exact same issue here with |
just downgraded to docker toolbox v1.8.3 and apparently it's working... can you give it a try ? |
i've tested both on my personal / work osx and the problem is solved. |
That's interesting to know but I would appreciate to use latest docker version, not |
I agree that's interesting. Does anyone know the big changes between those 2 versions? I don't believe this is a valid solution for me as I'm packaging this all in a docker-compose as a closed box solution for developers to use while developing other microservices and I'd rather not have a dependency on an old version of docker toolbox. @gottfrois Thanks for the link to the other issue. This does look like it could all be related. |
Running kong like this seems to solve serf connection issues and therefor, curl command freezing:
See #21 |
@ambrons I want to use docker-compose too, just tried and you can throw the following to make it work:
Full example:
|
@gottfrois you're the man! Did you override the Here's my whole docker-compose.yml with your addition:
|
@ambrons ah cool! I was missing this part, it was next on my todo ;) thx man |
Yep, you guys figured this out properly. From the Docker documentation at http://docs.docker.com.s3-website-us-east-1.amazonaws.com/engine/security/seccomp/
|
The documentation on the website has been updated. Thanks everybody. |
I'm running the 0.6.0 docker container, and getting this output:
I'm aware the 0.6.0 kong forces us to now use serf, but how does it relate to docker? Do I need a serf daemon on the kong container? Or a separate container with serf? Or how do I disable serf for development/testing purposes?
The text was updated successfully, but these errors were encountered: