syncing-server icon indicating copy to clipboard operation
syncing-server copied to clipboard

SQL for armf error even after trying tobi321:rpi-mariadb

Open irfanarif-ia opened this issue 4 years ago • 3 comments

Raspberry Pi 4; Getting an sql for armf error when following tutorial i even tried tobi321:rpi-mariadb it says the server is starting

irfanarif-ia avatar Mar 19 '21 18:03 irfanarif-ia

Rails has a delayed logs buffer flush so server is starting is actually ok - give a moment and it should be up and running

can you verify that?

karolsojko avatar Mar 22 '21 07:03 karolsojko

its up and running in the log, but still can't access it no port mapping on docker please check the image attached image

Container Log

see where a bundled gem is installed.

Prestart Step 3/4 - Migrating database

Prestart Step 4/4 - Seeding database

Starting Server...

=> Booting Puma

=> Rails 5.2.5 application starting in production 

=> Run `rails server -h` for more startup options

Puma starting in single mode...

* Puma version: 5.2.2 (ruby 2.6.5-p114) ("Fettisdagsbulle")

*  Min threads: 5

*  Max threads: 5

*  Environment: production

*  PID: 22

* Listening on http://0.0.0.0:3000

Use Ctrl-C to stop

irfanarif-ia avatar Mar 31 '21 19:03 irfanarif-ia

I have a similar issue on a raspberry pi 4b. Since mysql isnt available, i switched to tobi's mariadb and when i start the containers 4 of them decide not to play:

syncing-server_api-gateway_1                ./wait-for.sh syncing-serv ...   Exit 1
syncing-server_auth_1                       ./wait-for.sh syncing-serv ...   Exit 1
syncing-server_cache_1                      docker-entrypoint.sh redis ...   Up       0.0.0.0:49157->6379/tcp
syncing-server_db_1                         docker-entrypoint.sh --def ...   Up       0.0.0.0:49156->3306/tcp
syncing-server_syncing-server-js-worker_1   ./wait-for.sh syncing-serv ...   Exit 1
syncing-server_syncing-server-js_1          ./wait-for.sh syncing-serv ...   Exit 1
syncing-server_syncing-server_1             ./wait-for.sh db 3306 ./wa ...   Up

they all have the same error:

api-gateway_1               | standard_init_linux.go:219: exec user process caused: exec format error
api-gateway_1               | standard_init_linux.go:219: exec user process caused: exec format error
auth_1                      | standard_init_linux.go:219: exec user process caused: exec format error
auth_1                      | standard_init_linux.go:219: exec user process caused: exec format error
syncing-server_auth_1 exited with code 1
syncing-server_api-gateway_1 exited with code 1
syncing-server-js-worker_1  | standard_init_linux.go:219: exec user process caused: exec format error
syncing-server-js_1         | standard_init_linux.go:219: exec user process caused: exec format error
syncing-server-js-worker_1  | standard_init_linux.go:219: exec user process caused: exec format error
syncing-server-js_1         | standard_init_linux.go:219: exec user process caused: exec format error
syncing-server_syncing-server-js_1 exited with code 1
syncing-server_syncing-server-js-worker_1 exited with code 1

are the images maybe wrong?

griefie avatar Apr 10 '21 00:04 griefie