Analyze feature proposal for allowing volume mounts for services and build containers
Overview
Analyze the proposal in the Allow volume mounts to be configured on a job level for services and build containers issue. The goal of the analysis is the following:
-
-
Verify that is the right approach to address the various problems related to uses needing to be able to configure volume mounts for job service container. The related issues are:
- Allow volume mounts to be configured on a job l... (#28121) • Unassigned • 17.4
- Configure docker volumes in .gitlab-ci.yml (#3207) • Unassigned • Backlog
- Feature request: Allow to define entry points a... (#1525) • Unassigned • Backlog
- Introduce relative entrypoints and start servic... (#3210) • Unassigned • Backlog
- Add volumes-from option to .gitlab-ci.yml (gitlab#15840) • Unassigned • Backlog
-
-
- Determine if there are any risks from a security perspective as a result of implementing this proposal.
Problems to solve
- To address various use cases GitLab CI users need to leverage Docker volumes for getting data into services containers. The options available today are limited to the runner owner adding the volumes configuration to the runner's
config.toml
. With this approach, the volume applies to all services and CI job (build) containers. There is no flexibility on a per job basis.
Requirements
- Users need the ability to define volumes for services.
- Users need the ability for services to share volumes.
Edited by Darren Eastman