Open dnelaturi opened 1 year ago
Hi @dnelaturi, thanks for the issue! Can you please provide the Dockerfile for your image so I may debug? From what I can see this is not an issue with the Alpine base image. Rather, I suspect there is some type of unique line in the Dockerfile that Tern's parser does not recognize or an environment variable that Tern cannot properly export, hence the /bin/sh: export: line 0: JAVA_OPTS:: bad variable name
error that is throwing off the results.
while running tern on container image with alpine base image seeing following errors
/bin/sh: export: line 0: JAVA_OPTS:: bad variable name /bin/sh: export: line 0: JAVA_OPTS:: bad variable name /bin/sh: export: line 0: JAVA_OPTS:: bad variable name /bin/sh: export: line 0: JAVA_OPTS:: bad variable name /bin/sh: export: line 0: JAVA_OPTS:: bad variable name /bin/sh: export: line 0: JAVA_OPTS:: bad variable name
To Reproduce Steps to reproduce the behavior:
for image layer1 the output is clean Layer 1: info: Layer created by commands: /bin/sh -c #(nop) ADD file:9a4f77dfaba7fd2aa78186e4ef0e7486ad55101cefc1fabbc1b385601bb38920 in / info: Found 'Alpine Linux v3.17' in /etc/os-release. info: Retrieved package metadata using apk default method.
=======================================================================================
/bin/sh: export: line 0: JAVA_OPTS:: bad variable name /bin/sh: export: line 0: JAVA_OPTS:: bad variable name /bin/sh: export: line 0: JAVA_OPTS:: bad variable name /bin/sh: export: line 0: JAVA_OPTS:: bad variable name /bin/sh: export: line 0: JAVA_OPTS:: bad variable name /bin/sh: export: line 0: JAVA_OPTS:: bad variable name
=======================================================================================
Expected behavior Expected to see the results without errors.
Environment you are running Tern on Enter all that apply
Please attach files if they exist