#4001 [Plugin] FeatRequest - ImageSpec/ENVD allows user to configure backend builder TCP address/ENVD context Issue created by PudgyPigeon When using ImageSpec, flytekit uses ENVD in the background to build out Docker images. Currently, it does not seem like remote buildkitd server/instances are supported in Flytekit by default - nor are users able to affect further configuration options for ENVD contexts. Users can get around this by instantiating a context beforehand, but this requires data scientists to understand ENVD or for platform engineers to abstract away these configurations with internal platform tools. Support for more configuration/the ability to point the default flytekit ENVD context to a remote TCP address/buildkitd server would make using ImageSpec much easier for end-users. Whether this is supported through a pyflyte flag or a configuration field.value in the imagespec.yaml, allowing the user to configure the envd context configs used by Flytekit/pyflyte would be most wonderful. @pingsutw flyteorg/flyte