I have the following deployment: 1 apiVersion: apps/v1 1 kind: Deployment 2 metadata: 3 name: postgres-deployment 4 spec: 5 replicas: 1 6 selector: 7 matchLabels: 8 component: postgres 9 template: 10 metadata: 11 labels: 12 component: postg…

The problem is that when you mount that volume claim, it’s essentially taking the place of the content at the mountPath. [protosam@nullhost]$ docker run --rm -it prikshet/postgres sh $ ls -lah /var/lib/postgresql/data/postgresql.conf -rw------- 1 postgres postgres 28K Aug 9 10:50 /var/lib/postgres…

Instead of doing a config map, I simply copy this file to another directory and run postgres with the configuration in the changed directory using -c config_file: 1 FROM postgres:latest 1 ARG VERSION 2 3 COPY deployment/postgres_init /docker-entrypoint-initdb.d 4 USER postgres 5 RUN ini…

It’s a permissions issue. The FATAL error explicitly tells you what directory the permission problem exists on and the HINT tells you how to fix it. This is actually a pretty basic Linux issue and I highly recommend studying Linux from a comprehensive guide like this one , if you aren’t familiar wit…

Protosam, the problem is that you cannot start postgres as root because postgres doesn’t allow that and that directory seems to be owned by root when it’s mounted but owned by the user when it’s not mounted. So it seems like a kubernetes problem since I don’t know how to change the permissions of a …

That’s not at all what I’m elluding to. I guess it might not be obvious exactly how to fix perms. Fix the perms with an init container. Sorry btw, normally I’d drop a link to init containers but I’m on my phone right now.

This is what I’ve tried: [image] How to mount the directory with a specific user? General Discussions Basically I have this postgres image: 1 FROM postgres:latest 1 COPY deployment/postgres_init /docker-entrypoint-initdb.d 2 USER 999 3 RUN initdb 4 CMD postgres …

I still stand by init containers for this issue. You need to manipulate the data before the container with the actual data is running. [image] Init Containers This page provides an overview of init containers: specialized containers that run before app containers in a Pod. Init containe…

You might also be able to get some results by setting securityContext.fsGroup for the volume. It would still be owned by root though as the user and I don’t know of a way to change that other than using an init container to run a script to correct permissions.

Could you tell me what exactly the init container config would look like in this case? I put the following: initContainers: - name: change-user image: busybox:latest command: ['chown', '-R', 'postgres', '/var/lib/postgresql/data'] But it gives the error: I…

The container spec is going to be the same format as any other container. You need to assign volumeMounts to each container that should have volume mounts, including init containers. For the command you can also do this. It’s good for when you need to do multiple things against your volume mount. c…

Postgresql.conf not found when using volume mount

General Discussions

zendevil August 10, 2021, 3:18pm 7

This is what I’ve tried:

Topic		Replies	Views
Unable to mount postgrsql data directory with persistance volume General Discussions	0	808	October 25, 2019
Mounted directory has the wrong ownership General Discussions	1	2493	August 13, 2021
How to mount the directory with a specific user? General Discussions	0	1263	August 10, 2021
Postgres pod with local directory mounted for data General Discussions	7	8304	August 18, 2020
Write permissions on volume mount with security context fsgroup option General Discussions	6	116755	April 13, 2023

Postgresql.conf not found when using volume mount

Related topics