Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fix(setcap) #206

Merged
merged 3 commits into from
Jan 5, 2019
Merged

fix(setcap) #206

merged 3 commits into from
Jan 5, 2019

Commits on Dec 19, 2018

  1. chore(*) bump to Kong 0.15.0

    @hutchic
    hutchic committed Dec 19, 2018
    Configuration menu
    Copy the full SHA
    a3e3191 View commit details
    Browse the repository at this point in the history

Commits on Dec 21, 2018

  1. fix(setcap) move setcap out of the Dockerfile into the docker-entrypo… 

    …int.sh
    @hutchic
    hutchic committed Dec 21, 2018
    Configuration menu
    Copy the full SHA
    84a2213 View commit details
    Browse the repository at this point in the history

Commits on Jan 5, 2019

  1. feat(entrypoint) auto-setcap if transparent 

    * auto-detect 'transparent' suffix in listeners to trigger setcap
* ability to force setcap with new `SET_CAP_NET_RAW` env variable
* run master and worker processes as kong with su-exec
    * requires a workaround for /dev/stdout and /dev/stderr output

Unfortunately, `kong prepare` still has to be executed as root (as it is
the case prior to this patch), but trying to execute it as the kong user
doesn't seem to work. Will revisit later.

Co-authored-by: Colin Hutchinson <[email protected]>
    @thibaultcha @hutchic
    thibaultcha and hutchic committed Jan 5, 2019
    Configuration menu
    Copy the full SHA
    67a8f7a View commit details
    Browse the repository at this point in the history