I uploaded content with Git push on App Service Linux, but the permissions are not inherited. Everything ends up being 777. Do you know the reason?

Thanks for reaching here! As mentioned in this article , For App Service on Linux and Web app for Containers, persistent storage is rooted in /home. When you persist storage with the WEBSITES_ENABLE_APP_SERVICE_STORAGE app setting, we mount a location in Azure Storage to the /home mount point. The permissions on this are 777. You cannot change these permissions, even if you attempt to do so from an initialization script or from SSH. Let us know if further query.

About App Service Content Permissions

Accepted answer

SnehaAgrawal-MSFT 20,856 Reputation points

2022-08-29T16:47:40.783+00:00

Thanks for reaching here!
As mentioned in this article,

For App Service on Linux and Web app for Containers, persistent storage is rooted in /home.

When you persist storage with the WEBSITES_ENABLE_APP_SERVICE_STORAGE app setting, we mount a location in Azure Storage to the /home mount point. The permissions on this are 777.
You cannot change these permissions, even if you attempt to do so from an initialization script or from SSH.

Let us know if further query.
Please sign in to rate this answer.
Noriko 251 Reputation points

2022-08-30T00:16:48.087+00:00

Thank you. If WEBSITES_ENABLE_APP_SERVICE_STORAGE is set to false, permissions can be changed, but they cannot be persisted.
There was no "WEBSITES_ENABLE_APP_SERVICE_STORAGE" setting on the application settings screen, but is it correct that it is set to true by default?

SnehaAgrawal-MSFT 20,856 Reputation points

2022-08-30T14:24:54.397+00:00

Thanks for reply! You cannot do this in standard (built-in) Linux images, and you have to build your own custom container to run on Azure App Service.
For Details on how to Migrate custom software to Azure App Service using a custom container

When persistent storage is disabled, then writes to the /home directory are not persisted across app restarts or across multiple instances.
and when persistent storage is enabled, all writes to the /home directory are persisted and can be accessed by all instances of a scaled-out app.

The absence of this app setting will result in the setting being "true". In other words, if this app setting does not exist in your app, you will see the /home directory mapped to Azure Storage.

The app setting will be missing if you created your app while Web App for Containers was in public preview or if someone has deleted the app setting.

Also, If you set this app setting on an Azure App Service on Linux app using a built-in image, it will have no impact.

Reference: https://learn.microsoft.com/en-gb/archive/blogs/waws/things-you-should-know-web-apps-and-linux#you-can-enable-and-disable-storage-persistence-with-an-app-settingapplies-to-web-app-for-containers

Noriko 251 Reputation points

2022-08-31T11:09:56.277+00:00

Thank you. I would like to start operation with the configuration as it is, but by the permission becoming 777, is there a security risk such as unauthorized access?
Sign in to comment

Share via

About App Service Content Permissions

0 additional answers