udocker Issue on AWS Lambda with ARM64 Architecture

[sourabh-prasad]

When attempting to run udocker with the fakechroot engine on AWS Lambda using the aarch64 (ARM64) architecture, the execution fails. This issue prevents users from utilizing udocker within Lambda functions on ARM-based Lambda instances when the fakechroot engine is selected. we are using udocker latest version.

Reproduction Steps

1. Trying to execute a Python script with the python:3.9-alpine3.18 Docker image from public.ecr.aws/docker/library/.

2. The command being executed is:

  ['/opt/udocker/udocker', '--quiet', 'run', '-v', '/tmp', '-v', '/tmp/tmpnevtmuyu', '-v', '/tmp/tmpwjm2uz25', '-v', '/dev', '-v', '/proc', '-v', '/etc/hosts', '--nosysdirs', '--env', 'REQUEST_ID=5e4999ca-0cb4-4fc9-9664-ecacbd950291', '--env', 'INSTANCE_IP=169.254.41.157', '--env', 'INPUT_FILE_PATH=/tmp/tmpnevtmuyu/event_file', '--env', 'TMP_OUTPUT_DIR=/tmp/tmpwjm2uz25', '--entrypoint=/bin/sh /tmp/tmpnevtmuyu/script.sh', 'udocker_container']

Error Details

• Error message: bin/sh: No such file or directory in aarch64

• Fakechroot engine return code: 127

• Fakechroot engine stdout: (empty)

• Fakechroot engine stderr: env: /tmp/shared/udocker/containers/305c14b0-a8f1-388a-bde3-217d70f161b7/ROOT/bin/sh: No such file or directory