Bobcares

Bitnami Postgres | All About

by | Jul 21, 2022

Bitnami Postgres is an open source ORDBMS that provides better data integrity and reliability. Here our Support team provides an overview of Bitnami Postgres.

At Bobcares, as part of our Server Management service, responds to all questions.

Let’s take a closer look at Bitnami Postgres in detail.

What is Bitnami Postgres?

Postgres (PostgreSQL) is an object-relational database that provides reliability and data integrity. Postgres is open source and supports foreign keys, joins, views, triggers, and stored procedures.

Bitnami has packaged this software listing and hence the name.

Bitnami Image

A Bitnami image contains everything we need to run the preferred Bitnami packaged application. The installation and configuration of all software in the stack are completely automated. So it is simple for anyone, including non-technical users, to get them up and running.

How to get the Bitnami PostgreSQL Docker Image?

The simple way is to pull the prebuilt image from the Docker Hub Registry using the command:

$ docker pull bitnami/postgresql:latest

To get the Bitnami Postgres, we can also use a versioned tag to use a specific version. The Docker Hub Registry contains a list of available versions.

$ docker pull bitnami/postgresql:[TAG]

Maintaining the database

If we remove the container, we will lose all data and configurations. When we run the image next time, it re-initializes the database. To avoid data loss, we should mount a volume that will survive the removal of the container.

While going with Bitnami Postgres, for persistence we should mount a directory at the /bitnami/postgresql path. Then on the first run, it initializes the mounted directory if it is empty.

$ docker run \
-v /path/to/postgresql-persistence:/bitnami/postgresql \
bitnami/postgresql:latest

We can also do it by modifying the docker-compose.yml file. We can find it in the repository:

services:
  postgresql:
  ...
    volumes:
     - /path/to/postgresql-persistence:/bitnami/postgresql
  ...

How to connect with other containers?

A Bitnami Postgres server running inside a container can be easily accessed by the application containers. It is possible using Docker container networking. Containers on the same network can communicate by using the container name as the hostname. The two methods for connecting to other containers are:

Using the Command Line
  1. Firstly, create a network with the command:

    $ docker network create app-tier --driver bridge

  2. Then launch the PostgreSQL server instance using the command:
    $ docker run -d --name postgresql-server \
        --network app-tier \
        bitnami/postgresql:latest
  3. Finally, launch the Bitnami Postgres client instance with the command:
    $ docker run -it --rm \
        --network app-tier \
        bitnami/postgresql:latest psql -h postgresql-server -U postgres
Using the Docker Compose

In this section, we will explicitly define a new bridge network called app-tier. Consider that we want to connect to the PostgreSQL server from our own custom application image. So here the service name myapp identifies it.

version: '2'

networks:
  app-tier:
    driver: bridge

services:
  postgresql:
    image: 'bitnami/postgresql:latest'
    networks:
      - app-tier
  myapp:
    image: 'YOUR_APPLICATION_IMAGE'
    networks:
      - app-tier

Also, remember to update the YOUR_APPLICATION_IMAGE_  placeholder in the above snippet with our application image. In the application container, use the hostname postgresql to connect to the PostgreSQL server. Lastly, launch the containers with the command:

$ docker-compose up -d

[Looking for an answer to another question? We’re only a mouse click away.]

Conclusion

The installation and configuration of all of the software included in the Bitnami stack are completely automated. Thus making it easy for everyone, including those who are not very technical, to get them up and running. To conclude, our Support team went over the Bitnami Postgres detail.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF