go-vela
Workspace Access for Alternative Docker Users
Description
Currently if you run a container as a non-root user, that user does not have write access to the workspace where the git repository is cloned. In the specific case I'm targeting, that creates issues when I try to build a python package it runs into issues create the corresponding artifacts. There are of course workaround to achieve what I want, but they are less than ideal and add complexity. If there was a simple way to grant the docker user write access to the workspace, that would be much preferred.
Value
The main value is to allow artifacts to reside in the same directory as the workspace. That's how it works when running the container as root, ideally the same would apply if using a non-root user.
Definition of Done
A container running as a non-root user is able to write a file to the workspace.
