[bug]: `sudo:/app/keploy` command not found when running keploy docker image

keploy / keploy

Test generation for Developers. Generate tests and stubs for your application that actually work!

https://keploy.io

Apache License 2.0

3.4k stars 375 forks source link

[bug]: `sudo:/app/keploy` command not found when running keploy docker image #863

Open gouravkrosx opened 8 months ago

gouravkrosx commented 8 months ago

Is there an existing issue for this?

[X] I have searched the existing issues

Current behavior

When attempting to build and run a Docker image created via a Dockerfile, a 'sudo: /app/keploy' command not found error is encountered. This error arises because the Dockerfile runs a binary named 'keploy' and there is also a 'keploy' folder at the same location used to store keploy-generated tests.

Steps to reproduce

Clone the 'keploy' repository and configure it on your local machine.
Create a folder named 'keploy' in the same location using mkdir keploy
Build keploy docker image using sudo docker build -t keploy .
When you run the 'keploy' image using sudo docker run keploy, you will encounter the same error.

Environment

None

Version

Local

Repository

keploy

officialasishkumar commented 8 months ago

can you share the log/screenshot of your terminal? I am unable to reproduce it.

gouravkrosx commented 8 months ago

kadern0 commented 8 months ago

Cannot reproduce it either.

AniketNS commented 6 months ago

Hey @gouravkrosx, Can I work on this issue?

gouravkrosx commented 6 months ago

Sure @AniketNS. @kadern0 What problems are you facing while reproducing it?

CharvinKhanpara commented 5 months ago

Hello, i and @KrupalUpadhyay are willing to work on it. @gouravkrosx, Can we contribute ?

gouravkrosx commented 5 months ago

@CharvinKhanpara Anyone can contribute to this good first open-source issue.

CharvinKhanpara commented 5 months ago

Screenshot 2023-12-23 145220

@gouravkrosx what kind of output you are expected to come after solving the issue.

KrupalUpadhyay commented 5 months ago

@gouravkrosx, I reproduced and run docker image in my local docker engine. I didn't encounter such an error, docker image runs successfully and it creates a container. Can you elaborate by which method you run it so I could understand the bug you mentioned.

gouravkrosx commented 5 months ago

@KrupalUpadhyay @CharvinKhanpara Let me reproduce at my end once again.

bablysingh2409 commented 4 months ago

Hi @gouravkrosx ,can I work on this issue

CharvinKhanpara commented 4 months ago

@KrupalUpadhyay @CharvinKhanpara Let me reproduce at my end once again.

Okay !

slayerjain commented 4 months ago

I think this issue happens when we have keploy folder, and then try to build the docker image.

A quick fix could be changing the keploy binary name to something like keployBin here - https://github.com/keploy/keploy/blob/1ceee91e12df5bae4fae078f4ab98688cd47e93a/Dockerfile#L19

And then while copying to the runtime stage changing this back to keploy here - https://github.com/keploy/keploy/blob/1ceee91e12df5bae4fae078f4ab98688cd47e93a/Dockerfile#L41