Skip to content

Fix docker compose - #739

Open
thesp0nge wants to merge 2 commits into
masterfrom
fix-docker-compose
Open

Fix docker compose#739
thesp0nge wants to merge 2 commits into
masterfrom
fix-docker-compose

Conversation

@thesp0nge

Copy link
Copy Markdown

In order to have the kong user as regular one and not a DBA, a custome init script it was created and the docker compose files changed accordingly

@CLAassistant

CLAassistant commented May 13, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@thesp0nge

Copy link
Copy Markdown
Author

Do we have any update on this?

Comment on lines +9 to +10
CREATE USER kong WITH NOSUPERUSER NOCREATEDB NOCREATEROLE PASSWORD :'kong_password';
CREATE DATABASE kong OWNER kong;

@locao locao Jul 9, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Before your changes, db and user were configurable (POSTGRES_DB: ${KONG_PG_DATABASE:-kong} and POSTGRES_USER: ${KONG_PG_USER:-kong}) but now both will be forced to be kong. Is it intentional? Could we keep the previous behavior?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants