jorgebastida / jorgebastida/gordon
Docker issue
- Dominant language
- Python
- Stars
- 2k
- Forks
- 132
- PR merge metrics
- No merged PRs in 30d
Description
I pulled the recommended Docker image down with Kitematic and it booted with the following error.
Kind of important for my workflow since I compile a lot of C code for Lambda, but feel free to close if you think this out of scope.
{"errorMessage":"Cannot find module 'index'","errorType":"Error","stackTrace":["Function.Module._load (module.js:276:25)","Module.require (module.js:353:17)","require (internal/module.js:12:17)"]}
START RequestId: 87511eb4-1ea8-15aa-9a36-d93f338f827e Version: $LATEST
Unable to import module 'index': Error
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
END RequestId: 87511eb4-1ea8-15aa-9a36-d93f338f827e
REPORT RequestId: 87511eb4-1ea8-15aa-9a36-d93f338f827e Duration: 14.25 ms Billed Duration: 100 ms Memory Size: 1536 MB Max Memory Used: 24 MB
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the recommended Docker image launch through Kitematic and inspect the AWS Lambda runtime output for the missing index module. Compare the container's startup behavior with the reported C-compilation workflow; done means the image boots and the intended Lambda entry point can be imported without this error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker, node.js
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100