[GH-ISSUE #1155] Scheduled jobs added in Docker with `archivebox schedule ...` don't persist when container restarts

kerem commented

2026-03-01 17:57:27 +03:00

Owner

Originally created by @melyux on GitHub (Jun 8, 2023).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1155

Describe the bug

Adding a new schedule on a feed using sudo docker compose run archivebox schedule --every=day --depth=1 https://domain.of/feed says:

[√] Scheduled new ArchiveBox cron job for user: archivebox (1 jobs are active).

but subsequently running sudo docker compose run archivebox schedule --show says:

[X] There are no ArchiveBox cron jobs scheduled for your user (archivebox).

Steps to reproduce

docker compose yaml:

  archivebox:
    container_name: archivebox
    image: archivebox/archivebox:latest
    command: server --quick-init 0.0.0.0:8000
    restart: unless-stopped
    ports:
      - 8000:8000
    environment:
      - ALLOWED_HOSTS=*                   # add any config options you want as env vars
      - MEDIA_MAX_SIZE=5000m
      - PUBLIC_INDEX=False
      - PUBLIC_SNAPSHOTS=False
    volumes:
      - ./data:/data

Schedule something. Then do schedule --show.

Screenshots or log output

ArchiveBox version

0.6.3
ArchiveBox v0.6.3 Cpython Linux Linux-5.10.0-20-amd64-x86_64-with-glibc2.31 x86_64
DEBUG=False IN_DOCKER=True IS_TTY=True TZ=UTC FS_ATOMIC=True FS_REMOTE=True FS_PERMS=644 999:999 SEARCH_BACKEND=ripgrep

[i] Dependency versions:
 √  PYTHON_BINARY         v3.11.3         valid     /usr/local/bin/python3.11                                                   
 √  SQLITE_BINARY         v2.6.0          valid     /usr/local/lib/python3.11/sqlite3/dbapi2.py                                 
 √  DJANGO_BINARY         v3.1.14         valid     /usr/local/lib/python3.11/site-packages/django/__init__.py                  
 √  ARCHIVEBOX_BINARY     v0.6.3          valid     /usr/local/bin/archivebox                                                   

 √  CURL_BINARY           v7.74.0         valid     /usr/bin/curl                                                               
 √  WGET_BINARY           v1.21           valid     /usr/bin/wget                                                               
 √  NODE_BINARY           v18.16.0        valid     /usr/bin/node                                                               
 √  SINGLEFILE_BINARY     v0.3.16         valid     /node/node_modules/single-file/cli/single-file                              
 √  READABILITY_BINARY    v0.0.2          valid     /node/node_modules/readability-extractor/readability-extractor              
 √  MERCURY_BINARY        v1.0.0          valid     /node/node_modules/@postlight/mercury-parser/cli.js                         
 √  GIT_BINARY            v2.30.2         valid     /usr/bin/git                                                                
 √  YOUTUBEDL_BINARY      v2023.03.04     valid     /usr/local/bin/yt-dlp                                                       
 √  CHROME_BINARY         v112.0.5615.138  valid     /usr/bin/chromium                                                           
 √  RIPGREP_BINARY        v12.1.1         valid     /usr/bin/rg                                                                 

[i] Source-code locations:
 √  PACKAGE_DIR           22 files        valid     /app/archivebox                                                             
 √  TEMPLATES_DIR         3 files         valid     /app/archivebox/templates                                                   
 -  CUSTOM_TEMPLATES_DIR  -               disabled                                                                              

[i] Secrets locations:
 -  CHROME_USER_DATA_DIR  -               disabled                                                                              
 -  COOKIES_FILE          -               disabled                                                                              

[i] Data locations:
 √  OUTPUT_DIR            5 files @       valid     /data                                                                       
 √  SOURCES_DIR           0 files         valid     ./sources                                                                   
 √  LOGS_DIR              1 files         valid     ./logs                                                                      
 √  ARCHIVE_DIR           0 files         valid     ./archive                                                                   
 √  CONFIG_FILE           81.0 Bytes      valid     ./ArchiveBox.conf                                                           
 √  SQL_INDEX             204.0 KB        valid     ./index.sqlite3

Originally created by @melyux on GitHub (Jun 8, 2023). Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1155  #### Describe the bug  Adding a new schedule on a feed using `sudo docker compose run archivebox schedule --every=day --depth=1 https://domain.of/feed` says: `[√] Scheduled new ArchiveBox cron job for user: archivebox (1 jobs are active).` but subsequently running `sudo docker compose run archivebox schedule --show` says: `[X] There are no ArchiveBox cron jobs scheduled for your user (archivebox).` #### Steps to reproduce  docker compose yaml: ```yaml archivebox: container_name: archivebox image: archivebox/archivebox:latest command: server --quick-init 0.0.0.0:8000 restart: unless-stopped ports: - 8000:8000 environment: - ALLOWED_HOSTS=* # add any config options you want as env vars - MEDIA_MAX_SIZE=5000m - PUBLIC_INDEX=False - PUBLIC_SNAPSHOTS=False volumes: - ./data:/data ``` Schedule something. Then do `schedule --show`. #### Screenshots or log output  #### ArchiveBox version  ```logs 0.6.3 ArchiveBox v0.6.3 Cpython Linux Linux-5.10.0-20-amd64-x86_64-with-glibc2.31 x86_64 DEBUG=False IN_DOCKER=True IS_TTY=True TZ=UTC FS_ATOMIC=True FS_REMOTE=True FS_PERMS=644 999:999 SEARCH_BACKEND=ripgrep [i] Dependency versions: √ PYTHON_BINARY v3.11.3 valid /usr/local/bin/python3.11 √ SQLITE_BINARY v2.6.0 valid /usr/local/lib/python3.11/sqlite3/dbapi2.py √ DJANGO_BINARY v3.1.14 valid /usr/local/lib/python3.11/site-packages/django/__init__.py √ ARCHIVEBOX_BINARY v0.6.3 valid /usr/local/bin/archivebox √ CURL_BINARY v7.74.0 valid /usr/bin/curl √ WGET_BINARY v1.21 valid /usr/bin/wget √ NODE_BINARY v18.16.0 valid /usr/bin/node √ SINGLEFILE_BINARY v0.3.16 valid /node/node_modules/single-file/cli/single-file √ READABILITY_BINARY v0.0.2 valid /node/node_modules/readability-extractor/readability-extractor √ MERCURY_BINARY v1.0.0 valid /node/node_modules/@postlight/mercury-parser/cli.js √ GIT_BINARY v2.30.2 valid /usr/bin/git √ YOUTUBEDL_BINARY v2023.03.04 valid /usr/local/bin/yt-dlp √ CHROME_BINARY v112.0.5615.138 valid /usr/bin/chromium √ RIPGREP_BINARY v12.1.1 valid /usr/bin/rg [i] Source-code locations: √ PACKAGE_DIR 22 files valid /app/archivebox √ TEMPLATES_DIR 3 files valid /app/archivebox/templates - CUSTOM_TEMPLATES_DIR - disabled [i] Secrets locations: - CHROME_USER_DATA_DIR - disabled - COOKIES_FILE - disabled [i] Data locations: √ OUTPUT_DIR 5 files @ valid /data √ SOURCES_DIR 0 files valid ./sources √ LOGS_DIR 1 files valid ./logs √ ARCHIVE_DIR 0 files valid ./archive √ CONFIG_FILE 81.0 Bytes valid ./ArchiveBox.conf √ SQL_INDEX 204.0 KB valid ./index.sqlite3 ```

kerem

2026-03-01 17:57:27 +03:00

closed this issue
added the
status: wontfix
label

kerem commented

2026-03-01 17:57:28 +03:00

Author

Owner

@pirate commented on GitHub (Jun 11, 2023):

The schedule commands write to your local crontab file, can you check your user's crontab to see if they're in there?

@pirate commented on GitHub (Jun 11, 2023): The schedule commands write to your local crontab file, can you check your user's crontab to see if they're in there?

kerem commented

2026-03-01 17:57:28 +03:00

Author

Owner

@pirate commented on GitHub (Jun 11, 2023):

Wait nvm I saw you're in docker, you need to use the same container to have them persist. Can you exec bash in the container and check everything in /etc/cron.d in the docker container to see if it's in there. Let me know if you need help with the commands to do that.

@pirate commented on GitHub (Jun 11, 2023): Wait nvm I saw you're in docker, you need to use the same container to have them persist. Can you exec bash in the container and check everything in /etc/cron.d in the docker container to see if it's in there. Let me know if you need help with the commands to do that.

kerem commented

2026-03-01 17:57:28 +03:00

Author

Owner

@melyux commented on GitHub (Jun 11, 2023):

The contents of /etc/cron.d inside the container (after running the schedule command) are these:

.placeholder
e2scrub_all

@melyux commented on GitHub (Jun 11, 2023): The contents of /etc/cron.d inside the container (after running the schedule command) are these: .placeholder e2scrub_all

kerem commented

2026-03-01 17:57:28 +03:00

Author

Owner

@pirate commented on GitHub (Jun 13, 2023):

I think it may be more trouble than it's worth trying to use cron within the Docker container, as the container is not designed to persist any state other than the archivebox data folder (which is why your crontab gets wiped out every time the container is re-created).

The recommended approach is the one we have as a commented-out example in the provided docker-compose.yml:

services:
  archivebox:
    image: archivebox/archivebox:dev
    command: server --quick-init 0.0.0.0:8000
    ...
    
  archivebox_daily_pocket:
    image: archivebox/archivebox:dev
    command: schedule --foreground --every=day --depth=1 'https://getpocket.com/users/USERNAME/feed/all'
    volumes:
      - ./data:/data
      
  archivebox_daily_reddit:
    image: archivebox/archivebox:dev
    command: schedule --foreground --every=day --depth=1 'https://old.reddit.com/r/SOMESUBREDDITHERE'
    volumes:
      - ./data:/data
  
  ...

Using this pattern you would add a new yaml service definition block for every scheduled job you need to your docker-compose.yml. The example above shows archiving a pocket user's RSS feed and a subreddit homepage every day, but you can modify it / add more scheduled job blocks as needed. (Comment back here if you have any issues with this recommend pattern and I'll reopen the issue.)

This will be streamlined in the future once we add support for scheduling jobs via the UI: https://github.com/ArchiveBox/ArchiveBox/issues/578 (subscribe here for updates on progress). As part of that feature's implementation, jobs will be persisted in the DB anyway so they wont be wiped out when the container restarts, and this will become a non-issue / less of a UX wart.

@pirate commented on GitHub (Jun 13, 2023): I think it may be more trouble than it's worth trying to use cron within the Docker container, as the container is not designed to persist any state other than the archivebox data folder (which is why your crontab gets wiped out every time the container is re-created). The recommended approach is the one we have as a commented-out example in the provided [`docker-compose.yml`](https://github.com/ArchiveBox/ArchiveBox/blob/dev/docker-compose.yml#L64): ```yaml services: archivebox: image: archivebox/archivebox:dev command: server --quick-init 0.0.0.0:8000 ... archivebox_daily_pocket: image: archivebox/archivebox:dev command: schedule --foreground --every=day --depth=1 'https://getpocket.com/users/USERNAME/feed/all' volumes: - ./data:/data archivebox_daily_reddit: image: archivebox/archivebox:dev command: schedule --foreground --every=day --depth=1 'https://old.reddit.com/r/SOMESUBREDDITHERE' volumes: - ./data:/data ... ``` Using this pattern you would add a new yaml service definition block for every scheduled job you need to your `docker-compose.yml`. The example above shows archiving a pocket user's RSS feed and a subreddit homepage every day, but you can modify it / add more scheduled job blocks as needed. (Comment back here if you have any issues with this recommend pattern and I'll reopen the issue.) This will be streamlined in the future once we add support for scheduling jobs via the UI: https://github.com/ArchiveBox/ArchiveBox/issues/578 (subscribe here for updates on progress). As part of that feature's implementation, jobs will be persisted in the DB anyway so they wont be wiped out when the container restarts, and this will become a non-issue / less of a UX wart.

