-
Notifications
You must be signed in to change notification settings - Fork 98
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
Postgres v10.6 is actually v12 #223
Comments
Hi @holmesb, I believe the answer lies in your Rockstor version:
Indeed, we have had several improvements directly related to using different tags for the same docker image since 3.9.2-48. In particular:
My recommendation would thus to first uninstall your postgresql rock-on, refresh your list of rock-ons by clicking the "Update" button on the Rock-ons page, then update your Rockstor install to the latest version (now 3.9.2-56), and then refresh again your list of rock-ons, and then installing the postgres rock-on should pull the correct version. Hope this helps, |
Hi @FroggyFlox I suspected as much. After I switched from stable to testing, it's unclear how I can force the update to start. I've enabled auto-updates. Must I wait for the next scheduled update event to occur? Version (shown on the webui) has changed down to 3.9.2-1. I also can't access the rockon page now |
Hello again @holmesb, I see you have posted this up/down grade issue in the forum. I'll link to that and pick it up there. |
Upgrading rockstor to latest version per @FroggyFlox's suggestion has fixed. Thanks also to @phillxnet helping me upgrade. |
I won't profess to be a rockon expert, but somehow the tag isn't causing this version to be pulled.
A
docker inspect <container>
gives:I'm using rockstor 3.9.2-48
The text was updated successfully, but these errors were encountered: