[GH-ISSUE #1689] Bug: Dependencies like Chrome are not detected in v0.7.3 Docker image despite being installed

kerem commented

2026-03-01 14:47:52 +03:00

Owner

Originally created by @Guanchishan on GitHub (Jul 19, 2025).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1689

Originally assigned to: @pirate on GitHub.

Provide a screenshot and describe the bug

After upgrading the Docker image from v0.6.2 to v0.7.3, I encountered and fixed several database integrity errors. However, archivebox status still reports 4 missing dependencies (CHROME_BINARY, SINGLEFILE_BINARY, etc.), showing them as "unable to detect version". This happens even after manually installing these dependencies inside the container as the root user. The system seems to have the dependencies, but ArchiveBox cannot detect them.

I have tried many steps to fix this, including:

Entering the container as root.
Running apt-get update and then playwright install-deps to install all system libraries. This step completed successfully.
Running playwright install to install browser binaries. This also completed successfully.
Running chown -R archivebox:archivebox /node to fix potential npm permission issues.
Despite all these steps, when running archivebox status as the archivebox user, the dependencies are still reported as missing.

Steps to reproduce

-   Start with a data directory from a working v0.6.2 installation.
    
-   Upgrade the Docker image to `archivebox/archivebox:latest` (which is v0.7.3).
    
-   Start the container. It will enter a crash loop due to database `IntegrityError`.
    
-   Fix the database integrity issues for `core_archiveresult` and `core_snapshot_tags` tables.
    
-   Start the container successfully.
    
-   Exec into the container: `docker exec -it <container_name> /bin/bash`.
    
-   Run dependency checks: `su archivebox` then `archivebox status`.
    
-   Observe the "Missing 4 recommended dependencies" warning.

Logs or errors

[i] [2025-07-19 12:28:38] ArchiveBox v0.7.3: archivebox update --overwrite --extract readability
    > /data

[!] Warning: Missing 4 recommended dependencies
    ! SINGLEFILE_BINARY: /node/node_modules/.bin/single-file (unable to detect version)
      Hint: To install all packages automatically run: archivebox setup
            or to disable it and silence this warning: archivebox config --set SAVE_SINGLEFILE=False
            
    ! READABILITY_BINARY: /node/node_modules/.bin/readability-extractor (unable to detect version)
      Hint: To install all packages automatically run: archivebox setup
            or to disable it and silence this warning: archivebox config --set SAVE_READABILITY=False
            
    ! MERCURY_BINARY: /node/node_modules/.bin/mercury-parser (unable to detect version)
      Hint: To install all packages automatically run: archivebox setup
            or to disable it and silence this warning: archivebox config --set SAVE_MERCURY=False
            
    ! CHROME_BINARY: chromium (unable to detect version)
      Hint: To install all packages automatically run: archivebox setup
            or to disable it and silence this warning: archivebox config --set SAVE_CHROME=False

ArchiveBox Version

[√] Set up ArchiveBox and its dependencies successfully.
0.7.3
ArchiveBox v0.7.3 COMMIT_HASH=069aabc BUILD_TIME=2024-12-15 09:54:03 1734256443
IN_DOCKER=True IN_QEMU=False ARCH=x86_64 OS=Linux PLATFORM=Linux-5.10.60-qnap-x86_64-with-glibc2.36 PYTHON=Cpython
FS_ATOMIC=True FS_REMOTE=True FS_USER=999:999 FS_PERMS=644
DEBUG=False IS_TTY=True TZ=UTC SEARCH_BACKEND=ripgrep LDAP=False

[i] Dependency versions:
 √  PYTHON_BINARY         v3.11.11        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.7.3          valid     /usr/local/bin/archivebox                                                   

 √  CURL_BINARY           v8.10.1         valid     /usr/bin/curl                                                               
 √  WGET_BINARY           v1.21.3         valid     /usr/bin/wget                                                               
 √  NODE_BINARY           v20.18.1        valid     /usr/bin/node                                                               
 X  SINGLEFILE_BINARY     ?               invalid   /node/node_modules/.bin/single-file                                         
 X  READABILITY_BINARY    ?               invalid   /node/node_modules/.bin/readability-extractor                               
 X  MERCURY_BINARY        ?               invalid   /node/node_modules/.bin/mercury-parser                                      
 √  GIT_BINARY            v2.39.5         valid     /usr/bin/git                                                                
 √  YOUTUBEDL_BINARY      v2024.12.13     valid     /usr/local/bin/yt-dlp                                                       
 X  CHROME_BINARY         ?               invalid   chromium                                                                    
 √  RIPGREP_BINARY        v13.0.0         valid     /usr/bin/rg                                                                 

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

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

[i] Data locations:
 √  OUTPUT_DIR            9 files @       valid     /data                                                                       
 √  SOURCES_DIR           117 files       valid     ./sources                                                                   
 √  LOGS_DIR              1 files         valid     ./logs                                                                      
 √  ARCHIVE_DIR           2005 files      valid     ./archive                                                                   
 √  CONFIG_FILE           162.0 Bytes     valid     ./ArchiveBox.conf                                                           
 √  SQL_INDEX             33.9 MB         valid     ./index.sqlite3                                                             

[!] Warning: Missing 4 recommended dependencies
    ! SINGLEFILE_BINARY: /node/node_modules/.bin/single-file (unable to detect version)
      Hint: To install all packages automatically run: archivebox setup
            or to disable it and silence this warning: archivebox config --set SAVE_SINGLEFILE=False
            
    ! READABILITY_BINARY: /node/node_modules/.bin/readability-extractor (unable to detect version)
      Hint: To install all packages automatically run: archivebox setup
            or to disable it and silence this warning: archivebox config --set SAVE_READABILITY=False
            
    ! MERCURY_BINARY: /node/node_modules/.bin/mercury-parser (unable to detect version)
      Hint: To install all packages automatically run: archivebox setup
            or to disable it and silence this warning: archivebox config --set SAVE_MERCURY=False
            
    ! CHROME_BINARY: chromium (unable to detect version)
      Hint: To install all packages automatically run: archivebox setup
            or to disable it and silence this warning: archivebox config --set SAVE_CHROME=False

How did you install the version of ArchiveBox you are using?

Docker (or Podman/LXC/K8s/TrueNAS/Proxmox/etc)

What operating system are you running on?

Linux (Ubuntu/Debian/Arch/Alpine/etc.)

What type of drive are you using to store your ArchiveBox data?

some of data/ is on a local SSD or NVMe drive
some of data/ is on a spinning hard drive or external USB drive
some of data/ is on a network mount (e.g. NFS/SMB/Ceph/GlusterFS/etc.)
some of data/ is on a FUSE mount (e.g. SSHFS/RClone/S3/B2/Google Drive/Dropbox/etc.)

Docker Environment

Variable	Value
`APP_VENV`	`/app/.venv`
`APT_KEY_DONT_WARN_ON_DANGEROUS_USAGE`	`1`
`ARCHIVEBOX_USER`	`archivebox`
`CHROME_BINARY`	`chromium`
`CHROME_SANDBOX`	`False`
`CODE_DIR`	`/app`
`DATA_DIR`	`/data`
`DEBIAN_FRONTEND`	`noninteractive`
`DEFAULT_PGID`	`911`
`DEFAULT_PUID`	`911`
`GLOBAL_VENV`	`/venv`
`GPG_KEY`	`E3FF2839C048B25C084DEBE9B26995E310250568`
`IN_DOCKER`	`True`
`LANG`	`C.UTF-8`
`LANGUAGE`	`en_US:en`
`LC_ALL`	`C.UTF-8`
`MERCURY_BINARY`	`/node/node_modules/.bin/mercury-parser`
`NODE_DIR`	`/node`
`NODE_MODULES`	`/app/node_modules`
`NODE_VERSION`	`20`
`PATH`	`/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/node/node_modules/.bin:/venv/bin`
`PIP_DISABLE_PIP_VERSION_CHECK`	`1`
`PLAYWRIGHT_BROWSERS_PATH`	`/browsers`
`PYTHONIOENCODING`	`UTF-8`
`PYTHONUNBUFFERED`	`1`
`PYTHON_GET_PIP_SHA256`	`96461deced5c2a487ddc65207ec5a9cffeca0d34e7af7ea1afc470ff0d746207`
`PYTHON_GET_PIP_URL`	`https://github.com/pypa/get-pip/raw/0d8570dc44796f4369b652222cf176b3db6ac70e/public/get-pip.py`
`PYTHON_PIP_VERSION`	`23.0.1`
`PYTHON_SETUPTOOLS_VERSION`	`58.1.0`
`PYTHON_SHA256`	`2a9920c7a0cd236de33644ed980a13cbbc21058bfdc528febb6081575ed73be3`
`PYTHON_VERSION`	`3.9.17`
`READABILITY_BINARY`	`/node/node_modules/.bin/readability-extractor`
`SINGLEFILE_BINARY`	`/node/node_modules/.bin/single-file`
`TZ`	`UTC`
`USE_MERCURY`	`True`
`USE_READABILITY`	`True`
`USE_SINGLEFILE`	`True`
`VENV_PATH`	`/venv`
`npm_config_loglevel`	`error`

ArchiveBox Configuration

Originally created by @Guanchishan on GitHub (Jul 19, 2025). Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1689 Originally assigned to: @pirate on GitHub. ### Provide a screenshot and describe the bug After upgrading the Docker image from v0.6.2 to v0.7.3, I encountered and fixed several database integrity errors. However, `archivebox status` still reports 4 missing dependencies (CHROME_BINARY, SINGLEFILE_BINARY, etc.), showing them as "unable to detect version". This happens even after manually installing these dependencies inside the container as the root user. The system seems to have the dependencies, but ArchiveBox cannot detect them. I have tried many steps to fix this, including: 1. Entering the container as `root`. 2. Running `apt-get update` and then `playwright install-deps` to install all system libraries. This step completed successfully. 3. Running `playwright install` to install browser binaries. This also completed successfully. 4. Running `chown -R archivebox:archivebox /node` to fix potential npm permission issues. 5. Despite all these steps, when running `archivebox status` as the `archivebox` user, the dependencies are still reported as missing. ### Steps to reproduce ```markdown - Start with a data directory from a working v0.6.2 installation. - Upgrade the Docker image to `archivebox/archivebox:latest` (which is v0.7.3). - Start the container. It will enter a crash loop due to database `IntegrityError`. - Fix the database integrity issues for `core_archiveresult` and `core_snapshot_tags` tables. - Start the container successfully. - Exec into the container: `docker exec -it <container_name> /bin/bash`. - Run dependency checks: `su archivebox` then `archivebox status`. - Observe the "Missing 4 recommended dependencies" warning. ``` ### Logs or errors ```shell [i] [2025-07-19 12:28:38] ArchiveBox v0.7.3: archivebox update --overwrite --extract readability > /data [!] Warning: Missing 4 recommended dependencies ! SINGLEFILE_BINARY: /node/node_modules/.bin/single-file (unable to detect version) Hint: To install all packages automatically run: archivebox setup or to disable it and silence this warning: archivebox config --set SAVE_SINGLEFILE=False ! READABILITY_BINARY: /node/node_modules/.bin/readability-extractor (unable to detect version) Hint: To install all packages automatically run: archivebox setup or to disable it and silence this warning: archivebox config --set SAVE_READABILITY=False ! MERCURY_BINARY: /node/node_modules/.bin/mercury-parser (unable to detect version) Hint: To install all packages automatically run: archivebox setup or to disable it and silence this warning: archivebox config --set SAVE_MERCURY=False ! CHROME_BINARY: chromium (unable to detect version) Hint: To install all packages automatically run: archivebox setup or to disable it and silence this warning: archivebox config --set SAVE_CHROME=False ``` ### ArchiveBox Version ```shell [√] Set up ArchiveBox and its dependencies successfully. 0.7.3 ArchiveBox v0.7.3 COMMIT_HASH=069aabc BUILD_TIME=2024-12-15 09:54:03 1734256443 IN_DOCKER=True IN_QEMU=False ARCH=x86_64 OS=Linux PLATFORM=Linux-5.10.60-qnap-x86_64-with-glibc2.36 PYTHON=Cpython FS_ATOMIC=True FS_REMOTE=True FS_USER=999:999 FS_PERMS=644 DEBUG=False IS_TTY=True TZ=UTC SEARCH_BACKEND=ripgrep LDAP=False [i] Dependency versions: √ PYTHON_BINARY v3.11.11 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.7.3 valid /usr/local/bin/archivebox √ CURL_BINARY v8.10.1 valid /usr/bin/curl √ WGET_BINARY v1.21.3 valid /usr/bin/wget √ NODE_BINARY v20.18.1 valid /usr/bin/node X SINGLEFILE_BINARY ? invalid /node/node_modules/.bin/single-file X READABILITY_BINARY ? invalid /node/node_modules/.bin/readability-extractor X MERCURY_BINARY ? invalid /node/node_modules/.bin/mercury-parser √ GIT_BINARY v2.39.5 valid /usr/bin/git √ YOUTUBEDL_BINARY v2024.12.13 valid /usr/local/bin/yt-dlp X CHROME_BINARY ? invalid chromium √ RIPGREP_BINARY v13.0.0 valid /usr/bin/rg [i] Source-code locations: √ PACKAGE_DIR 24 files valid /app/archivebox √ TEMPLATES_DIR 3 files valid /app/archivebox/templates - CUSTOM_TEMPLATES_DIR - disabled None [i] Secrets locations: - CHROME_USER_DATA_DIR - disabled None - COOKIES_FILE - disabled None [i] Data locations: √ OUTPUT_DIR 9 files @ valid /data √ SOURCES_DIR 117 files valid ./sources √ LOGS_DIR 1 files valid ./logs √ ARCHIVE_DIR 2005 files valid ./archive √ CONFIG_FILE 162.0 Bytes valid ./ArchiveBox.conf √ SQL_INDEX 33.9 MB valid ./index.sqlite3 [!] Warning: Missing 4 recommended dependencies ! SINGLEFILE_BINARY: /node/node_modules/.bin/single-file (unable to detect version) Hint: To install all packages automatically run: archivebox setup or to disable it and silence this warning: archivebox config --set SAVE_SINGLEFILE=False ! READABILITY_BINARY: /node/node_modules/.bin/readability-extractor (unable to detect version) Hint: To install all packages automatically run: archivebox setup or to disable it and silence this warning: archivebox config --set SAVE_READABILITY=False ! MERCURY_BINARY: /node/node_modules/.bin/mercury-parser (unable to detect version) Hint: To install all packages automatically run: archivebox setup or to disable it and silence this warning: archivebox config --set SAVE_MERCURY=False ! CHROME_BINARY: chromium (unable to detect version) Hint: To install all packages automatically run: archivebox setup or to disable it and silence this warning: archivebox config --set SAVE_CHROME=False ``` ### How did you install the version of ArchiveBox you are using? Docker (or Podman/LXC/K8s/TrueNAS/Proxmox/etc) ### What operating system are you running on? Linux (Ubuntu/Debian/Arch/Alpine/etc.) ### What type of drive are you using to store your ArchiveBox data? - [x] some of `data/` is on a local SSD or NVMe drive - [ ] some of `data/` is on a spinning hard drive or external USB drive - [ ] some of `data/` is on a network mount (e.g. NFS/SMB/Ceph/GlusterFS/etc.) - [ ] some of `data/` is on a FUSE mount (e.g. SSHFS/RClone/S3/B2/Google Drive/Dropbox/etc.) ### Docker Environment | Variable | Value | | --- | --- | | `APP_VENV` | `/app/.venv` | | `APT_KEY_DONT_WARN_ON_DANGEROUS_USAGE` | `1` | | `ARCHIVEBOX_USER` | `archivebox` | | `CHROME_BINARY` | `chromium` | | `CHROME_SANDBOX` | `False` | | `CODE_DIR` | `/app` | | `DATA_DIR` | `/data` | | `DEBIAN_FRONTEND` | `noninteractive` | | `DEFAULT_PGID` | `911` | | `DEFAULT_PUID` | `911` | | `GLOBAL_VENV` | `/venv` | | `GPG_KEY` | `E3FF2839C048B25C084DEBE9B26995E310250568` | | `IN_DOCKER` | `True` | | `LANG` | `C.UTF-8` | | `LANGUAGE` | `en_US:en` | | `LC_ALL` | `C.UTF-8` | | `MERCURY_BINARY` | `/node/node_modules/.bin/mercury-parser` | | `NODE_DIR` | `/node` | | `NODE_MODULES` | `/app/node_modules` | | `NODE_VERSION` | `20` | | `PATH` | `/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/node/node_modules/.bin:/venv/bin` | | `PIP_DISABLE_PIP_VERSION_CHECK` | `1` | | `PLAYWRIGHT_BROWSERS_PATH` | `/browsers` | | `PYTHONIOENCODING` | `UTF-8` | | `PYTHONUNBUFFERED` | `1` | | `PYTHON_GET_PIP_SHA256` | `96461deced5c2a487ddc65207ec5a9cffeca0d34e7af7ea1afc470ff0d746207` | | `PYTHON_GET_PIP_URL` | `https://github.com/pypa/get-pip/raw/0d8570dc44796f4369b652222cf176b3db6ac70e/public/get-pip.py` | | `PYTHON_PIP_VERSION` | `23.0.1` | | `PYTHON_SETUPTOOLS_VERSION` | `58.1.0` | | `PYTHON_SHA256` | `2a9920c7a0cd236de33644ed980a13cbbc21058bfdc528febb6081575ed73be3` | | `PYTHON_VERSION` | `3.9.17` | | `READABILITY_BINARY` | `/node/node_modules/.bin/readability-extractor` | | `SINGLEFILE_BINARY` | `/node/node_modules/.bin/single-file` | | `TZ` | `UTC` | | `USE_MERCURY` | `True` | | `USE_READABILITY` | `True` | | `USE_SINGLEFILE` | `True` | | `VENV_PATH` | `/venv` | | `npm_config_loglevel` | `error` | ### ArchiveBox Configuration ```shell ```

kerem closed this issue

2026-03-01 14:47:53 +03:00

kerem commented

2026-03-01 14:47:53 +03:00

Author

Owner

@pirate commented on GitHub (Jul 21, 2025):

hmm those binaries ship inside the docker container already, they should require no manual installation: https://github.com/ArchiveBox/ArchiveBox/blob/v0.7.3/Dockerfile#L210

You can confirm with: docker run -it archivebox/archivebox:latest version

Are you sure you havent attempted to re-install them inside the container or otherwise changed the container's filesystem?

Also check your ArchiveBox.conf to make sure you dont have custom paths set for those binaries. We don't use /node anymore anywhere. You can delete any NODE_DIR config you have or any value that starts with /node from your config.

@pirate commented on GitHub (Jul 21, 2025): hmm those binaries ship inside the docker container already, they should require no manual installation: https://github.com/ArchiveBox/ArchiveBox/blob/v0.7.3/Dockerfile#L210 You can confirm with: `docker run -it archivebox/archivebox:latest version` <img width="1105" height="681" alt="Image" src="https://github.com/user-attachments/assets/06cf0070-94fc-401e-a904-377594703201" /> <img width="1171" height="361" alt="Image" src="https://github.com/user-attachments/assets/47655b20-0476-4fc4-865d-5dc21e42cc17" /> Are you sure you havent attempted to re-install them inside the container or otherwise changed the container's filesystem? Also check your `ArchiveBox.conf` to make sure you dont have custom paths set for those binaries. We don't use `/node` anymore anywhere. You can delete any `NODE_DIR` config you have or any value that starts with `/node` from your config.

kerem commented

2026-03-01 14:47:53 +03:00

Author

Owner

@Guanchishan commented on GitHub (Jul 23, 2025):

Hi, thanks for the suggestion.

I've now corrected my ArchiveBox.conf file. As you suspected, I had a custom CHROME_BINARY path set. I have removed that line from my configuration.

After updating the config, I completely reinstalled the container to ensure a clean state.

However, I'm now facing a new issue. When I run archivebox setup, I encounter a permission error. The error message specifically refers to the browser folder. I have already checked the permissions on the host machine, and they appear to be correct. This leads me to believe the problem originates from within the container itself, not from the host's filesystem.

Could you provide any further guidance on how to resolve this permission issue inside the container?

Thanks for your help.

@Guanchishan commented on GitHub (Jul 23, 2025): Hi, thanks for the suggestion. I've now corrected my `ArchiveBox.conf` file. As you suspected, I had a custom `CHROME_BINARY` path set. I have removed that line from my configuration. After updating the config, I completely reinstalled the container to ensure a clean state. However, I'm now facing a new issue. When I run `archivebox setup`, I encounter a permission error. The error message specifically refers to the `browser` folder. I have already checked the permissions on the host machine, and they appear to be correct. This leads me to believe the problem originates from within the container itself, not from the host's filesystem. Could you provide any further guidance on how to resolve this permission issue inside the container? Thanks for your help.

kerem commented

2026-03-01 14:47:53 +03:00

Author

Owner

@pirate commented on GitHub (Jul 23, 2025):

No need to run archivebox setup in docker as the container already ships with all the dependencies preinstalled. You only need archivebox init.

@pirate commented on GitHub (Jul 23, 2025): No need to run `archivebox setup` in docker as the container already ships with all the dependencies preinstalled. You only need `archivebox init`.

kerem commented

2026-03-01 14:47:53 +03:00

Author

Owner

@Guanchishan commented on GitHub (Jul 23, 2025):

Hi @pirate, thank you for your continued support and suggestions.

Following your advice, I have taken the following steps:

Re-initialized the Collection: With the clean container and corrected configuration, I ran archivebox init on my existing data volume, which completed successfully.
Attempted to Update: I then tried to archive some links by running archivebox update.

Unfortunately, the original issue persists. Even with a clean container and no custom paths in ArchiveBox.conf, the update process still fails with the same FileNotFoundError. The error messages indicate that ArchiveBox is still attempting to locate binaries in the old /node/... path, for example:

Extractor failed:
  FileNotFoundError [Errno 2] No such file or directory: '/node/node_modules/.bin/readability-extractor'

This is puzzling, as I believed that removing the custom paths from the config and using a fresh container would resolve this. It seems that the old configuration is still being referenced from somewhere.

I have avoided running archivebox setup as you advised. Could this old path information be cached somewhere else, perhaps within the index.sqlite3 database itself? Any guidance on where to look next would be greatly appreciated.

@Guanchishan commented on GitHub (Jul 23, 2025): Hi @pirate, thank you for your continued support and suggestions. Following your advice, I have taken the following steps: 1. Re-initialized the Collection: With the clean container and corrected configuration, I ran `archivebox init` on my existing data volume, which completed successfully. 2. Attempted to Update: I then tried to archive some links by running `archivebox update`. Unfortunately, the original issue persists. Even with a clean container and no custom paths in `ArchiveBox.conf`, the update process still fails with the same `FileNotFoundError`. The error messages indicate that ArchiveBox is still attempting to locate binaries in the old `/node/...` path, for example: ``` Extractor failed: FileNotFoundError [Errno 2] No such file or directory: '/node/node_modules/.bin/readability-extractor' ``` This is puzzling, as I believed that removing the custom paths from the config and using a fresh container would resolve this. It seems that the old configuration is still being referenced from somewhere. I have avoided running `archivebox setup` as you advised. Could this old path information be cached somewhere else, perhaps within the `index.sqlite3` database itself? Any guidance on where to look next would be greatly appreciated.

kerem commented

2026-03-01 14:47:53 +03:00

Author

Owner

@pirate commented on GitHub (Jul 31, 2025):

can you run docker run -it -v $PWD:/data archivebox/archivebox:latest config and docker run -it -v $PWD:/data archivebox/archivebox:latest version again and share the output

@pirate commented on GitHub (Jul 31, 2025): can you run `docker run -it -v $PWD:/data archivebox/archivebox:latest config` and `docker run -it -v $PWD:/data archivebox/archivebox:latest version` again and share the output

kerem commented

2026-03-01 14:47:54 +03:00

Author

Owner

@Guanchishan commented on GitHub (Aug 1, 2025):

docker run -it -v $PWD:/data archivebox/archivebox:latest config:

[!] Warning: Docker data volume is completely out of space! (84% used on /data)
    you need to free up at least 100Mb on the drive holding your data directory
    $ ncdu -x data

Filesystem      Size  Used Avail Use% Mounted on
none            400M  335M   66M  84% /data
[i] [2025-08-01 11:04:36] ArchiveBox v0.7.3: archivebox config
    > /data

[X] No archivebox index found in the current directory.
    /data

    Hint: Are you running archivebox in the right folder?
        cd path/to/your/archive/folder
        archivebox [command]

    Hint: To create a new archive collection or import existing data in this folder, run:
        archivebox init

docker run -it -v $PWD:/data archivebox/archivebox:latest version:

[!] Warning: Docker data volume is completely out of space! (84% used on /data)
    you need to free up at least 100Mb on the drive holding your data directory
    $ ncdu -x data

Filesystem      Size  Used Avail Use% Mounted on
none            400M  335M   65M  84% /data
0.7.3
ArchiveBox v0.7.3 COMMIT_HASH=069aabc BUILD_TIME=2024-12-15 09:54:03 1734256443
IN_DOCKER=True IN_QEMU=False ARCH=x86_64 OS=Linux PLATFORM=Linux-5.10.60-qnap-x86_64-with-glibc2.36 PYTHON=Cpython
FS_ATOMIC=True FS_REMOTE=True FS_USER=911:911 FS_PERMS=644
DEBUG=False IS_TTY=True TZ=UTC SEARCH_BACKEND=ripgrep LDAP=False

[i] Dependency versions:
 √  PYTHON_BINARY         v3.11.11        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.7.3          valid     /usr/local/bin/archivebox                                           

 √  CURL_BINARY           v8.10.1         valid     /usr/bin/curl                                                       
 √  WGET_BINARY           v1.21.3         valid     /usr/bin/wget                                                       
 √  NODE_BINARY           v20.18.1        valid     /usr/bin/node                                                       
 √  SINGLEFILE_BINARY     v1.1.54         valid     /app/node_modules/single-file-cli/single-file                       
 √  READABILITY_BINARY    v0.0.11         valid     /app/node_modules/readability-extractor/readability-extractor       
 √  MERCURY_BINARY        v1.0.0          valid     /app/node_modules/@postlight/parser/cli.js                          
 √  GIT_BINARY            v2.39.5         valid     /usr/bin/git                                                        
 √  YOUTUBEDL_BINARY      v2024.12.13     valid     /usr/local/bin/yt-dlp                                               
 √  CHROME_BINARY         v131.0.6778.33  valid     /usr/bin/chromium-browser                                           
 √  RIPGREP_BINARY        v13.0.0         valid     /usr/bin/rg                                                         

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

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


[i] Data locations: (not in a data directory)

P.s.: I am confused as to why it would have an error related to /data like this:

[X] No archivebox index found in the current directory.
    /data

Because my ArchiveBox site is actually accessible, I also tried running archivebox init, and the result was:

$ archivebox init
[i] [2025-08-01 11:09:18] ArchiveBox v0.7.3: archivebox init
    > /data

[^] Verifying and updating existing ArchiveBox collection to v0.7.3...
----------------------------------------------------------------------

[*] Verifying archive folder structure...
    + ./archive, ./sources, ./logs...
    + ./ArchiveBox.conf...

[*] Verifying main SQL index and running any migrations needed...
    Operations to perform:
      Apply all migrations: admin, auth, contenttypes, core, sessions
    Running migrations:
    No migrations to apply.

    √ ./index.sqlite3

[*] Checking links from indexes and archive folders (safe to Ctrl+C)...
    √ Loaded 2093 links from existing main index.
    ! Skipped adding 1 invalid link data directories.
        X (Link omitted by me)

    Hint: For more information about the link data directories that were skipped, run:
        archivebox status
        archivebox list --status=invalid

[*] [2025-08-01 12:11:19] Writing 0 links to main index...
    √ ./index.sqlite3

----------------------------------------------------------------------
[√] Done. Verified and updated the existing ArchiveBox collection.

And then, I ran docker run -it -v $PWD:/data archivebox/archivebox:latest config, the returned content is still the same:

[~] # docker run -it -v $PWD:/data archivebox/archivebox:latest config

[!] Warning: Docker data volume is completely out of space! (84% used on /data)
    you need to free up at least 100Mb on the drive holding your data directory
    $ ncdu -x data

Filesystem      Size  Used Avail Use% Mounted on
none            400M  336M   65M  84% /data
[i] [2025-08-01 12:49:27] ArchiveBox v0.7.3: archivebox config
    > /data

[X] No archivebox index found in the current directory.
    /data

    Hint: Are you running archivebox in the right folder?
        cd path/to/your/archive/folder
        archivebox [command]

    Hint: To create a new archive collection or import existing data in this folder, run:
        archivebox init

@Guanchishan commented on GitHub (Aug 1, 2025): `docker run -it -v $PWD:/data archivebox/archivebox:latest config`: ``` [!] Warning: Docker data volume is completely out of space! (84% used on /data) you need to free up at least 100Mb on the drive holding your data directory $ ncdu -x data Filesystem Size Used Avail Use% Mounted on none 400M 335M 66M 84% /data [i] [2025-08-01 11:04:36] ArchiveBox v0.7.3: archivebox config > /data [X] No archivebox index found in the current directory. /data Hint: Are you running archivebox in the right folder? cd path/to/your/archive/folder archivebox [command] Hint: To create a new archive collection or import existing data in this folder, run: archivebox init ``` `docker run -it -v $PWD:/data archivebox/archivebox:latest version`: ``` [!] Warning: Docker data volume is completely out of space! (84% used on /data) you need to free up at least 100Mb on the drive holding your data directory $ ncdu -x data Filesystem Size Used Avail Use% Mounted on none 400M 335M 65M 84% /data 0.7.3 ArchiveBox v0.7.3 COMMIT_HASH=069aabc BUILD_TIME=2024-12-15 09:54:03 1734256443 IN_DOCKER=True IN_QEMU=False ARCH=x86_64 OS=Linux PLATFORM=Linux-5.10.60-qnap-x86_64-with-glibc2.36 PYTHON=Cpython FS_ATOMIC=True FS_REMOTE=True FS_USER=911:911 FS_PERMS=644 DEBUG=False IS_TTY=True TZ=UTC SEARCH_BACKEND=ripgrep LDAP=False [i] Dependency versions: √ PYTHON_BINARY v3.11.11 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.7.3 valid /usr/local/bin/archivebox √ CURL_BINARY v8.10.1 valid /usr/bin/curl √ WGET_BINARY v1.21.3 valid /usr/bin/wget √ NODE_BINARY v20.18.1 valid /usr/bin/node √ SINGLEFILE_BINARY v1.1.54 valid /app/node_modules/single-file-cli/single-file √ READABILITY_BINARY v0.0.11 valid /app/node_modules/readability-extractor/readability-extractor √ MERCURY_BINARY v1.0.0 valid /app/node_modules/@postlight/parser/cli.js √ GIT_BINARY v2.39.5 valid /usr/bin/git √ YOUTUBEDL_BINARY v2024.12.13 valid /usr/local/bin/yt-dlp √ CHROME_BINARY v131.0.6778.33 valid /usr/bin/chromium-browser √ RIPGREP_BINARY v13.0.0 valid /usr/bin/rg [i] Source-code locations: √ PACKAGE_DIR 23 files valid /app/archivebox √ TEMPLATES_DIR 3 files valid /app/archivebox/templates - CUSTOM_TEMPLATES_DIR - disabled None [i] Secrets locations: - CHROME_USER_DATA_DIR - disabled None - COOKIES_FILE - disabled None [i] Data locations: (not in a data directory) ``` P.s.: I am confused as to why it would have an error related to `/data` like this: ``` [X] No archivebox index found in the current directory. /data ``` Because my ArchiveBox site is actually accessible, I also tried running `archivebox init`, and the result was: ``` $ archivebox init [i] [2025-08-01 11:09:18] ArchiveBox v0.7.3: archivebox init > /data [^] Verifying and updating existing ArchiveBox collection to v0.7.3... ---------------------------------------------------------------------- [*] Verifying archive folder structure... + ./archive, ./sources, ./logs... + ./ArchiveBox.conf... [*] Verifying main SQL index and running any migrations needed... Operations to perform: Apply all migrations: admin, auth, contenttypes, core, sessions Running migrations: No migrations to apply. √ ./index.sqlite3 [*] Checking links from indexes and archive folders (safe to Ctrl+C)... √ Loaded 2093 links from existing main index. ! Skipped adding 1 invalid link data directories. X (Link omitted by me) Hint: For more information about the link data directories that were skipped, run: archivebox status archivebox list --status=invalid [*] [2025-08-01 12:11:19] Writing 0 links to main index... √ ./index.sqlite3 ---------------------------------------------------------------------- [√] Done. Verified and updated the existing ArchiveBox collection. ``` And then, I ran `docker run -it -v $PWD:/data archivebox/archivebox:latest config`, the returned content is still the same: ``` [~] # docker run -it -v $PWD:/data archivebox/archivebox:latest config [!] Warning: Docker data volume is completely out of space! (84% used on /data) you need to free up at least 100Mb on the drive holding your data directory $ ncdu -x data Filesystem Size Used Avail Use% Mounted on none 400M 336M 65M 84% /data [i] [2025-08-01 12:49:27] ArchiveBox v0.7.3: archivebox config > /data [X] No archivebox index found in the current directory. /data Hint: Are you running archivebox in the right folder? cd path/to/your/archive/folder archivebox [command] Hint: To create a new archive collection or import existing data in this folder, run: archivebox init ```

kerem commented

2026-03-01 14:47:54 +03:00

Author

Owner

@pirate commented on GitHub (Aug 30, 2025):

What directory are in you in on the host? $PWD stores data/ in the current directory, so make sure it's a new empty dir somewhere.

After the first docker run -v $PWD:/data archivebox/archivebox:latest init inside the data dir, then on the host, run chmod -R 777 ., then all docker commands after that should be run from inside the data dir, or change $PWD to the absolute path.

Also don't ignore that warning about not having space remaining, archivebox will refuse to launch if it's below ~50mb.

@pirate commented on GitHub (Aug 30, 2025): What directory are in you in on the host? `$PWD` stores `data/` in the current directory, so make sure it's a new empty dir somewhere. After the first `docker run -v $PWD:/data archivebox/archivebox:latest init` inside the data dir, then on the host, run `chmod -R 777 .`, then all docker commands after that should be run from inside the data dir, or change `$PWD` to the absolute path. Also don't ignore that warning about not having space remaining, archivebox will refuse to launch if it's below ~50mb.

kerem commented

2026-03-01 14:47:54 +03:00

Author

Owner

@pirate commented on GitHub (Jan 8, 2026):

dev has an overhauled dependency management system, so I'm going to close this as stale as none of the relevant code is the same anymore. please open a new issue for any problems you encounter on dev!

It's not stable yet, so dont upgrade any big archive collections, but stay tuned for the next stable release with all the changes.

@pirate commented on GitHub (Jan 8, 2026): `dev` has an overhauled dependency management system, so I'm going to close this as stale as none of the relevant code is the same anymore. please open a new issue for any problems you encounter on `dev`! It's not stable yet, so dont upgrade any big archive collections, but stay tuned for the next stable release with all the changes.

kerem referenced this issue

2026-03-01 17:56:49 +03:00

[GH-ISSUE #1009] Question: binary path in config #2141

kerem referenced this issue

2026-03-14 23:54:32 +03:00

[GH-ISSUE #1009] Question: binary path in config #3652