kerem commented

2026-03-01 17:57:28 +03:00

Author

Owner

@melyux commented on GitHub (Jun 13, 2023):

Isn't it overkill to have a separate container for each feed? I have hundreds I was going to add, would this consume a lot of resources?

I saw in a different issue you had recommended maybe just one container for feeds that would read the added jobs, but I guess that would not work since the cron additions don't seem to be persisted even in the same container without restarting at all.

Looking forward to the streamlined solution! Subscribed.

@melyux commented on GitHub (Jun 13, 2023): Isn't it overkill to have a separate container for each feed? I have hundreds I was going to add, would this consume a lot of resources? I saw in a different issue you had recommended maybe just one container for feeds that would read the added jobs, but I guess that would not work since the cron additions don't seem to be persisted even in the same container without restarting at all. Looking forward to the streamlined solution! Subscribed.

kerem commented

2026-03-01 17:57:28 +03:00

Author

Owner

@pirate commented on GitHub (Jun 13, 2023):

Ah yeah that would be a huge pain to add hundreds of scheduled tasks that way 😢 It wouldn't necessarily consume tons of resources, because the containers don't do anything while they're sleeping and will readily swap to disk in case of RAM shortages, but if you have many jobs running frequently on a small machine I could see it being a problem.

If that was your plan, may I ask what your plan was for storing all that data? The main reason I haven't built out tons of scheduled archiving features is because it tends to rapidly balloon to terabytes of storage, so most people aren't actually able to archive that much.

