You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since we've updated Flyteconsole, we're unable to set the port we want. We found that this had become hardcoded into flyteconsole with the recent changes.
Expected behavior
We should be able to pick the port we want by setting the PORT env variable.
Additional context to reproduce
Set the PORT env to other than 8080 and run the docker image. It will always use 8080
Screenshots
No response
Are you sure this issue hasn't been raised already?
Yes
Have you read the Code of Conduct?
Yes
The text was updated successfully, but these errors were encountered:
To address the issue of the hardcoded port in Flyteconsole, it's important to note that the demo cluster's UI port is hardcoded to 30080, as discussed in the forum. This behavior is due to the message in the command line being hardcoded, even though the actual port configuration might be different. For a custom port configuration, changes in the Flyte repository and Dockerfile are necessary, as detailed in the same discussion.
Would you like more detailed steps on how to modify the Flyte repository and Dockerfile to use a custom port?
Describe the bug
Since we've updated Flyteconsole, we're unable to set the port we want. We found that this had become hardcoded into flyteconsole with the recent changes.
Expected behavior
We should be able to pick the port we want by setting the
PORT
env variable.Additional context to reproduce
Set the
PORT
env to other than 8080 and run the docker image. It will always use8080
Screenshots
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: