-
using the docker :latest, I recently updated, to what appears to be a pre-release? v8.2.2-pre now my system is effed up with server error 500, which I only deiscovered today I tried upgrading to v8.3.1 which didn't fix the error in the laravel.log I see snipeit.maintenances database table or view does not exist. I believe the prior version I was running was v8.2.1 can anyone advise a fix here I would believe that :latest would be a production ready tag, if it's mixed with pre-releases etc, which tags should I use to keep my platform stable? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
You'll need to run migrations. (See the Docker tab in your case.) v8.2.2-pre wasn't a pre-release, it was stable on master, just in between releases. The :latest tag will always have what's on the master branch (which is what we deploy from). https://hub.docker.com/r/snipe/snipe-it/tags - if you want to be locked into a specific version, you should pull the tag from that version. |
Beta Was this translation helpful? Give feedback.
-
thanks for the clarification that latest is stable. if anyone sees this with the same error: |
Beta Was this translation helpful? Give feedback.
You'll need to run migrations. (See the Docker tab in your case.)
v8.2.2-pre wasn't a pre-release, it was stable on master, just in between releases. The :latest tag will always have what's on the master branch (which is what we deploy from). https://hub.docker.com/r/snipe/snipe-it/tags - if you want to be locked into a specific version, you should pull the tag from that version.