There definitely is a way to do scheduled jobs with one container, it's just a matter of figuring out where the docker contab file is stored and mounting that path as a volume (maybe check /var/spool/cron/crontabs ?). I'm happy to work with you to figure that out, but I want to make sure it's feasible/desirable for you to actually store that much content first :)

@pirate commented on GitHub (Jun 13, 2023): Ah yeah that would be a huge pain to add hundreds of scheduled tasks that way 😢 It wouldn't necessarily consume tons of resources, because the containers don't do anything while they're sleeping and will readily swap to disk in case of RAM shortages, but if you have many jobs running frequently on a small machine I could see it being a problem. If that was your plan, may I ask what your plan was for storing all that data? The main reason I haven't built out tons of scheduled archiving features is because it tends to rapidly balloon to terabytes of storage, so most people aren't actually able to archive that much. There definitely is a way to do scheduled jobs with one container, it's just a matter of figuring out where the docker contab file is stored and mounting that path as a volume (maybe check `/var/spool/cron/crontabs` ?). I'm happy to work with you to figure that out, but I want to make sure it's feasible/desirable for you to actually store that much content first :)

kerem commented

2026-03-01 17:57:28 +03:00

Author

Owner

@melyux commented on GitHub (Jun 13, 2023):

It was just for tracking updates to blogs, which update only rarely, so disk space wouldn't be a problem even if I had only like 10 GB to spare. Maybe one new article to download every day out of all those hundreds of feeds. For me this would be a fairly primary use case for archivebox (set it and forget it!)

Let's do it! I couldn't get the scheduling to work inside the bash shell of the container because archivebox said it wouldn't run as root. If I mounted the crontab path, is there a way to schedule the feeds without running a separate container?

@melyux commented on GitHub (Jun 13, 2023): It was just for tracking updates to blogs, which update only rarely, so disk space wouldn't be a problem even if I had only like 10 GB to spare. Maybe one new article to download every day out of all those hundreds of feeds. For me this would be a fairly primary use case for archivebox (set it and forget it!) Let's do it! I couldn't get the scheduling to work inside the bash shell of the container because archivebox said it wouldn't run as root. If I mounted the crontab path, is there a way to schedule the feeds without running a separate container?

kerem commented

2026-03-01 17:57:29 +03:00

Author

Owner

@pirate commented on GitHub (Jun 13, 2023):

Figured it out, just mount the crontabs directory as a volume: ./etc/crontabs:/var/spool/cron/crontabs, and then you only need one container running archivebox schedule --foreground to handle running all the scheduled jobs together.

docker-compose.yml:

services:
  archivebox:
    image: archivebox/archivebox:dev
    command: server --quick-init 0.0.0.0:8000
    ...
    volumes:
      - ./data:/data
      - ./etc/crontabs:/var/spool/cron/crontabs

  archivebox_scheduler:
    image: archivebox/archivebox:dev
    command: schedule --foreground
    ...
    volumes:
      - ./data:/data
      - ./etc/crontabs:/var/spool/cron/crontabs

$ docker compose up

# add a scheduled job
$ docker compose run archivebox schedule --every=day 'https://example.com'

# restart the scheduler container to pick up the new scheduled job
$ docker compose restart archivebox_scheduler

# check the scheduler container's log output to make sure it's running all the jobs properly
$ docker compose logs archivebox_scheduler
[i] [2023-06-13 22:52:35] ArchiveBox v0.6.2: archivebox schedule --foreground
    > /data

[*] Running 2 ArchiveBox jobs in foreground task scheduler...
  > add --depth=0 "https://example.com/2"
  > add --depth=0 "https://example.com"

I've updated our provided example docker-compose.yml too https://github.com/ArchiveBox/ArchiveBox/blob/dev/docker-compose.yml

And the equivalent in plain docker without compose:
_{Click to expand...}

# create the folder on the hose to hold the crontab config
$ mkdir -p ./etc/crontabs

# start an archivebox container with the crontab folder mounted as a volume
$ docker run --rm -v $PWD:/data -v $PWD/etc/crontabs:/var/spool/cron/crontabs archivebox/archivebox:dev

[i] [2023-06-13 22:27:46] ArchiveBox v0.6.3: archivebox server --quick-init 0.0.0.0:8000
    > /data
    
...

System check identified no issues (0 silenced).
June 13, 2023 - 22:27:48
Django version 3.1.14, using settings 'core.settings'
Starting development server at http://0.0.0.0:8000/
Quit the server with CONTROL-C.

# in another terminal window, find the docker container's ID and exec a bash shell into it as root
$ docker ps
CONTAINER ID   IMAGE                       COMMAND                  CREATED          STATUS          PORTS      NAMES
3efe15e34b19   archivebox/archivebox:dev   "dumb-init -- /app/b…"   11 seconds ago   Up 10 seconds   8000/tcp   sleepy_cohen

$ docker exec -it --user=root 3efe15e34b19 /bin/bash

root@3efe15e34b19:/data $ whoami
root
root@3efe15e34b19:/data $ su archivebox  # switch to archivebox user to create the scheduled task

archivebox@3efe15e34b19:/data $ archivebox schedule --every=week 'https://example.com'
[√] Scheduled new ArchiveBox cron job for user: archivebox (1 jobs are active).
  > @daily cd /data && /usr/local/bin/archivebox add --depth=0 "https://example.com" >> /data/logs/schedule.log 2>&1 # archivebox_schedule
  ...
  
archivebox@3efe15e34b19:/data $ exit    # switch back to root user just to check that it saved to /var/spool/cron/crontabs

root@3efe15e34b19:/data $ cat /var/spool/cron/crontabs/archivebox
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (/tmp/tmpq2dqk7wj installed on Tue Jun 13 22:28:32 2023)
# (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)

@weekly cd /data && /usr/local/bin/archivebox add --depth=0 "https://example.com" >> /data/logs/schedule.log 2>&1 # archivebox_schedule

Then exit both terminals, stop the container completely, remove it, and restart it from scratch with the volumes mounted.

You should be able to run it with the foreground scheduler in docker and it will pick up the schedule task because it's persisted now.

docker run --rm -v $PWD:/data -v $PWD/etc/crontabs:/var/spool/cron/crontabs archivebox/archivebox:dev schedule --foreground

[i] [2023-06-13 22:34:08] ArchiveBox v0.6.3: archivebox schedule --foreground
    > /data

find: '/.config/chromium/Crash Reports/pending/': No such file or directory
[*] Running 1 ArchiveBox jobs in foreground task scheduler...
  > add --depth=0 "https://example.com"

Let me know if it works!

