Forem Creators and Builders

Cover image for Exec format error
Thomas Bnt
Thomas Bnt

Posted on • Updated on

Exec format error

I started to learn Docker and would like to install Forem on my Raspberry Pi 3.

Once Docker and docker-compose are installed, I cloned the good repository (almost 3Go 😵) and execute bin/container-setup.

Error when I install with bin/container-setup

I would like a little help for that :c

Full text of this image
Attaching to forem_redis, forem_bundle, forem_yarn, forem_postgresql, forem_rails, forem_seed, forem_sidekiq, forem_webpacker
forem_postgresql |
forem_postgresql | PostgreSQL Database directory appears to contain a database; Skipping initialization
forem_postgresql |
forem_postgresql | 2021-11-29 17:42:16.230 UTC [1] FATAL:  could not write lock file "postmaster.pid": No space left on device
bundle_1     | standard_init_linux.go:228: exec user process caused: exec format error
rails_1      | standard_init_linux.go:228: exec user process caused: exec format error
forem_postgresql exited with code 1
redis_1      | 1:C 29 Nov 2021 17:42:15.059 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1      | 1:C 29 Nov 2021 17:42:15.059 # Redis version=6.0.9, bits=32, commit=00000000, modified=0, pid=1, just started
redis_1      | 1:C 29 Nov 2021 17:42:15.059 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1      | 1:M 29 Nov 2021 17:42:15.066 # Warning: 32 bit instance detected but no memory limit set. Setting 3 GB maxmemory limit with 'noeviction' policy now.
redis_1      | 1:M 29 Nov 2021 17:42:15.067 * Running mode=standalone, port=6379.
redis_1      | 1:M 29 Nov 2021 17:42:15.067 # Server initialized
redis_1      | 1:M 29 Nov 2021 17:42:15.067 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1      | 1:M 29 Nov 2021 17:42:15.068 * Ready to accept connections
seed_1       | standard_init_linux.go:228: exec user process caused: exec format error
forem_bundle exited with code 1
sidekiq_1    | standard_init_linux.go:228: exec user process caused: exec format error
forem_seed exited with code 1
forem_rails exited with code 1
webpacker_1  | standard_init_linux.go:228: exec user process caused: exec format error
yarn_1       | standard_init_linux.go:228: exec user process caused: exec format error
forem_yarn exited with code 1
forem_sidekiq exited with code 1
forem_webpacker exited with code 1
Enter fullscreen mode Exit fullscreen mode

Discussion (4)

Collapse
derekenos profile image
derekenos

I've made some recent progress in getting Forem to run on a Raspberry Pi 4.

The major things I needed to do were:

It's a work-in-progress, and the Docker image takes approx. 1.5 hours to build on my pi, but these steps should result in a development build running on the rpi4:

git clone --depth=1 --branch=raspberrypi4 https://github.com/derekenos/forem
cd forem
docker build -f Dockerfile-rpi4-development -t quay.io/forem/forem:development .
docker-compose up
Enter fullscreen mode Exit fullscreen mode
Collapse
thomasbnt profile image
Thomas Bnt Author

Awesome!

Collapse
jrop profile image
jrop

Most Docker containers are built for 64-bit, and Raspberry Pi is running on the ARM architecture. exec format error is probably complaining that a ARM CPU can execute a 64-bit image. That's my best guess without seeing more details.

Collapse
thomasbnt profile image
Thomas Bnt Author

Thanks for your response 👍