docker-postgres | A Dockerized PostgreSQL development server | Continuous Deployment library

Change the host to; host.docker.internal.

This depends on the Os you are using. In order to access the host's network from within a container you will need to use the host's IP address in the docker. Conveniently, on Windows and Max this is resolved using the domain host.docker.internal from within the container. As specified in docker's documentation:

I want to connect from a container to a service on the host

The host has a changing IP address (or none if you have no network access). We recommend that you connect to the special DNS name host.docker.internal which resolves to the internal IP address used by the host. This is for development purpose and will not work in a production environment outside of Docker Desktop for Mac.

There is also a workaround for this in linux which has been answered in What is linux equivalent of "host.docker.internal"

I really hope nobody else runs across this, but finally I found the problem and for once it was not only between the chair and the monitor, but also RTFM was involved.

As mentioned I am using minikube to run my k8s cluster which provides PVs stored on the host disk. Where it is stored you may ask? Exaclty, here: /tmp/hostpath-provisioner/default/data-sessiondb-0/data/. You find the problem? No, I also took some time to figure it out. WHY ON EARTH does minikube use the tmp folder to store persistant volume claims?

This folder gets autom. cleared every now and so on.

SOLUTION: Change the path and DO NOT STORE PVs IN tmp FOLDERS.

They mention this here: https://minikube.sigs.k8s.io/docs/handbook/persistent_volumes/#a-note-on-mounts-persistence-and-minikube-hosts and give an example.

But why use the "dangerous" tmp path per default and not, let's say, data without putting a Warning banner there?

Sigh. Closing this question ^^

--> Workaround: https://github.com/kubernetes/minikube/issues/7511#issuecomment-612099413

Github issues to this topic:

• https://github.com/kubernetes/minikube/issues/7511
• https://github.com/kubernetes/minikube/issues/13038
• https://github.com/kubernetes/minikube/issues/3318
• https://github.com/kubernetes/minikube/issues/5144

My Github issue for clarification in the docs: https://github.com/kubernetes/minikube/issues/13038#issuecomment-981821696

If you open the link that Bitnami helpfully provided you right there in the output you can find the documentation for the image. https://github.com/bitnami/bitnami-docker-postgresql#configuration-file seems to be the most relevant part to you though.

It turns out that the answer is that PyCharm does not currently support docker-compose version 2, because it is still in beta. I simply should still be using docker-compose version 1.29.2.

As for why I was using docker-compose version 2, apparently the Docker cask on Homebrew defaults to enabling the "Use Docker Compose V2" Experimental Feature. I was able to disable this in my Docker Desktop settings.

I think the error is related to the location of your deploy-scripts directory. You attempt to perform a copy from the parent folder and this is not possible.

The path must be inside the context of the build; you cannot COPY ../something /something, because the first step of a docker build is to send the context directory (and subdirectories) to the docker daemon. src

It must be in a sub-directory of the directory containing your Dockerfile.

Bitnami Engineer here,

As the Bitnami PostgreSQL container is a non-root container, the user with id 1001 needs to have write permissions in the local folder you are mounting.

Try setting the helm charts volumePermissions.enabled to true.

Sometimes the cluster settings don't give the running container enough permissions to actuall write to the mounted volume by default.

You could use pg_dump to backup the data, btw, pg_dump is available in pgadmin, check it out