@pirate commented on GitHub (Jun 13, 2023): Figured it out, just mount the crontabs directory as a volume: `./etc/crontabs:/var/spool/cron/crontabs`, and then you only need one container running `archivebox schedule --foreground` to handle running all the scheduled jobs together. `docker-compose.yml`: ```yaml services: archivebox: image: archivebox/archivebox:dev command: server --quick-init 0.0.0.0:8000 ... volumes: - ./data:/data - ./etc/crontabs:/var/spool/cron/crontabs archivebox_scheduler: image: archivebox/archivebox:dev command: schedule --foreground ... volumes: - ./data:/data - ./etc/crontabs:/var/spool/cron/crontabs ``` ```bash $ docker compose up # add a scheduled job $ docker compose run archivebox schedule --every=day 'https://example.com' # restart the scheduler container to pick up the new scheduled job $ docker compose restart archivebox_scheduler # check the scheduler container's log output to make sure it's running all the jobs properly $ docker compose logs archivebox_scheduler [i] [2023-06-13 22:52:35] ArchiveBox v0.6.2: archivebox schedule --foreground > /data [*] Running 2 ArchiveBox jobs in foreground task scheduler... > add --depth=0 "https://example.com/2" > add --depth=0 "https://example.com" ``` I've updated our provided example `docker-compose.yml` too https://github.com/ArchiveBox/ArchiveBox/blob/dev/docker-compose.yml --- <details> <summary>And the equivalent in plain docker without compose: Click to expand...</summary> ```bash # create the folder on the hose to hold the crontab config $ mkdir -p ./etc/crontabs # start an archivebox container with the crontab folder mounted as a volume $ docker run --rm -v $PWD:/data -v $PWD/etc/crontabs:/var/spool/cron/crontabs archivebox/archivebox:dev [i] [2023-06-13 22:27:46] ArchiveBox v0.6.3: archivebox server --quick-init 0.0.0.0:8000 > /data ... System check identified no issues (0 silenced). June 13, 2023 - 22:27:48 Django version 3.1.14, using settings 'core.settings' Starting development server at http://0.0.0.0:8000/ Quit the server with CONTROL-C. ``` ```bash # in another terminal window, find the docker container's ID and exec a bash shell into it as root $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 3efe15e34b19 archivebox/archivebox:dev "dumb-init -- /app/b…" 11 seconds ago Up 10 seconds 8000/tcp sleepy_cohen $ docker exec -it --user=root 3efe15e34b19 /bin/bash root@3efe15e34b19:/data $ whoami root root@3efe15e34b19:/data $ su archivebox # switch to archivebox user to create the scheduled task archivebox@3efe15e34b19:/data $ archivebox schedule --every=week 'https://example.com' [√] Scheduled new ArchiveBox cron job for user: archivebox (1 jobs are active). > @daily cd /data && /usr/local/bin/archivebox add --depth=0 "https://example.com" >> /data/logs/schedule.log 2>&1 # archivebox_schedule ... archivebox@3efe15e34b19:/data $ exit # switch back to root user just to check that it saved to /var/spool/cron/crontabs root@3efe15e34b19:/data $ cat /var/spool/cron/crontabs/archivebox # DO NOT EDIT THIS FILE - edit the master and reinstall. # (/tmp/tmpq2dqk7wj installed on Tue Jun 13 22:28:32 2023) # (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $) @weekly cd /data && /usr/local/bin/archivebox add --depth=0 "https://example.com" >> /data/logs/schedule.log 2>&1 # archivebox_schedule ``` Then exit both terminals, stop the container completely, remove it, and restart it from scratch with the volumes mounted. You should be able to run it with the foreground scheduler in docker and it will pick up the schedule task because it's persisted now. ```bash docker run --rm -v $PWD:/data -v $PWD/etc/crontabs:/var/spool/cron/crontabs archivebox/archivebox:dev schedule --foreground [i] [2023-06-13 22:34:08] ArchiveBox v0.6.3: archivebox schedule --foreground > /data find: '/.config/chromium/Crash Reports/pending/': No such file or directory [*] Running 1 ArchiveBox jobs in foreground task scheduler... > add --depth=0 "https://example.com" ``` </details> Let me know if it works!

kerem commented

2026-03-01 17:57:29 +03:00

Author

Owner

@melyux commented on GitHub (Jun 14, 2023):

This is great, testing now. Since we're adding a cron job, is the second scheduler container still necessary? Wouldn't the primary archivebox container run the scheduled cron jobs itself?

@melyux commented on GitHub (Jun 14, 2023): This is great, testing now. Since we're adding a cron job, is the second scheduler container still necessary? Wouldn't the primary archivebox container run the scheduled cron jobs itself?

kerem commented

2026-03-01 17:57:29 +03:00

Author

Owner

@pirate commented on GitHub (Jun 14, 2023):

The primary container has the cron package installed but doesn't have any init system / doesn't run cron itself, it only runs the webserver.

@pirate commented on GitHub (Jun 14, 2023): The primary container has the cron package installed but doesn't have any init system / doesn't run cron itself, it only runs the webserver.

kerem commented

2026-03-01 17:57:29 +03:00

Author

Owner

@melyux commented on GitHub (Jun 14, 2023):

Gotcha. Would be very cool if it did run cron ;)

@melyux commented on GitHub (Jun 14, 2023): Gotcha. Would be very cool if it did run cron ;)

Rows
Columns

[GH-ISSUE #1155] Scheduled jobs added in Docker with archivebox schedule ... don't persist when container restarts #2227

Describe the bug

Steps to reproduce

Screenshots or log output

ArchiveBox version

[GH-ISSUE #1155] Scheduled jobs added in Docker with `archivebox schedule ...` don't persist when container restarts #2227