mirror of
https://github.com/snibox/snibox.git
synced 2026-04-25 15:56:04 +03:00
[GH-ISSUE #57] Broke after docker upgrade? #50
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/snibox#50
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 @DeviantEng on GitHub (Jul 24, 2019).
Original GitHub issue: https://github.com/snibox/snibox/issues/57
I've been running Snibox in a Docker Stack for a while, and it has been working great. Recently upgraded, pulled a new version of snibox docker, and now it's not working. Here is my stack file:
When I browse to the web, I get the follow:
Log file:
I've tried running
/app/bin/update, but to no avail. Any help?@vavgustov commented on GitHub (Jul 24, 2019):
try to run
and then restart
@DeviantEng commented on GitHub (Jul 25, 2019):
@vavgustov Thanks for the quick reply.
Unfortunately that didn't help, and I did restart the full stack. Same error in web, and same messages in the log file. I've also tried manually running
db:migrate, thinking that might be related but it also hasn't helped.@DeviantEng commented on GitHub (Jul 25, 2019):
In a last ditch effort, I was able to get it working.
I shutdown the stack, tar'd up all 3 data dirs and emptied them out. Redeployed the stack, ran
./bin/setupas well as./bin/rake assets:precompile, restarted the stack and validated it was working (without my data, of course).Then I shut down the stack, emptied my
db-datadir, copied over my data fromdb-data, and restarted the stack. Seems working so far!@vavgustov commented on GitHub (Jul 26, 2019):
ok great! I'll try to recheck this issue on next update
@tschaerni commented on GitHub (Oct 24, 2019):
Thanks a lot. I had the same issue, but I'm using an external database server, so I wasn't sure if that had something to do with it.
Thankfully, deleting the content of the backend _data folder solved the issue.
Cheers!