Skip to content
This repository has been archived by the owner on May 20, 2021. It is now read-only.

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

Open
irfanarif-ia opened this issue Mar 19, 2021 · 3 comments
Open

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

irfanarif-ia opened this issue Mar 19, 2021 · 3 comments
Assignees
Labels
help wanted Extra attention is needed

Comments

@irfanarif-ia
Copy link

irfanarif-ia commented Mar 19, 2021

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

@JaspalSuri JaspalSuri changed the title Raspberry Pi 4; Getting an sql for armf error when following tutorial i even tried tobi321:rpi-mariadb it says the server is starting SQL for armf error even after trying tobi321:rpi-mariadb Mar 20, 2021
@JaspalSuri JaspalSuri added the help wanted Extra attention is needed label Mar 20, 2021
@karolsojko
Copy link
Member

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?

@irfanarif-ia
Copy link
Author

irfanarif-ia commented Mar 31, 2021

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 https://0.0.0.0:3000

Use Ctrl-C to stop

@griefie
Copy link

griefie commented Apr 10, 2021

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?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants