Docker setup fails with "executable file not found in $PATH: unknown."

[BreakfastSerial]

I've seen this issue reported before and closed again, but I'm facing the problem. NPM/Node is hell to maintain, if you're not a developer and well versed with the JavaScript package managers, so I'd always prefer Docker.

I'm following the Docker setup guide:

$ git clone https://github.com/aquasecurity/cloudsploit.git
$ cd cloudsploit
$ docker build . -t cloudsploit:0.0.1
$ docker run cloudsploit:0.0.1 -h
$ docker run -e AWS_ACCESS_KEY_ID=XX -e AWS_SECRET_ACCESS_KEY=YY cloudsploit:0.0.1 --compliance=pci

---

$ docker build . -t cloudsploit:0.0.1
Sending build context to Docker daemon  20.64MB
Step 1/7 : FROM node:lts-alpine3.12
 ---> 7ae9aa692723
Step 2/7 : ARG PACKAGENAME=cloudsploit
 ---> Using cache
 ---> 947b6a7c54ce
Step 3/7 : COPY . /var/scan/cloudsploit/
 ---> Using cache
 ---> b1acb18b9432
Step 4/7 : RUN cd /var/scan && npm init --yes && npm install ${PACKAGENAME} && npm link /var/scan/cloudsploit
 ---> Using cache
 ---> 731f1d6839e4
Step 5/7 : ENV PATH "$PATH:/var/scan/node_modules/.bin"
 ---> Using cache
 ---> 396bde21e4ef
Step 6/7 : ENTRYPOINT ["cloudsploitscan"]
 ---> Using cache
 ---> 2522adda6a98
Step 7/7 : CMD []
 ---> Using cache
 ---> b4d40a09f3ec
Successfully built b4d40a09f3ec
Successfully tagged cloudsploit:0.0.1

The following step fails for me with:

$ docker run cloudsploit:0.0.1 -h
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "cloudsploitscan": executable file not found in $PATH: unknown.
ERRO[0001] error waiting for container: context canceled 

I've also tried to add the trailing slash, as suggested here: https://github.com/aquasecurity/cloudsploit/issues/1118#issuecomment-1117654018, but that didn't work for me.

On Debian 12, docker --version #Docker version 20.10.24+dfsg1, build 297e128.

[Unbound3d]

Did you manage to fix the issue? Changing ENTRYPOINT ["cloudsploitscan"] to ENTRYPOINT ["cloudsploit-scan"] in the Dockerfile seems to resolve the issue for me.

[dlew56]

Did you manage to fix the issue? Changing ENTRYPOINT ["cloudsploitscan"] to ENTRYPOINT ["cloudsploit-scan"] in the Dockerfile seems to resolve the issue for me.

This resolved it for me. Thanks @Unbound3d