@ancient-wolf-19325

flytectl demo start

command fails with below error:

Error response from daemon: driver failed programming external connectivity on endpoint flyte-sandbox 
 Bind for 0.0.0.0:30000 failed: port is already allocated

I have "kind" cluster which uses port 30000. Is it possible to configure flytectl demo cluster to use some other port instead of 30000?

Yes, it is possible to configure the

flytectl demo

cluster to use a different port. You can modify the port configuration in the

config.yaml

file or by changing the Dockerfile and Flyte repository settings. According to this discussion, you can change the port by updating the

flyte.yaml

configuration file and the Dockerfile. Here are the steps: 1. Clone the Flyte repository:

git clone https://github.com/flyteorg/flyte.git
   cd flyte

2. Modify the

flyte.yaml

file: Change the

httpPort

configuration from

30000

to your desired port. 3. Update the Dockerfile: Change the port in the Dockerfile to expose the new port instead of

30000

. 4. Build the Docker image:

docker build -t custom-flyte-image --file docker/sandbox-lite/Dockerfile .

5. Start the demo cluster with the new image:

flytectl demo start --image custom-flyte-image

Would you like more detailed steps on how to modify the Flyte repository and Dockerfile to use a custom port? Sources: - How should I run the demo cluster if I want to have the flyt - Flytectl Feature: flytectl demo cluster - configurable port number 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.