Notes on FF_DISABLE_UMASK_FOR_DOCKER_EXECUTOR usage

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Label this issue

In some cases, it is helpful to set the feature flag FF_DISABLE_UMASK_FOR_DOCKER_EXECUTOR to 1. If you set this flag before running any jobs, you are good to go.

If you run jobs and then learn that you need to set FF_DISABLE_UMASK_FOR_DOCKER_EXECUTOR to solve the permissions/ownership problem that you are encountering, it may not be enough to simply set the flag. Additional actions may need to be taken in order to update the cached directories that are used. By default, GIT_STRATEGY is set to fetch.

You can do one of two things:

• Run the job once with GIT_STRATEGY set to clone (useful if you don't have access to the Runner host)
• Remove the client directory in use by docker (only useful if you shell access to the Runner host)

Hello @bcarranza; I made this for you!

Ticket: 185763

Agent: Brie Carranza