-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Question: :dev branch container gives permission denied errors on migration script (in /app) even after new install #1002
Comments
A quick and dirty workaround to fix permissions on start:
|
@selim13 Can you make this a PR? I have the same issue |
@agnosticlines @selim13 You can use my docker image |
Yeah sorry a bug got merged into dev with one of the recent PRs a few months ago and I haven't had a chance to bisect and dig it out yet. |
This should be fixed now as I merged @turian's PR with the missing migration. Comment back if you're still having issues on the latest dev release. |
Hi, I found that this problem seems to still exist:
|
I believe this issue should be fixed again, comment back if you're still having trouble and I can re-open it. |
Hi! Looks like trouble is back with migration 0069
|
Ok yeah the issue is it's trying to create a new migration that it shouldn't be creating. Don't run the workarounds posted above (don't worry if you did it should be fine), it's an edge case for some setups that I need to fix in the code directly. |
unfortunately currently my instance is stuck without being able to access my archive anymore, I was using 0.7.2 but at some moment it stopped grabbing titles for all links with just something like "title not found", or similar from logs and also it was really, really slow in most cases, so I tried to update it to latest dev 0.8.2 - now stuck with I should've create a full instance backup before trying to update.. :( |
@Astro1247, I understand it looks scary but don't worry you shouldn't lose data, Django migrations are deterministic and atomic (meaning if they fail during some step it wont leave your db in a corrupted state). In the future you should definitely back up before installing any BETA releases but I'll help fix it for now. I just pushed fixes for the two underlying issues you encountered (missing migration 0069 and created_by_id failure): You should be able to pull the latest docker compose pull
docker compose down
docker compose up |
Just bumping this to send a new notification because I edited my previous comment quite a bit ^ |
Thanks, it managed to recover (some?, it said it loaded 530 links and next row it said it ignored 530 invalid links) data and even it completely mixed all the data (date of saving is new now) at least I'm able to view this data and archivebox itself started. All new starts are now with this warning:
Also no new archiving tasks can be completed, no matter how much different attempts with different settings I've done, all fails into:
So no new data can be saved, it all fails with same error, even that everything is okay, when using vnc everything seems fine too, but, its fails on archiving attempt :) Also, all these actions that I've taken, all this updates etc were to fix failing title extracting, and.. it still fails to extract any page title XD Even with everything latest
|
Hi there,
I've been using ArchiveBox for quite a while, previously I was using the :latest branch, which works fine for most things, except that SingleFile doesn't work because of the missing link to
/usr/bin/chromium-browser
I see there's a fix in the dockerfile, so when I switch to the dev docker release the link is correct however I cannot start the server due to permission errors, this happens regardless of
PUID
,PGID
host permissions (777 for debugging) of the data folder, the issue appears to be for some reason the/app/
folder has the wrong permissionsInitial logs
This happens even if I set up a brand new directory with the :dev branch to create a new database and do setup/init.
If I create the container and spawn a shell to poke around it appears
/app
has permissionsroot:root
which should be fine, but I guess ArchiveBox writes out the migration files to the/app
directory, what's interesting is that this happens even on a totally fresh install.Here are the permissions:
Update:
May not be a permissions issue, the file doesn't seem to exist
Not too sure what causes this, I looked at the migrations subdir and they're all on git anyways, so I'm guessing it's trying to execute a migration that doesn't exist yet? Maybe @pirate pushed a new build expecting a migration there when there isn't one yet?
Update: Yeah it's a permissions issue, giving
archivebox:archivebox
ownership of/app/archivebox/core/migrations
works:The text was updated successfully, but these errors were encountered: