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
when using image spec to push an image to the local registry, users need to run envd context create --name flyte-sandbox --builder tcp --builder-address localhost:30003 --use command. it'd be helpful to document this step and provide an explanation of why it is necessary.
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:
Hi @samhita-alla! 👋 I'm Dosu, a friendly bot here to assist you. I'm designed to help with bugs, answer your queries, and guide you on becoming a contributor while we wait for a human maintainer. Let's get started, shall we? 😊
Thank you for your suggestion to improve the Flyte documentation. I agree that it would be beneficial to provide more detailed information about the envd context create --name flyte-sandbox --builder tcp --builder-address localhost:30003 --use command.
Based on the information available in the repository, the --name flyte-sandbox option in the command sets the release name for the helm chart. This release name is used in various places to define names for Kubernetes resources. You can find more details about this in the charts/flyte-sandbox/templates/_helpers.tpl file.
Unfortunately, I couldn't find specific information about how the --builder tcp and --builder-address localhost:30003 options affect the operation of the command, or how the envd context create command interacts with the local registry, either in general or in the context of Flyte.
If you could provide more details about these aspects, it would be helpful in improving the documentation. For example, if you have specific knowledge or experience about how these options work or how the command interacts with the local registry, that would be valuable information to include.
I hope this helps, and I look forward to your response. If you have any other questions or suggestions, please don't hesitate to ask.
Description
when using image spec to push an image to the local registry, users need to run
envd context create --name flyte-sandbox --builder tcp --builder-address localhost:30003 --use
command. it'd be helpful to document this step and provide an explanation of why it is necessary.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: