close
The Wayback Machine - https://web.archive.org/web/20211004032405/https://github.com/sundowndev/phoneinfoga/issues/725
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker - Raspberry Pi 4 - Armv7 build? #725

Open
kllngtme opened this issue Mar 14, 2021 · 17 comments
Open

Docker - Raspberry Pi 4 - Armv7 build? #725

kllngtme opened this issue Mar 14, 2021 · 17 comments

Comments

@kllngtme
Copy link

@kllngtme kllngtme commented Mar 14, 2021

Hi, is it possible to create a docker image for the raspberry pi architecture? It's a ARMV7 build.

When I try to run it up in a docker environment I'm getting a hard crash:

phoneinfoga    | standard_init_linux.go:219: exec user process caused: exec format error
phoneinfoga exited with code 1
@KamilLenica
Copy link

@KamilLenica KamilLenica commented Mar 24, 2021

In the meantime before official containeer is provided You can clone repo and run build locally using included Dockerfile

sundowndev added a commit that referenced this issue Mar 24, 2021
related to #725
@sundowndev
Copy link
Owner

@sundowndev sundowndev commented Mar 29, 2021

@kllngtme Docker image is now available for amd64, arm/v7 & arm64. Could you please try again ? Ensure to use the stable or v2 tag, not latest. Thanks

@kllngtme
Copy link
Author

@kllngtme kllngtme commented Mar 29, 2021

@sundowndev , thankyou. It is loading and working on a raspberry pi 4 now with no issues using stable. One thing I noticed though, trying to search with the webui using the correct E164 numbering doesn't pull up anything and shows "Parameter 'number' must be a valid integer". Using the correct E164 numbering through the CLI IS working without issues though. The example number on the webui used as well as the CLI is 14155552671 as well as +14155552671.

@KamilLenica
Copy link

@KamilLenica KamilLenica commented Mar 29, 2021

@sundowndev Just verified, Container starts up without issues
WebGUI has problem as described by @kllngtme

@sundowndev
Copy link
Owner

@sundowndev sundowndev commented Mar 29, 2021

Just tried using the demo and master branch, it works well:

$ curl -X GET http://localhost:5000/api/numbers/14155552671/scan/local

{"success":true,"error":"","result":{"rawLocal":"4155552671","local":"(415) 555-2671","E164":"+14155552671","international":"14155552671","countryCode":1,"country":"US","carrier":""}}

Could you take a look at the network tab to see what's wrong with the request ?

@kllngtme
Copy link
Author

@kllngtme kllngtme commented Mar 29, 2021

@sundowndev not sure what you mean by network tab

@sundowndev
Copy link
Owner

@sundowndev sundowndev commented Mar 29, 2021

@sundowndev not sure what you mean by network tab

I mean the network tab of the developer tool of your browser. For example, press F12 if you're using Firefox. Ensure to open it before the scan, then click on the errored HTTP request.

@kllngtme
Copy link
Author

@kllngtme kllngtme commented Mar 29, 2021

{success: false, error: "Parameter 'number' must be a valid integer."}
error: "Parameter 'number' must be a valid integer."
success: false

@KamilLenica
Copy link

@KamilLenica KamilLenica commented Mar 29, 2021

@sundowndev i am pretty sure this is problem with frontend. Console commands are working without problem

@sundowndev
Copy link
Owner

@sundowndev sundowndev commented Mar 29, 2021

@sundowndev i am pretty sure this is problem with frontend. Console commands are working without problem

The API responds with an error so the issue comes from the web backend. May be the frontend sends bad data to the API but that sounds weird since it works properly on my end.

Could you provide the complete URL of one of those scan requests ? Also what's the version you're running on?

@kllngtme
Copy link
Author

@kllngtme kllngtme commented Mar 29, 2021

http://192.168.1.226:5000/api/numbers/14155552671/scan/local

{success: false, error: "Parameter 'number' must be a valid integer."}
error: "Parameter 'number' must be a valid integer."
success: false

@sundowndev
Copy link
Owner

@sundowndev sundowndev commented Mar 30, 2021

http://192.168.1.226:5000/api/numbers/14155552671/scan/local

{success: false, error: "Parameter 'number' must be a valid integer."}
error: "Parameter 'number' must be a valid integer."
success: false

@kllngtme Thanks. What response do you get from http://192.168.1.226:5000/api please ? This is gonna be hard to fix if I cannot reproduce it 😕

@sundowndev
Copy link
Owner

@sundowndev sundowndev commented Mar 30, 2021

I pushed a quick patch on the master branch to help us troubleshoot this. Could you pull Docker image on the latest tag and try again? The error will still be here but it should be more explicit. Be sure to use linux/amd64 arch to run this image. Thanks!

@kllngtme
Copy link
Author

@kllngtme kllngtme commented Mar 30, 2021

{success: false, error: "Parameter 'number' must be a valid integer."}
error: "Parameter 'number' must be a valid integer."
success: false

This is the response:
{success: false, error: "Parameter 'number' must be a valid integer."}
error: "Parameter 'number' must be a valid integer."
success: false

@sundowndev
Copy link
Owner

@sundowndev sundowndev commented Mar 30, 2021

{success: false, error: "Parameter 'number' must be a valid integer."}
error: "Parameter 'number' must be a valid integer."
success: false

This is the response:
{success: false, error: "Parameter 'number' must be a valid integer."}
error: "Parameter 'number' must be a valid integer."
success: false

No I meant the response of that particular URL : http://192.168.1.226:5000/api it's supposed to give information about the current Phoneinfoga version.

Example :

$ curl -sSL -X GET 'http://demo.phoneinfoga.crvx.fr/api/' -H 'accept: application/json'

{
  "success": true,
  "version": "v2.3.8",
  "commit": "8403f33"
}

@kllngtme
Copy link
Author

@kllngtme kllngtme commented Mar 31, 2021

Mine isn't showing the version:
The response is {"success":true,"version":"","commit":""}

I'm using stable as well as latest still crashes and comes up with:
phoneinfoga | standard_init_linux.go:219: exec user process caused: exec format error

@sundowndev
Copy link
Owner

@sundowndev sundowndev commented Apr 1, 2021

I'm using stable as well as latest still crashes and comes up with:
phoneinfoga | standard_init_linux.go:219: exec user process caused: exec format error

Yes, as I said, the latest tag is updated from the master branch and is only compatible with linux/amd64.

Mine isn't showing the version:
The response is {"success":true,"version":"","commit":""}

Very strange, I'll to reproduce that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
@KamilLenica @kllngtme @sundowndev and others