Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

Im having issues with a failed deployment. based on the below log - i think - it is because the command “lsof” is not recognized - but i am not sure. I also have no idea how to go about fixing this, as lsof is not a call i am making but something from an npm installed package.
node:events:491
[2022-09-28 05:28:32] throw er; // Unhandled 'error' event
[2022-09-28 05:28:32] ^
[2022-09-28 05:28:32]
[2022-09-28 05:28:32] Error: spawn lsof ENOENT
[2022-09-28 05:28:32] at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
[2022-09-28 05:28:32] at onErrorNT (node:internal/child_process:478:16)
[2022-09-28 05:28:32] at processTicksAndRejections (node:internal/process/task_queues:83:21)
[2022-09-28 05:28:32] Emitted 'error' event on ChildProcess instance at:
[2022-09-28 05:28:32] at Process.ChildProcess._handle.onexit (node:internal/child_process:289:12)
[2022-09-28 05:28:32] at onErrorNT (node:internal/child_process:478:16)
[2022-09-28 05:28:32] at processTicksAndRejections (node:internal/process/task_queues:83:21) {
[2022-09-28 05:28:32] errno: -2,
[2022-09-28 05:28:32] code: 'ENOENT',
[2022-09-28 05:28:32] syscall: 'spawn lsof',
[2022-09-28 05:28:32] path: 'lsof',
[2022-09-28 05:28:32] spawnargs: [ '-s', 'TCP:LISTEN', '-i', ':8302' ]
[2022-09-28 05:28:32] }
bpdsksrtmj
Niketan Sharma
819167b5336c456e9ad38395fec1c5
SarkariResultht
e3002a14a547406799fe27a6abf211
9e483d26583f44f6bafe369a29b405
keneucker
keneucker
Shamoil Khan
Frederik
f25932a0b984430fb48c4256f1aaad