-
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
unknown directive "ssl_certificate_by_lua" #400
Comments
What OS are you using? |
Before cloning rm -rf /etc/kong/ And master should work. |
@thefosk Thanks, I'll give it a try and I'll report back here. I'm trying to build Kong (from master branch) inside docker, and integrate it into a docker-compose setup with dockerfile mashape/cassandra. |
@thefosk I've attempted to run the following command before continuing and building the source from the master branch:
Unfortunatly, I got the same output when continuing:
P.s. I'm using debian:jessie as baseimage for my Dockerfile |
@thefosk I've created a gist that illustrates more what I currently have: https://gist.github.com/dirkmoors/b466461b0a7ee9d45fc0 |
I received the same error when using an unpatched version of OpenResty. When I patched and installed OpenResty then the error went away. |
@jasonmotylinski-dowjones What do you mean by 'patched' vs 'unpatched'? Could you elaborate more on how you fixed it? |
@dirkmoors Here in the packaging scripts OpenResty source code is downloaded, patched, and built: https://github.com/Mashape/kong/blob/master/distributions/.build-package-script.sh#L159-L182 These commands will output OpenResty to I submitted a pull request for creating a Vagrant box. In this diff OpenResty is built and install into it's default location which solved the problem for me: https://github.com/Mashape/kong/pull/396/files#diff-b870d96f4620ca5a0a12ef59aeab7b6e |
Instead of manually patching OpenResty (it's an option), you can take the following steps:
|
+1 |
@thefosk & @jasonmotylinski-dowjones thanks! That seems to have worked! |
@thefosk The complete solution I came up with: I've also created a proposal to integrate my approach into your docker-kong repo: |
Hello,
I'm trying to get the master branch working, but I'm running into the following issue:
How can I solve that?
Thanks in advance!
The text was updated successfully, but these errors were encountered: