make "flyte start devbox" support custom ports

[aliisayev008gemini-cloud]

Basically the title, right now I cannot specify custom ports for the devbox deployment.

--help flag gave me the following options:

│ --image TEXT Docker image to use for the devbox cluster.
│ [default: (cr.flyte.org/flyteorg/flyte-devbox:latest
│ (cr.flyte.org/flyteorg/flyte-devbox:gpu-latest when --gpu))]
│ --dev Enable dev mode inside the devbox cluster (sets FLYTE_DEV=True).
│ --gpu Pass host GPUs into the devbox container (adds --gpus all to docker run).
│ Requires an NVIDIA-enabled host. Defaults --image to a GPU-capable image if
│ --image is not explicitly set.
│ --help Show this message and exit.

Is there any way to customize the ports?

[runllm]

There is currently no documented or supported way to specify custom ports for the devbox deployment using the flyte start devbox command. The available CLI options are --image, --dev, --gpu, and --help; none allow port customization. The ports used are hardcoded in the implementation and not exposed as configurable CLI parameters according to the official documentation and source code (Flyte CLI reference, devbox source code).

Would you like more detail on how the ports are set internally or possible workarounds?

Sources:

• Flyte CLI reference
• devbox source code

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!

[aliisayev008gemini-cloud]

@RunLLM suggested workarounds

[runllm]

There is no officially supported way to customize ports via the flyte start devbox CLI. The ports are hardcoded in the source code and not exposed as CLI options (devbox source code, Flyte CLI reference).

Possible workarounds include: (1) modifying the source code to change the _PORTS list before building and running your own version of the CLI, or (2) using Docker port mapping or network tools to remap ports after the container is started, though this may require stopping the default container and running your own with custom docker run parameters. These approaches are not officially documented or supported.

Would you like step-by-step guidance on either of these workarounds?

Sources:

• devbox source code
• Flyte CLI reference

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!

[muskan-creates352]

Hi, I would like to work on this issue.
I’m planning to add support for custom port mappings in flyte start devbox by introducing a CLI option and making the Docker port configuration dynamic while preserving the current default behavior.

Please let me know if there are any implementation preferences or related discussions I should be aware of before starting. Thanks!