sparse-window-1536
03/11/2022, 6:43 PMtest_google_cloud
, but the system won't find it: if I try to run it, I'm met with the error AttributeError: module 'src.flyte.tasks' has no attribute 'test_google_cloud'
. I ran docker build
again, serialized the tasks again, registered them again, and still nothing. The task is registered, since I can see it on the UI, but the worker can't find it. What is happening?freezing-airport-6809
/root
freezing-airport-6809
pyflyte package --in-container-source-path /…
freezing-airport-6809
src.flyte.tasks
right?freezing-airport-6809
working
directory the function should be loadablesparse-window-1536
03/11/2022, 7:13 PM-d
option and the error persists. Before, it was just a Forbidden
error coming from trying to copy the file to /root
. Now, this appears:
flytekit.exceptions.user.FlyteAssertion: Failed to get data from <s3://my-s3-bucket/fast/v3-fastb17df494435c35acc740957bbca00389.tar.gz> to /home/flyte/app (recursive=False).
Original exception: Called process exited with error code: 1. Stderr dump:
b'fatal error: An error occurred (403) when calling the HeadObject operation: Forbidden\n'
The root of the source code is /home/flyte/app
sparse-window-1536
03/11/2022, 7:15 PMsrc.flyte.tasks
is right. It deleted the sandbox and started from scratch, and now the task can be executed. It seems that the problem happens when I create new tasks after the first build/serializationsparse-window-1536
03/11/2022, 7:15 PMhallowed-translator-36253
sparse-window-1536
03/25/2022, 3:19 PMchown
argument when copying the directory to the container (COPY --chown=flyte:flyte src/ /home/flyte/src
on the Dockerfile, for a non-root user flyte
)
• Passing the --in-container-source-path
when (fast) registering the tasks (--in-container-source-path /home/flyte
in my case)