New RunLLM response generated: >>>*# Question* Hi community, I want to know how to use

http

image registry for flytepluing-envd? When I use

http

url in image registry, I will get

#22 ERROR: failed to do request: Head "<https://test-1797217457.ap-northeast-1.elb.amazonaws.com:5000/v2/split_imag/blobs/sha256:056025e5e2a8242cc32ad6af915817cfc4f5dc4fbgr1604585b1e767re13c9>": http: server gave HTTP response to HTTPS client

# Answer To use an

http

image registry with

flytekitplugins-envd

, you need to ensure that the registry is correctly configured to accept HTTP requests. The error you're encountering indicates that the server is giving an HTTP response to an HTTPS client, which suggests a mismatch in the expected protocol. According to this discussion, you can configure the

envd

context to use HTTP by specifying the correct builder address and ensuring the registry is set up to handle HTTP requests. Here is a step-by-step guide: 1. Install

flytekitplugins-envd

:

pip install flytekitplugins-envd

2. Create an

envd

context:

envd context create --name flyte-sandbox --builder tcp --builder-address localhost:30003 --use

3. Define your

ImageSpec

with the HTTP registry:

from flytekit import ImageSpec

    pandas_image_spec = ImageSpec(
        base_image="ghcr.io/flyteorg/flytekit:py3.8-1.6.2",
        packages=["pandas", "numpy"],
        registry="http://localhost:30000"
    )

4. Ensure your local registry is running and accessible via HTTP. You might need to configure your Docker registry to accept HTTP connections. This can typically be done by modifying the Docker daemon configuration to allow insecure registries. 5. Run your Flyte tasks and workflows using the defined

ImageSpec

. If you continue to face issues, ensure that the registry URL is correctly formatted and that the registry is properly configured to handle HTTP requests. Would you like more detailed steps or further assistance? Sources: - this discussion Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1724720168.694519 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.