Latest Action

[knxp34]

Hello Team

When attempting run the latest action I get:
"docker: Error response from daemon: unable to find user mobsf: no matching entries in passwd file."

Perhaps the user in the docker image changed again?

Full step output:

Run fundacaocerti/mobsf-action@v1.7.[2]
env:
JAVA_HOME_12.0.2_x64: /opt/hostedtoolcache/jdk/12.0.2/x64
JAVA_HOME: /opt/hostedtoolcache/jdk/12.0.2/x64
JAVA_HOME_12_0_2_X64: /opt/hostedtoolcache/jdk/12.0.2/x64
INPUT_FILE_NAME: build/app/outputs/apk/app.apk
SCAN_TYPE: apk
OUTPUT_FILE_NAME: mobsf-report
/usr/bin/docker run --name f155486fde8f45edb49c993ff06cde7e0c710_0e71e8 --label 6f1554 --workdir /github/workspace --rm -e JAVA_HOME_12.0.2_x64 -e JAVA_HOME -e JAVA_HOME_12_0_2_X64 -e INPUT_FILE_NAME -e SCAN_TYPE -e OUTPUT_FILE_NAME -e HOME -e GITHUB_JOB -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_REPOSITORY_OWNER -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RETENTION_DAYS -e GITHUB_RUN_ATTEMPT -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_SERVER_URL -e GITHUB_API_URL -e GITHUB_GRAPHQL_URL -e GITHUB_REF_NAME -e GITHUB_REF_PROTECTED -e GITHUB_REF_TYPE -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e GITHUB_ACTION_REPOSITORY -e GITHUB_ACTION_REF -e GITHUB_PATH -e GITHUB_ENV -e GITHUB_STEP_SUMMARY -e RUNNER_OS -e RUNNER_ARCH -e RUNNER_NAME -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e ACTIONS_CACHE_URL -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/emc-KeyAttestation/emc-KeyAttestation":"/github/workspace" 6f1554:86fde8f45edb49c993ff06cde7e0c710
docker: Error response from daemon: unable to find user mobsf: no matching entries in passwd file.

[abualialfatih23]

is there any way to solve this problem?, i also faced same issue

[Sherlouk]

Plus one 🙂

[mutairibassam]

@knxp34 @Sherlouk @abualialfatih23 I faced the same issue, and I solved it by reverting back to release v1.7.1.

[JonasVautherin]

Same thing here, v1.7.1 works, but v1.7.2 does not.