mirror of
https://github.com/ciur/papermerge.git
synced 2026-04-25 12:05:58 +03:00
[GH-ISSUE #312] Update Docker to 2.0.0.rc35 #248
Labels
No labels
2.1
3.0
3.0.1
3.0.2
3.0.3
3.0.3
3.1
3.2
3.2
3.3
3.5
3.x
Fixed. Waiting for feedback.
Fixed. Waiting for feedback.
UX
Version 2.1 - alpha
XSS
announcement
beta
blocker
bug
cannot reproduce
confirmed
confirmed
critical
demo
dependencies
deployment
detchnical debt
discussion
docker
documentation
donations
duplicate
enhancement
feature request
frontend
fundraising
good first issue
good issue
help wanted
high
implemented
important
improvement
incomplete
invalid
investigation
kubernetes
low
low impact
medium
medium
medium impact
migration from 2.0
migration from 2.1
missing-language
missing-ocr-language
no-activity
note
ocr
outofscope
packaging
performance
popular request
pull-request
pypi
question
raspberry pi
roadmap
search
security
setup
status
task
technical debt
updates
user xp
version 1.4.0 - demo
will be implemented
will not be implemented
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/papermerge#248
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @w4tzmann on GitHub (Feb 25, 2021).
Original GitHub issue: https://github.com/ciur/papermerge/issues/312
Originally assigned to: @ciur on GitHub.
Description
A clear and concise description of what the bug is.
Changed the papermerge images flages from 'latest' to '2.0.0.rc35'. After starting the containers again, i receive Server Error (500).
db container logs:
papermerge_worker log:
Expected
Login page without error
Actual
Website response with Server Error 500 -Looks for me like there was no update for the db schema.
Info:
@ciur commented on GitHub (Feb 26, 2021):
@w4tzmann, thank you for reporting this. The issue is because new schema changes are not applied. It is docker image issue. I will fix it.
@ciur commented on GitHub (Feb 26, 2021):
I close this issue as duplicate of #311.
@yieldhog commented on GitHub (Feb 27, 2021):
@ciur
I am getting this same problem with a fresh installation (Linuxserver latest image). It looks as if others are having the same problem. An issue has been opened with linuxserver.
https://www.reddit.com/r/Papermerge/comments/ls7dq3/new_update_broke_my_instance_docker/
@ciur commented on GitHub (Feb 27, 2021):
@yieldhog,
yes, there is an issue with upgrading from 1.5.x to 2.0.0. I fixed it and tomorrow I will release next release candidate (together with reported XSS problems fixed as well) .
@yieldhog commented on GitHub (Feb 27, 2021):
@ciur,
Thanks, appreciate your work on this -- excited to check it out. Just an FYI, if feedback is helpful at all, this was a new (fresh) installation, not an upgrade.