Hey, everyone! I'm kinda confused on how to use custom images on a sandbox with Flyte 1.x.x. At first I thought the sandbox would pull the image from my local repository, but this doesn't seem to be the case, since I'm receiving the error
containers with unready status: [ash8dlh4m294mnd9psbs-f62iya2y-0]|Back-off pulling image "flyte-example:1.0"
when trying to execute a workflow, even though I have the flyte-example:1.0 image on my local repo. But, at the same time, it doesn't seem like I should have to build the image inside the sandbox container, right? The container from
flytectl demo start
doesn't even mount the working directory into
.I can't find anything in the documentation that says how to do this...
4 months ago
if you do
flytectl demo start --source .
your working directory will be mounted onto the demo cluster container, and you can use
flytectl demo exec docker build /root --tag …
to build the custom container from within the demo container
@Marc Paquette@Smriti Satyan@Samhita Alla@Alekhya friendly ping to make sure we make an issue to document this [create new docs issue]
and yeah that is correct… there are two daemons weirdly.
would be great if the registry was shared at least but that was difficult to do.
4 months ago
yes currently we couldn’t find a way to share the registry within another child container process. If you find a way we would love to have this contribution as it would make it even more simpler.Heres another way i do if i am serializing core examples from cookbook which builds the image in the demo container registry.
flytectl demo start --source ~/flytesnacks/cookbook/
flytectl demo exec -- make -C core/ serialize
flytectl register file ~/flytesnacks/cookbook/core/_pb_output/* -d development -p flytesnacks --version v1
flytectl get launchplan -p flytesnacks -d development core.flyte_basics.lp.go_greet --latest --execFile execFile.yaml
flytectl create execution -p flytesnacks -d development --execFile execFile.yaml