Suspected bug upon RapiDAST container startup

[dreyes333]

Hi, was trying to use latest image yesterday and got the error message below upon container initialization. I suspect it might be due to this commit but I'm not too sure.

usage: rapidast.py [-h]
                   [--log-level {debug,verbose,info,warning,error,critical}]
                   [--config CONFIG_FILE] [--no-cleanup]
rapidast.py: error: unrecognized arguments: sh -c if [ -x /usr/local/bin/bash ]; then
	exec /usr/local/bin/bash 
elif [ -x /usr/bin/bash ]; then
	exec /usr/bin/bash 
elif [ -x /bin/bash ]; then
	exec /bin/bash 
elif [ -x /usr/local/bin/sh ]; then
	exec /usr/local/bin/sh 
elif [ -x /usr/bin/sh ]; then
	exec /usr/bin/sh 
elif [ -x /bin/sh ]; then
	exec /bin/sh 
elif [ -x /busybox/sh ]; then
	exec /busybox/sh 
else
	echo shell not found
	exit 1
fi

[sfowl]

Hi @dreyes333 could you share the command/method you are using to run the container image? I don't seem to be able to reproduce this.

[dreyes333]

Hi @sfowl, I am using the image in a Gitlab CI job

2.9.0 seems to be stable but when using latest it messes up during job initialization , it doesn't even get to the script part.

Thanks for the quick reply

[sfowl]

@dreyes333 Thank you for the hint. I've made a PR with an example of how to use the most recent version of rapidast in gitlab, could you check if it helps you?

EDIT: Also, based on your report we have updated our release notes with a warning: https://github.com/RedHatProductSecurity/rapidast/releases/tag/2.9.1

[dreyes333]

@sfowl thank you for looking into this. Added the entrypoint using latest version and that seems to work 👍