Emulation layer used on arm64 to run amd64 image breaks peer2profit logic

[MRColorR]

The pee2profit deb package is for x64 so the image was rebuilt for amd64 arch only and I was thinking of using binfmt as the emulation layer on arm devices. With this setup:

• The peer2profit app launches in both amd64 host and arm64 host containers (the container here runs the emulation layer)
• VNC connection is good for both. I can enter the peer2profit details and the device will show up in the devices in the peer2profit dashboard. But:
• Peer2profit containers running on an amd64 host state turn green
• Peer2profit containers running on an arm64 host state remain gray and seem unable to get IP and location information.

To help during troubleshooting in the image some optional packages such as strace are now included.

Any help is welcome, feel free to participate and send pull requests.

[MRColorR]

my findings so far are:

• an x64 image will work as expected if running on a docker x64 machine, after some time in the dashboard the node will go from gray to green, IP information is populated correctly in the dashboard
• on an arm64 device using the binfmt emulation layer the same x64 image will boot (GUI appears and email is accepted, login successful) but then in the dashboard the node will remain grey, no IP information.

so the problem could be one or more of these things:

• maybe the binfmt emulation layer causes problems at the network level
• maybe the peer2profit app can detect that it's running inside an emulation layer and doesn't proceed after login
• maybe the peer2profit app can detect that it's running on a different architecture and doesn't proceed after login

[MRColorR]

maybe we could try box64 as emulator