[GH-ISSUE #903] Singlefile not working in docker-compose on arm64 (M1 Macs, RPi 4, etc.)

kerem commented

2026-03-01 14:44:36 +03:00

Owner

Originally created by @jillisstada on GitHub (Dec 16, 2021).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/903

Have archivebox running local on my mac which works fine with a local installed single-file.
Want to user docker-compose run archivebox add .... with single-file
docker-compose run archivebox works but not single-file

      > singlefile
        Extractor failed:                                                                                                                                                                             
             SingleFile was not able to archive the page
            Got single-file response code: 0.

I added in Archivebox.conf

[DEPENDENCY_CONFIG]
SINGLEFILE_BINARY = /opt/homebrew/lib/node_modules/single-file/cli/single-file

Maybe this is more a docker question?

Originally created by @jillisstada on GitHub (Dec 16, 2021). Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/903 Have archivebox running local on my mac which works fine with a local installed single-file. Want to user docker-compose run archivebox add .... with single-file docker-compose run archivebox works but not single-file ```logs > singlefile Extractor failed: SingleFile was not able to archive the page Got single-file response code: 0. ``` I added in Archivebox.conf ```ini [DEPENDENCY_CONFIG] SINGLEFILE_BINARY = /opt/homebrew/lib/node_modules/single-file/cli/single-file ``` Maybe this is more a docker question?

kerem

2026-03-01 14:44:36 +03:00

closed this issue
added the
help wanted

touches: dependencies/packaging
labels

kerem commented

2026-03-01 14:44:37 +03:00

Author

Owner

@jillisstada commented on GitHub (Dec 16, 2021):

docker-compose archivebox --version gives:
√ SINGLEFILE_BINARY v0.3.16 valid /node/node_modules/single-file/cli/single-file
which is not on my mac
doesn't read my ArchiveBox.conf?

docker-composer run archivebox setup :

[+] Installing enabled ArchiveBox dependencies automatically...

    Installing YOUTUBEDL_BINARY automatically using pip...
2021.04.26 is already installed youtube-dl

    Installing CHROME_BINARY automatically using playwright...
Chromium 89.0.4389.114 built is already installed chromium

    Installing SINGLEFILE_BINARY, READABILITY_BINARY, MERCURY_BINARY automatically using npm...
SINGLEFILE_BINARY, READABILITY_BINARY, and MERCURURY_BINARY are already installed

[√] Set up ArchiveBox and its dependencies successfully.

@jillisstada commented on GitHub (Dec 16, 2021): docker-compose archivebox --version gives: `√ SINGLEFILE_BINARY v0.3.16 valid /node/node_modules/single-file/cli/single-file` which is not on my mac doesn't read my `ArchiveBox.conf`? docker-composer run archivebox setup : ```logs [+] Installing enabled ArchiveBox dependencies automatically... Installing YOUTUBEDL_BINARY automatically using pip... 2021.04.26 is already installed youtube-dl Installing CHROME_BINARY automatically using playwright... Chromium 89.0.4389.114 built is already installed chromium Installing SINGLEFILE_BINARY, READABILITY_BINARY, MERCURY_BINARY automatically using npm... SINGLEFILE_BINARY, READABILITY_BINARY, and MERCURURY_BINARY are already installed [√] Set up ArchiveBox and its dependencies successfully. ```

kerem commented

2026-03-01 14:44:37 +03:00

Author

Owner

@pirate commented on GitHub (Dec 16, 2021):

Docker uses a linux system and has all its dependencies bundled with it internally already, do not set SINGLEFILE_BINARY or any other _BINARY configs when using docker.

If it's still not working after removing those settings, please post your full docker-compose.yml config and ArchiveBox.conf config contents.

@pirate commented on GitHub (Dec 16, 2021): Docker uses a linux system and has all its dependencies bundled with it internally already, do not set ` SINGLEFILE_BINARY` or any other `_BINARY` configs when using docker. If it's still not working after removing those settings, please post your full `docker-compose.yml` config and `ArchiveBox.conf` config contents.

kerem commented

2026-03-01 14:44:37 +03:00

Author

Owner

@jillisstada commented on GitHub (Dec 16, 2021):

Thanks for responding
I added the setting because it didn't work.
get this error

      > singlefile
        Extractor failed:                                                                                                                                                                             
             SingleFile was not able to archive the page
            Got single-file response code: 0.

attached yml and conf as zip
Archive.zip

@jillisstada commented on GitHub (Dec 16, 2021): Thanks for responding I added the setting because it didn't work. get this error ```logs > singlefile Extractor failed: SingleFile was not able to archive the page Got single-file response code: 0. ``` attached yml and conf as zip [Archive.zip](https://github.com/ArchiveBox/ArchiveBox/files/7730660/Archive.zip)

kerem commented

2026-03-01 14:44:37 +03:00

Author

Owner

@pirate commented on GitHub (Dec 16, 2021):

You have SAVE_SINGLEFILE = False and SINGLEFILE_BINARY = /opt/homebrew/lib/node_modules/single-file/cli/single-file still set in your config, please remove those and try again.

You can also try changing the image to use the latest version: image: ${DOCKER_IMAGE:-archivebox/archivebox:dev} (:dev instead of :master).

@pirate commented on GitHub (Dec 16, 2021): You have `SAVE_SINGLEFILE = False` and `SINGLEFILE_BINARY = /opt/homebrew/lib/node_modules/single-file/cli/single-file` still set in your config, please remove those and try again. You can also try changing the image to use the latest version: `image: ${DOCKER_IMAGE:-archivebox/archivebox:dev}` (`:dev` instead of `:master`).

kerem commented

2026-03-01 14:44:37 +03:00

Author

Owner

@jillisstada commented on GitHub (Dec 16, 2021):

before adding SINGLEFILE_BINARY it didn't work, that's why I put it in, it should not be there anymore.
SAVE_SINGLEFILE = False because I don't want single file all the time.
I wrote a program that sets SAVE_SINGLEFILE = True occasionally :

docker-compose run archivebox  config --set SAVE_SINGLEFILE=True

With the local installed archivebox without docker that works fine;
I'll try your suggestions tomorrow, latest version and always true.

Thank You

@jillisstada commented on GitHub (Dec 16, 2021): before adding `SINGLEFILE_BINARY` it didn't work, that's why I put it in, it should not be there anymore. `SAVE_SINGLEFILE = False` because I don't want single file all the time. I wrote a program that sets `SAVE_SINGLEFILE = True` occasionally : ```bash docker-compose run archivebox config --set SAVE_SINGLEFILE=True ``` With the local installed archivebox without docker that works fine; I'll try your suggestions tomorrow, latest version and always true. Thank You

kerem commented

2026-03-01 14:44:37 +03:00

Author

Owner

@jillisstada commented on GitHub (Dec 17, 2021):

Terminal Saved Output.txt
I've tried docker-compose with and without default Archivebox.conf and with :dev, output in attachment.
I keep getting the error.

      > singlefile
        Extractor failed:                                                                                                                                                                             
             SingleFile was not able to archive the page
            Got single-file response code: 0.

I'm running on a mac M1 but that shouldn't be the problem.
archivebox and single-file installed on the mac works fine.
I will take a docker course

@jillisstada commented on GitHub (Dec 17, 2021): [Terminal Saved Output.txt](https://github.com/ArchiveBox/ArchiveBox/files/7733821/Terminal.Saved.Output.txt) I've tried docker-compose with and without default `Archivebox.conf` and with `:dev`, output in attachment. I keep getting the error. ```logs > singlefile Extractor failed: SingleFile was not able to archive the page Got single-file response code: 0. ``` I'm running on a mac M1 but that shouldn't be the problem. archivebox and single-file installed on the mac works fine. I will take a docker course

kerem commented

2026-03-01 14:44:37 +03:00

Author

Owner

@jillisstada commented on GitHub (Dec 21, 2021):

@jillisstada commented on GitHub (Dec 21, 2021): ![Screenshot 2021-12-21 at 09 52 49](https://user-images.githubusercontent.com/48590240/146900603-d2181e09-b14d-4983-b310-be56c59fdf2d.png)

kerem commented

2026-03-01 14:44:37 +03:00

Author

Owner

@jillisstada commented on GitHub (Dec 23, 2021):

installed docker archivebox on a intel chip mac, no problem

@jillisstada commented on GitHub (Dec 23, 2021): installed docker archivebox on a intel chip mac, no problem

kerem commented

2026-03-01 14:44:37 +03:00

Author

Owner

@pirate commented on GitHub (Dec 23, 2021):

Ah that makes sense, I was wondering why I've been unable to reproduce this on my Intel mac.

@pirate commented on GitHub (Dec 23, 2021): Ah that makes sense, I was wondering why I've been unable to reproduce this on my Intel mac.

kerem commented

2026-03-01 14:44:37 +03:00

Author

Owner

@tam481 commented on GitHub (Jan 24, 2022):

Hello, I recently started using ArchiveBox (Brilliant product. Well done). I am getting the same error on my Raspberry Pi 4 (arch64) running Debian Bullseye. Apologies if that is a different issue.

Whenever I try to archive a page I get:
singlefile Extractor failed: SingleFile was not able to archive the page Got single-file response code: 0.

@tam481 commented on GitHub (Jan 24, 2022): Hello, I recently started using ArchiveBox (Brilliant product. Well done). I am getting the same error on my Raspberry Pi 4 (arch64) running Debian Bullseye. Apologies if that is a different issue. Whenever I try to archive a page I get: singlefile Extractor failed: SingleFile was not able to archive the page Got single-file response code: 0.

kerem commented

2026-03-01 14:44:37 +03:00

Author

Owner

@darkstar commented on GitHub (Jan 28, 2022):

This is actually #905 the single-file error is a red herring. If you enter the container and execute the commands it tells you to, you see that it's not finding the correct chromium executable

@darkstar commented on GitHub (Jan 28, 2022): This is actually #905 the single-file error is a red herring. If you enter the container and execute the commands it tells you to, you see that it's not finding the correct chromium executable

kerem commented

2026-03-01 14:44:37 +03:00

Author

Owner

@pirate commented on GitHub (Apr 21, 2022):

I believe I fixed it in the latest commits on dev github.com/ArchiveBox/ArchiveBox@57df65f28f / in the latest Docker release: https://hub.docker.com/layers/archivebox/archivebox/archivebox/0.6.3

I also bumped chromium, yt-dlp, youtube-dl, ripgrep, git, single-file, and a few other dependencies to their latest versions ^.

Give it a shot and let me know if it works on your machines. If you still have issues comment back here and I'll reopen the ticket.

@pirate commented on GitHub (Apr 21, 2022): I believe I fixed it in the latest commits on dev https://github.com/ArchiveBox/ArchiveBox/commit/57df65f28fe72677d21e29ce6c9e9d7bcd0ba918 / in the latest Docker release: https://hub.docker.com/layers/archivebox/archivebox/archivebox/0.6.3 I also bumped chromium, yt-dlp, youtube-dl, ripgrep, git, single-file, and a few other dependencies to their latest versions ^. Give it a shot and let me know if it works on your machines. If you still have issues comment back here and I'll reopen the ticket.

kerem commented

2026-03-01 14:44:38 +03:00

Author

Owner

@darkstar commented on GitHub (Apr 21, 2022):

Works for me now 👍
thanks for the fix!

@darkstar commented on GitHub (Apr 21, 2022): Works for me now 👍 thanks for the fix!

kerem referenced this issue

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

[GH-ISSUE #564] New Extractor Idea: gallery-dl for image gallery downloading #1869

kerem referenced this issue

2026-03-14 22:30:39 +03:00