missing dependencies

Open
#12 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, elixir
Domain
backend, cloud

Research direction

Start by inspecting the /var/task/bootstrap entry point and the /var/task/bin/playground runtime invocation shown in the log. Reproduce the custom runtime in AWS Lambda and investigate the reported shared-library version requirements for libtinfo, libz, and libm. Done means the Elixir runtime starts without these dependency errors.

Written by the indexing model from the issue text.

Description

START RequestId: 8129d07b-d4f2-4c9c-878e-9587c4f5bce6 Version: $LATEST
++ dirname /var/task/bootstrap
+ BASE=/var/task
+ EXE=/var/task/bin/playground
+ HOME=/tmp
+ export HOME
+ export RELEASE_READ_ONLY=true
+ RELEASE_READ_ONLY=true
+ export LD_LIBRARY_PATH=/lib64:/usr/lib64:/var/runtime:/var/runtime/lib:/var/task:/var/task/lib:/opt/lib:/var/task/lib/elixir_runtime-0.1.0/priv
+ LD_LIBRARY_PATH=/lib64:/usr/lib64:/var/runtime:/var/runtime/lib:/var/task:/var/task/lib:/opt/lib:/var/task/lib/elixir_runtime-0.1.0/priv
+ /var/task/bin/playground start
/var/task/erts-10.6.4/bin/beam.smp: /lib64/libtinfo.so.6: no version information available (required by /var/task/erts-10.6.4/bin/beam.smp)
/var/task/erts-10.6.4/bin/beam.smp: /lib64/libz.so.1: version `ZLIB_1.2.7.1' not found (required by /var/task/erts-10.6.4/bin/beam.smp)
/var/task/erts-10.6.4/bin/beam.smp: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /var/task/erts-10.6.4/bin/beam.smp)
END RequestId: 8129d07b-d4f2-4c9c-878e-9587c4f5bce6
REPORT RequestId: 8129d07b-d4f2-4c9c-878e-9587c4f5bce6	Duration: 662.47 ms	Billed Duration: 663 ms	Memory Size: 128 MB	Max Memory Used: 5 MB	
RequestId: 8129d07b-d4f2-4c9c-878e-9587c4f5bce6 Error: Runtime exited with error: exit status 1
Runtime.ExitError
Dominant language
Elixir
Stars
129
Forks
31
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws-samples/aws-lambda-elixir-runtime

All issues in aws-samples/aws-lambda-elixir-runtime

Similar issues

More Elixir issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.