#general

Changing Port Number for Docker Container

TLDR Ramya had issues with port 9000 not being available. Yash rV suggested binding an available port, which resolved the problem.

4mo

Join the chat

Jul 25, 2023 (4 months ago)

Photo of md5-080141ed2f7a4ebfb0eb0761cd5d70f2

Ramya

06:24 AM

9000 port is not avilable can we change the port number

Photo of md5-cf77c5ac54f90e38660b2ee9331d5457

Yash rV

09:10 AM

Have you tried to bind an available port with port 9000 of your container? To achieve this, you'll need to make adjustments in the clickhouse section of docker-compose.yaml file locally.

Ramya

09:53 AM

yes tried working now

09:53

Ramya

09:53 AM

thanks

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

Troubleshooting SigNoz Local Setup on M1 Mac

Sindhu had issues with their local SigNoz installation using Docker on an M1 Mac. Srikanth helped diagnose the problem. It was resolved by manually starting the ClickHouse container and then starting SigNoz via Docker Compose in the terminal.

8mo

Issue Resolved: Unable to Update Metrics Retention Period

Asif was having trouble updating metrics retention period. Srikanth suggested a fresh install after deletion. Asif successfully resolved his issue after removing all docker resources and recreating everything.

3mo

Troubleshooting Init Container Installation Errors

Pishang encountered installation errors with an init container. They isolated the problem to a network issue within the container and resolved it by modifying DNS nameserver settings. Pranay acknowledged the resolution.