-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Official way to include extensions #340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Yeah, I think noting this in the image description is probably a good idea
to help reduce the potential for confusion around it. 👍
|
would be cool to mention "official" way to activate already installed extensions; for example. I have to run |
Not any mean
credit: https://www.reddit.com/r/docker/comments/ea70rz/why_did_adding_a_postgres_extension_to_the_base/ |
based on @phluan 's work, here's the |
What is the official way of adding postgres extensions, given postgres-alpine is a base image?
I tried to add
postgresql-pglogical
andpostgis
extensions by installing respectiveapk
packages, but this process, despite being the most intuitive and straightforward, failed for me.Here's my
Dockerfile
:Opening a now-closed issue in apline linux tracker made me realize that in a container above I ended up having two postgreses installed:
apk
(apk
has to make sure that for given packages to install all dependencies are met; forpostgresql-pglogical
andpostgis
package calledpostgres
is a dependency).I can see other issues asking for clarification around adding extensions:
Maybe it makes sense to include a statement in a readme? Something like:
The text was updated successfully, but these errors were encountered: