Bobcares

How to add PostGIS extension to PostgreSQL Docker

PDF Header PDF Footer

Learn how to add PostGIS extension to PostgreSQL using Docker. Our PostgreSQL Support team is here to help you with your questions and concerns.

How to add PostGIS extension to PostgreSQL Docker

Are you ready to install PostgreSQL with the PostGIS extension and PgAdmin 4 via Docker?

Our experts have put together this handy guide to help you out:

  1. Docker Installation
  2. PostgreSQL 12 Installation
  3. PgAdmin 4 Installation
  4. Configure PgAdmin 4

1. Docker Installation

To begin with, we have to head to the official Docker website and download the Docker Desktop for our operating system. Then, run the installation. It is a simple process that gets us started for our PostgreSQL and PostGIS setup.

2. PostgreSQL 12 Installation

Now, it is time to install PostgreSQL 12 with the PostGIS extension.

How to add PostGIS extension to PostgreSQL Docker

  1. First, open a terminal and create a local folder.
  2. Then, create a Docker volume and mount it in this folder as seen here:
    docker volume create --driver local –name=pgvolume
  3. Now, it is time to set up environment parameters by creating a file named `pg-env.list` and add our configurations and save the file.
  4. After that, we have to create a network bridge to connect PostgreSQL 12 and PgAdmin 4 containers.
    docker network create --driver bridge pgnetwork
  5. Then, run the PostgreSQL Docker container by pulling the required image as seen here:
       docker run --publish 5432:5432 --volume=pgvolume:/pgdata --env-file=pg-env.list --name=postgres --hostname=postgres --network=pgnetwork --detach crunchydata/crunchy-postgres-gis:centos7–12.5–3.0–4.5.1

This will take some time, but after completion, we will have a fully functional PostgreSQL database with PostGIS.

3. PgAdmin 4 Installation

  1. To begin with, create a Docker volume for PgAdmin 4:
    docker volume create --driver local –name=pga4volume
  2. Now, create a file named `pgadmin-env.list` and add our settings.
  3. After that, run the PgAdmin 4 Docker container by pulling the necessary image:
    docker run --publish 5050:5050 --volume=pga4volume:/var/lib/pgadmin --env-file=pgadmin-env.list --name=pgadmin4 --hostname=pgadmin4 --network=pgnetwork --detach crunchydata/crunchy-pgadmin4:centos7–12.5–4.5.1

4. Configure PgAdmin 4

Now, it is time to open our browser and head to `localhost:5050`.

We can log in with the credentials mentioned in `pgadmin-env.list`.

After logging in, we have to create a server. Then pass the ports, username, and password we created during the PostgreSQL installation.

Alternatively, we can do this:

  1. First, make sure we have a running PostgreSQL Docker container.
  2. Then, get the PostGIS Docker image and stop the running PostgreSQL container.
  3. After that, we have to create a new container that links our PostgreSQL container with the PostGIS extension as seen here:
    sudo docker run -d --name postgis_postgres -e POSTGRES_PASSWORD=postgrespassword -e POSTGRES_USER=postgres -v /path/to/local/folder:/var/lib/postgresql/data -p 8000:8000 kartoza/postgis:9.6-2.4
  4. Now, we can enter the running container:
    sudo docker exec -it postgis_postgres bash
  5. After that, link to the PostgreSQL console admin:
    psql -h localhost -p 5432 -U postgres
  6. Finally, we can create the PostGIS extension:
    postgres=# CREATE EXTENSION postgis;

After the above steps, we have successfully set up a development environment with PostgreSQL, PostGIS, and PgAdmin 4 using Docker.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Experts demonstrated how to add a PostGIS extension to PostgreSQL using Docker.

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 *

Docker Support

Spend time on your business, not on your servers.

Managing a server is time consuming. Whether you are an expert or a newbie, that is time you could use to focus on your product or service. Leave your server management to us, and use that time to focus on the growth and success of your business.

TALK TO US Or click here to learn more.

Speed issues driving customers away?
We’ve got your back!

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