#support

Sample Application Installation and Tracing Data Generation

TLDR Eugene is trying to install a sample application and generate tracing data but struggles with failing pods and server errors. Prashant provided a link as a response.

5mo

Join the chat

Jul 10, 2023 (5 months ago)

Photo of md5-0ca37054c6c9042aa04fcfb92cc7d99c

Eugene

02:34 PM

Hello,
I am trying to install sample-application and generate tracing data
https://signoz.io/docs/install/kubernetes/others/#optional-install-a-sample-application-and-generate-tracing-data

But pods cannot start:

Normal   Pulling    6s (x3 over 48s)   kubelet            Pulling image "signoz/locust:0.8.1-py3.6"                                                                                                                   ││   Warning  Failed     5s (x3 over 47s)   kubelet            Failed to pull image "signoz/locust:0.8.1-py3.6": rpc error: code = NotFound desc = failed to pull and unpack image "":  ││ failed to resolve reference "": : not found                                                                                                       ││   Warning  Failed     5s (x3 over 47s)   kubelet            Error: ErrImagePull

When I try to pull the image on my local computer I receive the following error:

docker pull signoz/locust:0.8.1-py3.6
Error response from daemon: manifest for signoz/locust:0.8.1-py3.6 not found: manifest unknown: manifest unknown

Could you please advise how the issue can be solved?

Image 1 for Hello,
I am trying to install sample-application and generate tracing data
<https://signoz.io/docs/install/kubernetes/others/#optional-install-a-sample-application-and-generate-tracing-data>

But pods cannot start:
```Normal Pulling 6s (x3 over 48s) kubelet Pulling image "signoz/locust:0.8.1-py3.6" ││ Warning Failed 5s (x3 over 47s) kubelet Failed to pull image "signoz/locust:0.8.1-py3.6": rpc error: code = NotFound desc = failed to pull and unpack image "<http://docker.io/signoz/locust:0.8.1-py3.6|docker.io/signoz/locust:0.8.1-py3.6>": ││ failed to resolve reference "<http://docker.io/signoz/locust:0.8.1-py3.6|docker.io/signoz/locust:0.8.1-py3.6>": <http://docker.io/signoz/locust:0.8.1-py3.6|docker.io/signoz/locust:0.8.1-py3.6>: not found ││ Warning Failed 5s (x3 over 47s) kubelet Error: ErrImagePull ```
When I try to pull the image on my local computer I receive the following error:
```docker pull signoz/locust:0.8.1-py3.6
Error response from daemon: manifest for signoz/locust:0.8.1-py3.6 not found: manifest unknown: manifest unknown```
Could you please advise how the issue can be solved?

Jul 11, 2023 (5 months ago)

Photo of md5-1899629483c7ab1dccfbee6cc2f637b9

Prashant

06:03 AM

https://signoz-community.slack.com/archives/C01HWUTP4HH/p1689053549239359?thread_ts=1688997895.778209&cid=C01HWUTP4HH

SigNoz Community

Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI

Indexed 1023 threads (61% resolved)

Join Our Community

Similar Threads

Resolving SigNoz v.0.22 Crash for Python Application

COMER reports a SigNoz v.0.22 crash with their Python app. Despite Srikanth's troubleshooting suggestions and confirmation that their application runs fine without `opentelemetry-instrument`, the cause of the problem remains unclear.

1mo

Slow Log Messages in SigNoz with Logrus and OpenTelemetry

Harald reported slow log messages in SigNoz with logrus and open telemetry. They narrowed down the problem to focusing on relevant k8s namespaces, which improved performance to near real-time.

5mo

Node Tracing Error & Angular Console Error

Angeles experienced errors in both node tracing and Angular console. Prashant asked for the guide used, while vishal-signoz checked the express and otel versions. Palash was asked to check the angular part.

9mo