[bug]: keploy-config throwing error when containerName is not provided.

[charankamarapu]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

1. Currently When I use keploy with docker and keploy-config. When I don't provide containerName param in the config but provide it in the appCmd it shouldn't throw an error but it is throwing an error.

This is happening because in cmd/record.go we are checking for containerName but only in args not in config. We need to actually check it in appCmd and not in os.args.

Steps to reproduce

1. Run gin-mongo via docker and use keploy-config.

Environment

None

Version

Local

Repository

keploy