mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #1552] Bug: v0.7.1 on alpine linux OSError: crontab: can't open 'archivebox': No such file or directory #3943
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#3943
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 @jvoisin on GitHub (Oct 19, 2024).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1552
Describe the bug
archivebox schedule --showresults in a stacktrace.Steps to reproduce
Screenshots or log output
ArchiveBox version
ArchiveBox was installed via pip, on Alpine Linux edge, x64.
@pirate commented on GitHub (Oct 19, 2024):
It seems you created an archivebox user to run it, but the user has no home folder / crontab folder, perhaps a quirk of alpine?
Can you try creating
/etc/crontabs/archiveboxmanually?@jvoisin commented on GitHub (Oct 19, 2024):
Running
crontab -eas thearchiveboxuser fixed the issue, so it indeed seems that there was something wrong with the file creation.@pirate commented on GitHub (Oct 21, 2024):
I'm closing this as the v0.8.x and above scheduler doesn't use the system crontab at all, so this issue will go away anyway in future releases.