[GH-ISSUE #534] Raspberry Pi: "exec format error" #342

Closed
opened 2026-03-01 14:42:39 +03:00 by kerem · 5 comments
Owner

Originally created by @fn5 on GitHub (Nov 13, 2020).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/534

Describe the bug

When I try and run the second command as provided in the Quickstart I get an error as below.
Let me know if there's anything I can do to help. Thankyou.

Steps to reproduce

$ docker run -v ~/archivebox:/data -it nikisweeting/archivebox manage createsuperuser

Screenshots or log output

standard_init_linux.go:211: exec user process caused "exec format error"

Software versions

  • OS: Raspbian 10 (buster)
  • Python version: 3.7.3
  • Chrome version: Chromium 84.0.4147.141 Built on Raspbian , running on Raspbian 10
Originally created by @fn5 on GitHub (Nov 13, 2020). Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/534 <!-- Please fill out the following information, feel free to delete sections if they're not applicable or if long issue templates annoy you :) --> #### Describe the bug <!-- A description of what the bug is, what you expected to happen, and any relevant context about issue. --> When I try and run the second command as provided in the Quickstart I get an error as below. Let me know if there's anything I can do to help. Thankyou. #### Steps to reproduce <!-- For example: 1. Ran ArchiveBox with the following config '...' 2. Saw this output during archiving '....' 3. UI didn't show the thing I was expecting '....' --> ``` $ docker run -v ~/archivebox:/data -it nikisweeting/archivebox manage createsuperuser ``` #### Screenshots or log output <!-- If applicable, post any relevant screenshots or copy/pasted terminal output from ArchiveBox. If you're reporting a parsing / importing error, **you must paste a copy of your redacted import file here**. --> `standard_init_linux.go:211: exec user process caused "exec format error"` #### Software versions - OS: Raspbian 10 (buster) - Python version: 3.7.3 - Chrome version: Chromium 84.0.4147.141 Built on Raspbian , running on Raspbian 10
Author
Owner

@pirate commented on GitHub (Nov 13, 2020):

ARM is a bit of a special case. You need to build the image on an arm CPU for it to run on arm (or use buildx).

git clone https://github.com/pirate/ArchiveBox
cd ArchiveBox

docker build . -t archivebox
docker run -v ~/archivebox:/data -it archivebox manage createsuperuser
docker run -v ~/archivebox:/data -it archivebox ...
...

If it still doesn't work after that, can you post the output of running the archivebox version command:

docker run -v ~/archivebox:/data -it archivebox version
<!-- gh-comment-id:726591189 --> @pirate commented on GitHub (Nov 13, 2020): ARM is a bit of a special case. You need to *build* the image on an arm CPU for it to run on arm (or use buildx). ```bash git clone https://github.com/pirate/ArchiveBox cd ArchiveBox docker build . -t archivebox docker run -v ~/archivebox:/data -it archivebox manage createsuperuser docker run -v ~/archivebox:/data -it archivebox ... ... ``` If it still doesn't work after that, can you post the output of running the `archivebox version` command: ```bash docker run -v ~/archivebox:/data -it archivebox version ```
Author
Owner

@chrismeller commented on GitHub (Nov 16, 2020):

@pirate You can actually use docker buildx to build images for different architectures. For instance, I use this to build for my Pi3 from my Windows desktop:

docker buildx build --platform=linux/arm/v7 .

<!-- gh-comment-id:727874435 --> @chrismeller commented on GitHub (Nov 16, 2020): @pirate You can actually use docker buildx to build images for different architectures. For instance, I use this to build for my Pi3 from my Windows desktop: `docker buildx build --platform=linux/arm/v7 .`
Author
Owner

@fn5 commented on GitHub (Nov 16, 2020):

Thankyou for your help here.
The build completed successfully, but now upon running init I get this error:

redacted@redacted:~/ArchiveBox $ docker run -v ~/archivebox:/data -it archivebox init
[i] [2020-11-16 10:55:20] ArchiveBox v0.4.21: archivebox init
    > /data

[+] Initializing a new ArchiveBox collection in this folder...
    /data
------------------------------------------------------------------

[+] Building archive folder structure...
Traceback (most recent call last):
  File "/usr/local/bin/archivebox", line 33, in <module>
    sys.exit(load_entry_point('archivebox', 'console_scripts', 'archivebox')())
  File "/app/archivebox/cli/__init__.py", line 123, in main
    run_subcommand(
  File "/app/archivebox/cli/__init__.py", line 63, in run_subcommand
    module.main(args=subcommand_args, stdin=stdin, pwd=pwd)    # type: ignore
  File "/app/archivebox/cli/archivebox_init.py", line 33, in main
    init(
  File "/app/archivebox/util.py", line 113, in typechecked_function
    return func(*args, **kwargs)
  File "/app/archivebox/main.py", line 295, in init
    Path(SOURCES_DIR).mkdir(exist_ok=True)
  File "/usr/local/lib/python3.8/pathlib.py", line 1287, in mkdir
    self._accessor.mkdir(self, mode)
PermissionError: [Errno 13] Permission denied: '/data/sources'

I did this as the init command led to this output:

redacted@redacted:~/ArchiveBox $ docker run -v ~/archivebox:/data -it archivebox manage createsuperuser
[i] [2020-11-16 10:54:25] ArchiveBox v0.4.21: archivebox manage createsuperuser
    > /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
<!-- gh-comment-id:727903504 --> @fn5 commented on GitHub (Nov 16, 2020): Thankyou for your help here. The build completed successfully, but now upon running init I get this error: ``` redacted@redacted:~/ArchiveBox $ docker run -v ~/archivebox:/data -it archivebox init [i] [2020-11-16 10:55:20] ArchiveBox v0.4.21: archivebox init > /data [+] Initializing a new ArchiveBox collection in this folder... /data ------------------------------------------------------------------ [+] Building archive folder structure... Traceback (most recent call last): File "/usr/local/bin/archivebox", line 33, in <module> sys.exit(load_entry_point('archivebox', 'console_scripts', 'archivebox')()) File "/app/archivebox/cli/__init__.py", line 123, in main run_subcommand( File "/app/archivebox/cli/__init__.py", line 63, in run_subcommand module.main(args=subcommand_args, stdin=stdin, pwd=pwd) # type: ignore File "/app/archivebox/cli/archivebox_init.py", line 33, in main init( File "/app/archivebox/util.py", line 113, in typechecked_function return func(*args, **kwargs) File "/app/archivebox/main.py", line 295, in init Path(SOURCES_DIR).mkdir(exist_ok=True) File "/usr/local/lib/python3.8/pathlib.py", line 1287, in mkdir self._accessor.mkdir(self, mode) PermissionError: [Errno 13] Permission denied: '/data/sources' ``` I did this as the init command led to this output: ``` redacted@redacted:~/ArchiveBox $ docker run -v ~/archivebox:/data -it archivebox manage createsuperuser [i] [2020-11-16 10:54:25] ArchiveBox v0.4.21: archivebox manage createsuperuser > /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 ```
Author
Owner

@fdplacido commented on GitHub (Nov 21, 2020):

@jackitsdotcom instead of using the volume (-v) with ~/archivebox:/data, create some directory yourself and point to it (or change ~/archivebox permissions:

mkdir ~/mydocker/myarchivebox
docker run -v ~/mydocker/myarchivebox:/data -it archivebox init

Otherwise the folder can be only written by root, that's why it said Permission denied.

<!-- gh-comment-id:731610350 --> @fdplacido commented on GitHub (Nov 21, 2020): @jackitsdotcom instead of using the volume (`-v`) with `~/archivebox:/data`, create some directory yourself and point to it (or change `~/archivebox` permissions: ``` mkdir ~/mydocker/myarchivebox docker run -v ~/mydocker/myarchivebox:/data -it archivebox init ``` Otherwise the folder can be only written by root, that's why it said Permission denied.
Author
Owner

@pirate commented on GitHub (Nov 23, 2020):

I'm going to close this because the docker buildx workflow for ARM cpus is now merged. https://hub.docker.com/r/archivebox/archivebox

If you're still having permissions errors with the data folder @jackitsdotcom please comment here https://github.com/ArchiveBox/ArchiveBox/issues/539 and I'd be happy to help.

<!-- gh-comment-id:732292116 --> @pirate commented on GitHub (Nov 23, 2020): I'm going to close this because the docker buildx workflow for ARM cpus is now merged. https://hub.docker.com/r/archivebox/archivebox If you're still having permissions errors with the data folder @jackitsdotcom please comment here https://github.com/ArchiveBox/ArchiveBox/issues/539 and I'd be happy to help.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ArchiveBox#342
No description provided.