Fix distro detection for raspberry pi

Bug description

I found that starting from version 2.14.0 Prisma support ARM64. Source: https://github.com/prisma/prisma/releases/tag/2.14.0 and https://github.com/prisma/prisma/issues/861#issuecomment-764867224

I need to run project on Raspberry Pi4 8Gb with Ubuntu 20.04.2 Server LTS. Project runs in docker image based on arm64v8/node:14.15.4-buster. Command prisma generate running okay. Project can’t start with the same error as prisma --version shows error:

prisma --version
Error: Could not find introspection-engine binary. Searched in /root/node_modules/prisma/introspection-engine-linux-arm-openssl-1.1.x and /root/node_modules/introspection-engine-linux-arm-openssl-1.1.x

How to reproduce

docker run --rm -it arm64v8/node:14.15.4-buster /bin/bash
root@2682f203a74a:/# npm i -s prisma@2.16.0
+ prisma@2.16.0
added 2 packages from 1 contributor and audited 2 packages in 11.691s
found 0 vulnerabilities

root@2682f203a74a:/# npm i -s @prisma/client@2.16.0
warning The postinstall script automatically ran `prisma generate` and did not find your `prisma/schema.prisma`.
If you have a Prisma schema file in a custom path, you will need to run
`prisma generate --schema=./path/to/your/schema.prisma` to generate Prisma Client.
If you do not have a Prisma schema file yet, you can ignore this message.

+ @prisma/client@2.16.0
added 2 packages from 1 contributor and audited 4 packages in 7.799s
found 0 vulnerabilities

root@2682f203a74a:/# export PATH="/node_modules/.bin:./node_modules/.bin:${PATH}"
root@2682f203a74a:/# prisma --version
Error: Could not find introspection-engine binary. Searched in /node_modules/prisma/introspection-engine-linux-arm-openssl-1.1.x and /node_modules/introspection-engine-linux-arm-openssl-1.1.x
root@2682f203a74a:/#

Expected behavior

prisma version

Prisma information

Project runs in docker image based on arm64v8/node:14.15.4-buster Prisma installed as

npm i -s prisma@2.16.0
npm i -s @prisma/client@2.16.0

Prisma schema is using native

generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["native"]
  output        = "./src/generated/db-client"
}

Environment & setup

uname -a
Linux ubuntu 5.4.0-1028-raspi #31-Ubuntu SMP PREEMPT Wed Jan 20 11:30:45 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

docker version
Client: Docker Engine - Community
 Version:           20.10.3
 API version:       1.41
 Go version:        go1.13.15
 Git commit:        48d30b5
 Built:             Fri Jan 29 14:33:47 2021
 OS/Arch:           linux/arm64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.3
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       46229ca
  Built:            Fri Jan 29 14:32:03 2021
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.4.3
  GitCommit:        269548fa27e0089a8b8278fc4fc781d7f65a939b
 runc:
  Version:          1.0.0-rc92
  GitCommit:        ff819c7e9184c13b7c2607fe6c30ae19403a7aff
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Docker image arm64v8/node:14.15.4-buster uses

docker run --rm -it arm64v8/node:14.15.4-buster /bin/bash
root@2682f203a74a:/# node -v
v14.15.4
root@2682f203a74a:/# npm -v
6.14.10

[jelitter]

Hello! Is there any update on this ? Or any reliable workaround I can follow ? Thanks.

[pantharshit00]

@matthewmueller This issue ain’t about support but correct detection of OS inside of docker in raspberry pi.

I think we need to still look into this one.