You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 10-2.5/README.md
+17-5Lines changed: 17 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,9 +8,10 @@ This image ensures that the default database created by the parent `postgres` im
8
8
9
9
*`postgis`
10
10
*`postgis_topology`
11
-
*`fuzzystrmatch`
12
11
*`postgis_tiger_geocoder`
13
12
13
+
Note: As of PostGIS v3.x, raster has been factored out into a separate extension `postgis_raster` which must be installed separately.
14
+
14
15
Unless `-e POSTGRES_DB` is passed to the container at startup time, this database will be named after the admin user (either `postgres` or the user specified with `-e POSTGRES_USER`). If you would prefer to use the older template database mechanism for enabling PostGIS, the image also provides a PostGIS-enabled template database called `template_postgis`.
15
16
16
17
## Usage
@@ -21,10 +22,21 @@ In order to run a basic container capable of serving a PostGIS-enabled database,
21
22
22
23
For more detailed instructions about how to start and control your Postgres container, see the documentation for the `postgres` image [here](https://registry.hub.docker.com/_/postgres/).
23
24
24
-
Once you have started a database container, you can then connect to the database as follows:
25
-
26
-
docker run -it --link some-postgis:postgres --rm postgres \
27
-
sh -c 'exec psql -h "$POSTGRES_PORT_5432_TCP_ADDR" -p "$POSTGRES_PORT_5432_TCP_PORT" -U postgres'
25
+
Once you have started a database container, you can then connect to the database either directly on the running container:
26
+
27
+
docker exec -ti some-postgis psql -U postgres
28
+
29
+
... or starting a new container to run as a client. In this case you can use a user-defined network to link both containers:
30
+
31
+
docker network create some-network
32
+
33
+
# Server container
34
+
docker run --name some-postgis --network some-network -e POSTGRES_PASSWORD=mysecretpassword -d postgis/postgis
Check the documentation on the [`postgres` image](https://registry.hub.docker.com/_/postgres/) and [Docker networking](https://docs.docker.com/network/) for more details and alternatives on connecting different containers.
28
40
29
41
See [the PostGIS documentation](http://postgis.net/docs/postgis_installation.html#create_new_db_extensions) for more details on your options for creating and using a spatially-enabled database.
Copy file name to clipboardExpand all lines: 10-3.1/README.md
+17-5Lines changed: 17 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,9 +8,10 @@ This image ensures that the default database created by the parent `postgres` im
8
8
9
9
*`postgis`
10
10
*`postgis_topology`
11
-
*`fuzzystrmatch`
12
11
*`postgis_tiger_geocoder`
13
12
13
+
Note: As of PostGIS v3.x, raster has been factored out into a separate extension `postgis_raster` which must be installed separately.
14
+
14
15
Unless `-e POSTGRES_DB` is passed to the container at startup time, this database will be named after the admin user (either `postgres` or the user specified with `-e POSTGRES_USER`). If you would prefer to use the older template database mechanism for enabling PostGIS, the image also provides a PostGIS-enabled template database called `template_postgis`.
15
16
16
17
## Usage
@@ -21,10 +22,21 @@ In order to run a basic container capable of serving a PostGIS-enabled database,
21
22
22
23
For more detailed instructions about how to start and control your Postgres container, see the documentation for the `postgres` image [here](https://registry.hub.docker.com/_/postgres/).
23
24
24
-
Once you have started a database container, you can then connect to the database as follows:
25
-
26
-
docker run -it --link some-postgis:postgres --rm postgres \
27
-
sh -c 'exec psql -h "$POSTGRES_PORT_5432_TCP_ADDR" -p "$POSTGRES_PORT_5432_TCP_PORT" -U postgres'
25
+
Once you have started a database container, you can then connect to the database either directly on the running container:
26
+
27
+
docker exec -ti some-postgis psql -U postgres
28
+
29
+
... or starting a new container to run as a client. In this case you can use a user-defined network to link both containers:
30
+
31
+
docker network create some-network
32
+
33
+
# Server container
34
+
docker run --name some-postgis --network some-network -e POSTGRES_PASSWORD=mysecretpassword -d postgis/postgis
Check the documentation on the [`postgres` image](https://registry.hub.docker.com/_/postgres/) and [Docker networking](https://docs.docker.com/network/) for more details and alternatives on connecting different containers.
28
40
29
41
See [the PostGIS documentation](http://postgis.net/docs/postgis_installation.html#create_new_db_extensions) for more details on your options for creating and using a spatially-enabled database.
Copy file name to clipboardExpand all lines: 11-2.5/README.md
+17-5Lines changed: 17 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,9 +8,10 @@ This image ensures that the default database created by the parent `postgres` im
8
8
9
9
*`postgis`
10
10
*`postgis_topology`
11
-
*`fuzzystrmatch`
12
11
*`postgis_tiger_geocoder`
13
12
13
+
Note: As of PostGIS v3.x, raster has been factored out into a separate extension `postgis_raster` which must be installed separately.
14
+
14
15
Unless `-e POSTGRES_DB` is passed to the container at startup time, this database will be named after the admin user (either `postgres` or the user specified with `-e POSTGRES_USER`). If you would prefer to use the older template database mechanism for enabling PostGIS, the image also provides a PostGIS-enabled template database called `template_postgis`.
15
16
16
17
## Usage
@@ -21,10 +22,21 @@ In order to run a basic container capable of serving a PostGIS-enabled database,
21
22
22
23
For more detailed instructions about how to start and control your Postgres container, see the documentation for the `postgres` image [here](https://registry.hub.docker.com/_/postgres/).
23
24
24
-
Once you have started a database container, you can then connect to the database as follows:
25
-
26
-
docker run -it --link some-postgis:postgres --rm postgres \
27
-
sh -c 'exec psql -h "$POSTGRES_PORT_5432_TCP_ADDR" -p "$POSTGRES_PORT_5432_TCP_PORT" -U postgres'
25
+
Once you have started a database container, you can then connect to the database either directly on the running container:
26
+
27
+
docker exec -ti some-postgis psql -U postgres
28
+
29
+
... or starting a new container to run as a client. In this case you can use a user-defined network to link both containers:
30
+
31
+
docker network create some-network
32
+
33
+
# Server container
34
+
docker run --name some-postgis --network some-network -e POSTGRES_PASSWORD=mysecretpassword -d postgis/postgis
Check the documentation on the [`postgres` image](https://registry.hub.docker.com/_/postgres/) and [Docker networking](https://docs.docker.com/network/) for more details and alternatives on connecting different containers.
28
40
29
41
See [the PostGIS documentation](http://postgis.net/docs/postgis_installation.html#create_new_db_extensions) for more details on your options for creating and using a spatially-enabled database.
0 commit comments