mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #946] Question: Unable to create the django_migrations table (database is locked) - When OUTPUT_DIR to SAMBA share #3608
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#3608
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 @stephenmetzger on GitHub (Mar 16, 2022).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/946
Hello,
Running ArchiveBox in docker (docker compose) am trying to output my archives to a samba share mounted on the archivebox host.
I am configuring the directories, and the docker-compose.yml file, then running the
docker-compose run archivebox init --setupcommand. Once finished, I'm updating the ArchiveBox.conf file to containOUTPUT_DIR = /mnt/archivebox(which is where i have my mounted SAMBA share directory mounted to the container from the host using a bind mount), and running thedocker-compose up -dcommand.In the logs, there is a long pause at
[+] Building main SQL index and running initial migrations..., then a failure to load. Full log:I have exact setup working succesfully working another machine with ArchiveBox running in docker, but cannot seem to get it to work on this machine (Ubuntu Server 21.10).
@stephenmetzger commented on GitHub (Mar 16, 2022):
Not sure why I was getting the issue above, but ended up finding a workaround (probably the 'right' way to do it).
I started from scratch and ran a new
--setupanddocker-compose upwith a typical configuration as outlined in the docs to get the package to get the directories and files set up, then edited my docker-compose.yml file to manually mount everything where I wanted it to live. My volumes section under archivebox now looks like this:Any issues doing it this way?
@pirate commented on GitHub (Mar 16, 2022):
Nope, that's a valid way to do it! But I recommend this instead so you don't have to hardcode those file paths:
@stephenmetzger commented on GitHub (Mar 16, 2022):
Fantastic. Thanks. So, for docker generally, you can specify a subdirectory of a directory to be linked to a different path than the rest of the base-directory? Does the order they are listed matter?
@pirate commented on GitHub (Mar 16, 2022):
Yes, and the order matters. Sub-path overrides for paths within a parent must be listed after the parent.
@pirate commented on GitHub (Apr 12, 2022):
Note I've added a new DB/filesystem troubleshooting area to the wiki that may help people arriving here from Google: https://github.com/ArchiveBox/ArchiveBox/wiki/Upgrading-or-Merging-Archives#database-troubleshooting
Contributions/suggestions welcome there.
@p0n1 commented on GitHub (Oct 26, 2023):
This is working. When the
index.sqlite3created successfully in local, I just moved all files into/mnt/smb/archiveboxand redeployed the container. The ArchiveBox could operate normally. No moredatabase is lockedissues. Not sure why.BTW, I also tried NFS mounting and didn't encounter database locked issue.