could someone please help me with executing the task: 1. build the dockerimage and pushed to

flyte-sandbox-docker-registry

which is running on port 30000. 2. execute the

pyflyte run --remote --inmage host:30000/<img> <.py> wf

3. Seeing error on dashboard

http:server gave HTTP response to HTTPS client

Could someone please guide me with exact step to fix this issue with

flyte demo cluster

looking

this command throws me

flag provided but not defined: -builder

which version of envd you are using?

pip show envd

version 0.3.5

too old, try to use 0.3.45

sorry 0.3.45

hmm, I’m using 0.3.45 as well

I delete the virtual env and tried once again

nice!

next step shall I do pyflyte run ?

yes

but I have pushed my image already in localhost:30000 image registry but this time getting error in task

3/13/2024 121955 PM UTC [ContainersNotReady|ErrImagePull]: containers with unready status: [f119dfe8b5080445e83d-n0-0]|rpc error: code = Unknown desc = failed to pull and unpack image "192.168.180.8130000/samplev1.0": failed to resolve reference "192.168.180.8130000/samplev1.0": failed to do request: Head "https://192.168.180.81:30000/v2/sample/manifests/v1.0": http: server gave HTTP response to HTTPS client

could you show me your imageSpec definition?

sorry If i am confusing you, as a first approach I tried with imagespec which dint work for me. So I have taken second approach where I build the image for dockerfile and pushed to localhost:30000 (flyte-sandbox-docker-registry)

ah, i see

yes I am able to pull in host machine after adding insecure registry in / etc/docker/`daemon.sh` but within flyte demo cluster i think some configuration is needed to pull the image while running the task

seems like a bug, mind creating an issue for it. [flyte-bug]

🐞 Create a new Flyte Bug issue: https://github.com/flyteorg/flyte/issues/new?assignees=&labels=bug%2Cuntriaged&template=bug_report.yaml&title=%5BBUG%5D+

I can test the sandbox tomorrow morning

sure, I will do it. thank you

could you try to use imageSpec(registry=“localhost:30000”) instead of using the image you pushed

okay first I will build image using envd

yes, thanks! because I think imageSpec should work

in imagespec registry i will add localhost:30000 right

yes

$pyflyte build example.py wf

throws error : Builder None is not registered but I can see in

envd context ls

sandbox context is set

you need to install envd plugin btw.

pip install flytekitplugins-envd

It worked !!!!!

awesome 🎉

thank you very much

but pushing your prebuilt image should work as well, don’t know what’s happening

i feel k3s need to be configured to pull image from insecured registry

maybe, need to investigate

sure

thank you!

but 30003 is not exposed in

kubectl get svc

it’s not running in the pod

ohh this I dint knew

okok