You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
kudulite build paths for Elastic Premium function apps take excessively long causing builds to crash. This is caused because the shared home directory in Elastic Premium containers are powered by Azure Files and during build, kudulite build process uses the /home directory for storing logs, caching packages etc.
We can make several improvements in this build process, by work-arounds like changing the default caching location for Python builds, storing logs temporarily in local disk and then moving over to home. More details TBD.
The text was updated successfully, but these errors were encountered:
The work-around for the time-being can be (assuming storage is in the same region as EP plan) --
App an App Setting XDG_CACHE_HOME to point to /tmp/.cache (or other local dir). This will make pip cache everything there instead of the shared home dir.
Do not poll logs for EP sku builds, and use /api/isdeploying as the truth.
Maybe instead of 1, we could set that Environment var in kudulite if sku is EP. But changing the client is simpler at the moment.
With this, we should be unblocked to successfully do builds. But, we should still think of an actual fix and try to get it done soon. That fix would help improve build times even more.
kudulite build paths for Elastic Premium function apps take excessively long causing builds to crash. This is caused because the shared home directory in Elastic Premium containers are powered by Azure Files and during build, kudulite build process uses the /home directory for storing logs, caching packages etc.
We can make several improvements in this build process, by work-arounds like changing the default caching location for Python builds, storing logs temporarily in local disk and then moving over to home. More details TBD.
The text was updated successfully, but these errors were encountered: