Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rsg for testing Docker API #2

Closed
rajusreenivasan opened this issue Apr 8, 2020 · 2 comments
Closed

rsg for testing Docker API #2

rajusreenivasan opened this issue Apr 8, 2020 · 2 comments
Assignees

Comments

@rajusreenivasan
Copy link

We wanted to test the usage of APIs hosted in Kubernetes. I came to know that the feature is not available and the tool can be used to test locally hosted APIs. So I am trying to run a Docker image in my developer machine and test the API using localhost. But it is not working as expected. The steps performed is given below

  1. Created Docker image with Python Django image to expose Rest API
  2. Started the container in the developer machine

docker run -p 8090:8080 djangoimage:1.0
Watching for file changes with StartReloader

  1. Started duplicate session and verified the API

curl -i http://127.0.0.1:8090/
Hello World. You are at the index page

  1. Executed below rsg command

rsg --target test/test --api-path / --api-port 8090
Launching test/test for idle state resource usage assessment
Found idle state resource usage. Memory 0 kb CPU: 0 ms

  1. The docker is also throwing below error message in the first session
    ConnectionResetError: [Error 104] Connection reset by peer

Can you please look into the issue ? Can we use the tool to test Rest API created using Docker containers ?

Thanks
Raju Sreenivasan

@mhausenblas mhausenblas self-assigned this Apr 8, 2020
@mhausenblas
Copy link
Owner

I'm not sure what you're trying to do here. As per the docs the --target needs to be the SOT.

@rajusreenivasan
Copy link
Author

oh i am sorry. AWS suggested this tool to test the Rest API before deploying to Kubernetes Cluster. I did not read the documentation properly. Thanks for the clarifications

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants