bitnami-docker-postgresql | Bitnami Docker Image for PostgreSQL | Continuous Deployment library

by bitnami Shell Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | bitnami-docker-postgresql Summary

bitnami-docker-postgresql is a Shell library typically used in Devops, Continuous Deployment, PostgresSQL, Docker applications. bitnami-docker-postgresql has no bugs, it has no vulnerabilities and it has low support. However bitnami-docker-postgresql has a Non-SPDX License. You can download it from GitHub.

PostgreSQL (Postgres) is an open source object-relational database known for reliability and data integrity. ACID-compliant, it supports foreign keys, joins, views, triggers and stored procedures. Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.

Support

Quality

Security

License

Reuse

Support

bitnami-docker-postgresql has a low active ecosystem.

It has 378 star(s) with 204 fork(s). There are 35 watchers for this library.

It had no major release in the last 6 months.

There are 15 open issues and 202 have been closed. On average issues are closed in 44 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of bitnami-docker-postgresql is current.

Quality

bitnami-docker-postgresql has 0 bugs and 0 code smells.

Security

bitnami-docker-postgresql has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

bitnami-docker-postgresql code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

bitnami-docker-postgresql has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

bitnami-docker-postgresql releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of bitnami-docker-postgresql

Get all kandi verified functions for this library.

bitnami-docker-postgresql Key Features

No Key Features are available at this moment for bitnami-docker-postgresql.

bitnami-docker-postgresql Examples and Code Snippets

No Code Snippets are available at this moment for bitnami-docker-postgresql.

Community Discussions

Trending Discussions on bitnami-docker-postgresql

CrashLoopBackOff on postgresql bitnami helm chart

/opt/bitnami/scripts/postgresql/entrypoint.sh: line 30: exec: max_connections=500: not found

postgresql container not starting: chmod: changing permissions of '/bitnami/postgresql/data': Operation not permitted

Helm postgres cannot create directory

QUESTION

CrashLoopBackOff on postgresql bitnami helm chart

Asked 2022-Jan-04 at 18:31

I know there have been already a lot of questions about this, and I read already most of them, but my problem does not seem to fit them.

I am running a postgresql from bitnami using a helm chart as described below. A clean setup is no problem and everything starts fine. But after some time, until now I could not find any pattern, the pod goes into CrashLoopBackOff and I cannot recover it whatever I try!

Helm uninstall/install does not fix the problem. The PVs seem to be the problem, but I do not know why. And I do not get any error message, which is the weird and scary part of it.

I use a minikube to run the k8s and helm v3.

Helm chart: https://artifacthub.io/packages/helm/bitnami/postgresql/10.9.5

Here are the definitions and logs:

...

ANSWER

Answered 2022-Jan-04 at 18:31

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:

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

Source https://stackoverflow.com/questions/70122497

QUESTION

/opt/bitnami/scripts/postgresql/entrypoint.sh: line 30: exec: max_connections=500: not found

Asked 2021-Aug-11 at 02:27

Today I want to increase PostgreSQL max conenctions, then I add config to my kubernetes PostgreSQL config:

...

ANSWER

Answered 2021-Aug-11 at 02:26

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.

Source https://stackoverflow.com/questions/68735163

QUESTION

postgresql container not starting: chmod: changing permissions of '/bitnami/postgresql/data': Operation not permitted

Asked 2020-Sep-17 at 08:52

bitnami/postgresql is unable to start with volume mount. I am using 10.14.0 version of the official docker image.

Container starts without the volume mount:

...

ANSWER

Answered 2020-Sep-17 at 08:52

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.

Source https://stackoverflow.com/questions/63924161

QUESTION

Helm postgres cannot create directory

Asked 2020-Aug-06 at 13:02

I'm using Helm to deploy postgres on Kubernetes cluster. I create a persistent volume and a persistent volume claim:

pv.yaml:

...

ANSWER

Answered 2020-Aug-06 at 13:02

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.

Source https://stackoverflow.com/questions/63283477

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install bitnami-docker-postgresql

A Streaming replication cluster can easily be setup with the Bitnami PostgreSQL Docker Image using the following environment variables:. In a replication cluster you can have one master and zero or more slaves. When replication is enabled the master node is in read-write mode, while the slaves are in read-only mode. For best performance its advisable to limit the reads to the slaves. The first step is to start the master. In this command we are configuring the container as the master using the POSTGRESQL_REPLICATION_MODE=master parameter. A replication user is specified using the POSTGRESQL_REPLICATION_USER and POSTGRESQL_REPLICATION_PASSWORD parameters. Next we start a replication slave container. In the above command the container is configured as a slave using the POSTGRESQL_REPLICATION_MODE parameter. Before the replication slave is started, the POSTGRESQL_MASTER_HOST and POSTGRESQL_MASTER_PORT_NUMBER parameters are used by the slave container to connect to the master and replicate the initial database from the master. The POSTGRESQL_REPLICATION_USER and POSTGRESQL_REPLICATION_PASSWORD credentials are used to authenticate with the master. In order to change the pg_hba.conf default settings, the slave needs to know if POSTGRESQL_PASSWORD is set. With these two commands you now have a two node PostgreSQL master-slave streaming replication cluster up and running. You can scale the cluster by adding/removing slaves without incurring any downtime. Note: The cluster replicates the master in its entirety, which includes all users and databases.
POSTGRESQL_REPLICATION_MODE: Replication mode. Possible values master/slave. No defaults.
POSTGRESQL_REPLICATION_USER: The replication user created on the master on first run. No defaults.
POSTGRESQL_REPLICATION_PASSWORD: The replication users password. No defaults.
POSTGRESQL_REPLICATION_PASSWORD_FILE: Path to a file that contains the replication users password. This will override the value specified in POSTGRESQL_REPLICATION_PASSWORD. No defaults.
POSTGRESQL_MASTER_HOST: Hostname/IP of replication master (slave parameter). No defaults.
POSTGRESQL_MASTER_PORT_NUMBER: Server port of the replication master (slave parameter). Defaults to 5432.
POSTGRESQL_SYNCHRONOUS_COMMIT_MODE: Establishes the type of synchronous commit. The available options are: on, remote_apply, remote_write, local and off. The default value is on. For more information, check the official PostgreSQL documentation.
POSTGRESQL_NUM_SYNCHRONOUS_REPLICAS: Establishes the number of replicas that will enable synchronous replication. This number must not be above the number of slaves that you configure in the cluster.
Bitnami provides up-to-date versions of PostgreSQL, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container. or if you're using Docker Compose, update the value of the image property to bitnami/postgresql:latest. Stop the currently running container using the command.

Support

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page. Subscribe to project updates by watching the bitnami/postgresql GitHub repo.

Find more information at: