mirror of
https://github.com/bitnami/containers.git
synced 2026-03-21 23:38:32 +08:00
2.0.3-debian-10-r2 release
This commit is contained in:
@@ -10,14 +10,14 @@ COPY prebuildfs /
|
||||
# Install required system packages and dependencies
|
||||
RUN install_packages ca-certificates curl libc6 libgcc1 libpcre3 libssl1.1 libyaml-0-2 perl procps sudo unzip zlib1g
|
||||
RUN . /opt/bitnami/scripts/libcomponent.sh && component_unpack "kong" "2.0.3-0" --checksum bc3ee3cecff31386a2e778e29a74ff2259ef4c3da3f62a811fffd0a75caf4276
|
||||
RUN . /opt/bitnami/scripts/libcomponent.sh && component_unpack "gosu" "1.11.0-3" --checksum c18bb8bcc95aa2494793ed5a506c4d03acc82c8c60ad061d5702e0b4048f0cb1
|
||||
RUN . /opt/bitnami/scripts/libcomponent.sh && component_unpack "gosu" "1.12.0-0" --checksum 582d501eeb6b338a24f417fededbf14295903d6be55c52d66c52e616c81bcd8c
|
||||
RUN apt-get update && apt-get upgrade -y && \
|
||||
rm -r /var/lib/apt/lists /var/cache/apt/archives
|
||||
|
||||
COPY rootfs /
|
||||
RUN /opt/bitnami/scripts/kong/postunpack.sh
|
||||
ENV BITNAMI_APP_NAME="kong" \
|
||||
BITNAMI_IMAGE_VERSION="2.0.3-debian-10-r1" \
|
||||
BITNAMI_IMAGE_VERSION="2.0.3-debian-10-r2" \
|
||||
PATH="/opt/bitnami/kong/bin:/opt/bitnami/kong/openresty/bin:/opt/bitnami/kong/openresty/luajit/bin:/opt/bitnami/kong/openresty/nginx/sbin:/opt/bitnami/common/bin:$PATH"
|
||||
|
||||
EXPOSE 8000 8001 8443 8444
|
||||
|
||||
@@ -28,28 +28,16 @@ $ docker-compose up -d
|
||||
|
||||
> This [CVE scan report](https://quay.io/repository/bitnami/kong?tab=tags) contains a security report with all open CVEs. To get the list of actionable security issues, find the "latest" tag, click the vulnerability report link under the corresponding "Security scan" field and then select the "Only show fixable" filter on the next page.
|
||||
|
||||
# How to deploy Kong in Kubernetes?
|
||||
|
||||
You can find an example for testing Kong in Kubernetes with the `test.yaml` file. To launch it, run the command:
|
||||
|
||||
```console
|
||||
$ kubectl apply -f test.yaml
|
||||
```
|
||||
|
||||
> NOTE: If you are pulling from a private container registry, replace the image name with the full URL to the docker image, e.g.:
|
||||
>
|
||||
> - image: 'your-registry/image-name:your-version'
|
||||
|
||||
# Why use a non-root container?
|
||||
|
||||
Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers [in our docs](https://docs.bitnami.com/containers/how-to/work-with-non-root-containers/).
|
||||
Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers [in our docs](https://docs.bitnami.com/tutorials/work-with-non-root-containers/).
|
||||
|
||||
# Supported tags and respective `Dockerfile` links
|
||||
|
||||
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/).
|
||||
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.bitnami.com/tutorials/understand-rolling-tags-containers/).
|
||||
|
||||
|
||||
* [`2-debian-10`, `2.0.3-debian-10-r1`, `2`, `2.0.3`, `latest` (2/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-kong/blob/2.0.3-debian-10-r1/2/debian-10/Dockerfile)
|
||||
* [`2-debian-10`, `2.0.3-debian-10-r2`, `2`, `2.0.3`, `latest` (2/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-kong/blob/2.0.3-debian-10-r2/2/debian-10/Dockerfile)
|
||||
|
||||
Subscribe to project updates by watching the [bitnami/kong GitHub repo](https://github.com/bitnami/bitnami-docker-kong).
|
||||
|
||||
|
||||
Reference in New Issue
Block a user