Thomas Blom
02/03/2023, 2:53 AM--fast
in conjunction with --image
to do a fast register of local code that will be "overlayed" onto to the specified image (as I understand it). But in my trials I find that:
1. --fast is not a recognized option, eventually realized it is a command (without dashes), are the docs are wrong?
2. Then it complains "No such option --image". Again, are docs are wrong? Or I'm misreading something.
I was trying to modify a command that works without "fast" into one that runs with "fast" to see if I can avoid building and pushing a new image (the image I specify in this case already exists). The command looks like this, where I've inserted $FAST_REG into a command that otherwise works to serialize against a given image:
pyflyte --pkgs plaster.genv2 serialize $FAST_REG --image <my-ecr-registry-path>/<my-image-name>:<tag> --local-source-root . workflows -f /tmp/_pb_outputs
...where the $FAST_REG is where I'm attempting to insert "fast" and run my local code overlayed with what is in the image I'm specifying. I'm probably misunderstanding something, and the docs aren't helping me.
Thanks for any tips!Ketan (kumare3)
Thomas Blom
02/03/2023, 3:03 AMKetan (kumare3)
Thomas Blom
02/03/2023, 3:06 AMKetan (kumare3)
Alireza
02/03/2023, 3:10 AM-i
then image parameters?Thomas Blom
02/03/2023, 3:18 AMAlireza
02/03/2023, 3:40 AMKetan (kumare3)
--fast
but hte command should look more like
pyflyte serialize fast workflows
The docs are using the more preferred command
pyflyte package
pyflyte register
you do not need to pyflyte package/serialize
at all for registerpyflyte package
-> flytectl register
Samhita Alla
Thomas Blom
02/03/2023, 2:44 PMNiels Bantilan
02/03/2023, 3:05 PMpyflyte serialize
is an old CLI command: pyflyte package
is the recommended way of getting a portable zip file of flyte tasks/workflows at this point/Jimmy Du
02/08/2023, 12:42 AMpyflyte register
or pyflyte package + flytectl register
, does the docker image need to contain the actual workflow/task definition logic?
The existing Dockerfile generated by pyflyte init
has code to copy the workflow/task logic, which seems to imply that the workflow/task logic should be in the Docker image, but from the discussion in this thread and some of the documentation, it doesn't seem like this copy is necessary. Are there benefits to copying the code into the Docker image (would there be lower latency/steps skipped)?
Logic in Dockerfile that copies workflow/task code:
# Copy the actual code
COPY . /root
Ketan (kumare3)
/root
is that code is copied there in a default “regular” register flowJimmy Du
02/08/2023, 1:18 AM