Skip to content

Specify postgis versions in docker tags #18

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

Closed
JacobHayes opened this issue Feb 4, 2016 · 6 comments
Closed

Specify postgis versions in docker tags #18

JacobHayes opened this issue Feb 4, 2016 · 6 comments

Comments

@JacobHayes
Copy link
Contributor

We have deployed databases that are on 9.3/2.1 (in process of migrating to 9.5/2.2) and don't want to upgrade developer databases until we have a clear migration path for deployed environments. Since these images aren't tagged with the postgis version we can't stay on 2.1 without vendoring the old dockerfile (which we'd rather not do).

9.x/2.1 combinations wouldn't necessarily need to be maintained, like 9.0 is now - tagged, but not updated.

@JacobHayes
Copy link
Contributor Author

I don't think this is a PR sort of thing since the tags are handled outside this repo, otherwise I'd submit one. :)

@md5
Copy link
Contributor

md5 commented Feb 4, 2016

Since I'm using Docker Hub's automated builds, it's difficult for me to maintain multiple sets of tags. The other complication is the fact that there is no longer a 2.1 version of the postgis package on apt.postgresql.org, so it's no longer possible to build a 9.3-2.1 image unless you leave out that package (resulting in the userspace utilities being dropped).

I took a look at the build details on Docker Hub and it looks like you should be able to pull the last build of 9.3-2.1 like so:

$ docker pull mdillon/postgis@sha256:aff8d882c76395e7c76bd1910b130c601d4ca2984c900c1723a167b770fb19d8

@md5
Copy link
Contributor

md5 commented Feb 4, 2016

@JacobHayes
Copy link
Contributor Author

Unfortunate how the userland package is managed. Thanks for the image/sha, that'll work great!

I'm haven't used the automated builds, but could there be Dockerfiles, with just FROM mdillon/postgis@sha256:{latest_built_sha} where that would point to the pre-2.2 image tags? That's basically what I plan to do internally.

@md5
Copy link
Contributor

md5 commented Feb 5, 2016

There could be Dockerfiles like that as automated builds, but I'd rather not maintain them myself. The problem is that if there are security updates for the postgres images, I won't be able to update the 2.1 images unless I have an alternate Dockerfile that removes the postgis package.

@JacobHayes
Copy link
Contributor Author

I don't mean maintain them, simply to create them, have them tagged as 9.x-2.1 (maybe with a -deprecated or similar) and then they could be removed. There is currently a 9.0 image tag that won't be updated, these would be in the same boat.

Any way, thank you for your help, I'll go ahead and close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants