Cristian Chiru

This is strange, I do not have such issue on Kubernetes. What are you trying to do? I can see that the default container user has id 1000, but `/usr/local/kong`...

I have set default user in the Dockerfile to `kong` and made a new release. Can you please test?

I cannot reproduce this... for me works just fine. 1. Can you please provide the yamls you are loading? 2. I see the image you are using is not from...

I am using Kong exclusively with dbless, in Kubernetes. I do not get such error, and I am having a hard time figuring this out. If you enable ingress, dbless...

Perhaps this is related to https://github.com/revomatico/docker-kong-oidc/pull/14?

## Context 1. Deployed 4.x PGO and a postgres instance 2. Upgraded PGO to 5.0.x then 5.1 3. The new PostgresCluster CR is now using the latest exporter: `registry.developers.crunchydata.com/crunchydata/crunchy-postgres-exporter:ubi8-5.1.0-0` ##...

``` ./test.sh Created container: 8414f3c7190b8b3979846860ac289992c93fde4e2edf18615abcdd8776707faf Host: headers.4tools.net Connection: keep-alive X-Forwarded-For: 172.17.0.1 X-Forwarded-Proto: http X-Forwarded-Host: localhost X-Forwarded-Port: 180 X-Forwarded-Path: /request.php X-Real-IP: 172.17.0.1 User-Agent: curl/7.81.0 Accept: */* Success!!! Deleted container: docker-kong-oidc ```

The weird part is that the constant is defined, as expected. The issue has a different cause root cause, but the message is misleading. Those constants are used exactly like...

Sorry for the late response, can you please update the rockspec? saw just now you made almost the same changes as a previous PR