Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

Hello. We have some engineers hitting permissions issues in Flyte tasks when trying to read/write to data files bundled with the task that seem to be owned by root when the image is built. Are there any best practices (ie. copying files to write) around this or ways to tune this so these files are owned by the flytekit user?

could you elaborate?  which files? the default image does switch the user to be non-root at the end of the dockerfile yeah

I think these are files bundled when pyflyte creates the image. These are bazel runfiles/datafiles that are on the filesystem. Might be an artifact of bazel really

we just started seeing a similar issue in the last hour and are investigating why our mostly recently registered workflows are failing with permissions on root

since we hadn't changed anything related were looking at some things first we don't normally pin (such as flytectl version) but haven't found anything yet

To follow up, I could not figure out tonight _why_ this started occurring out of the blue, but I was able to work around it by adding the `--fast` flag here:
```pyflyte --pkgs $PACKAGES package --fast
flytectl register files -p $PROJECT -d $DOMAIN --archive flyte-package.tgz --version $VERSION```
in our case `pyflyte` is `1.13.5` and `flytectl`  is the latest (`0.9.4`).  Figured I'd add it in case it also helped you.  I know pyflyte deprecated that flag in more recent versions, so maybe its somehow an interaction between pyflyte and flytectl, but I really have no idea.