fix: Used absolute path to index.js in entrypoint #176
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When this image is used as a docker executor in CircleCI, the entrypoint gets disabled and the user has to explicitly invoke the entrypoint script. So the effective
docker run
command that gets executed would look something like below:In such a case, the run fails with exit code
1
without displaying any error message. The contents of theaction.log
, when viewed manually, are below:Using an absolute path in the
node
command asnode /index.js
instead ofnode index.js
fixes the above error.As for the container exiting before the error messages are displayed, it is due to the
set -e
line. To exit the container after displaying the errors, I have removed theset -e
statement, captured the exit code of thenode
command which I have used as the exit code for the script after displaying the contents ofaction.log