Skip to content
GitLab Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Menu
    Projects Groups Snippets
  • Get a free trial
  • Sign up
  • Login
  • Sign in / Register
  • gitlab-runner gitlab-runner
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 2,409
    • Issues 2,409
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 130
    • Merge requests 130
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

GitLab 15.0 has launched! Please visit Breaking changes in 15.0 and 15.0 Removals to see which breaking changes may impact your workflow.

  • GitLab.org
  • gitlab-runnergitlab-runner
  • Issues
  • #6581
Closed
Open
Created Feb 05, 2020 by Steve Azzopardi@steveazzMaintainer

Remove FF_USE_LEGACY_VOLUMES_MOUNTING_ORDER feature flag

Overview

In !1352 (merged) we fixed a small regression where the user-defined volumes for the Docker executor are added to the service container. This caused some breaking changes #4260 (closed). We added FF_USE_LEGACY_VOLUMES_MOUNTING_ORDER which allowed the user to use the old behavior where the volume is not mounted to the service container.

Proposal

Remove FF_USE_LEGACY_VOLUMES_MOUNTING_ORDER and have the volume be mounted to the service all the time (which is the default behavior right now)

Assignee
Assign to
Time tracking