gitlab-runner 10.5 does no longer have a way for something like --volumes-from=$(hostname)-build since new containers are now preferred

Summary

Many demos and docs had this syntax for passing certain commands between build stages --volumes-from=$(hostname)-build

Newly upgraded functionality does no longer support this "hacky" way of building artifacts (ie run npm install or php composer install from a "tooling" container, which would allow to build all necessary dependencies using various generic building toolkits.

gitlab-runner 10.5 introduced prefer new containers concept in MR !818 (merged) and it completely breaks this dependency.

Obviously we could probably utilize something like cache folders, just a little painful to have to figure out best way to approach the problem when we have hundreds of projects with built-in gitlab-ci custom files that need immediate fixing in order to fix all of our deploy scripts. Are there any recommendations? I couldn't find if this is an optional configurable behavior just yet, but assuming the name was change to PREFER - there's probably consideration for some sort of option to be set in config.toml maybe ?

Steps to reproduce

    - METEOR_RELEASE=$(cat .meteor/release | cut -f2 -d'@')
    - echo "Step 1. Pull most recent version of the builder-image. Detected version - ${METEOR_RELEASE}"
    - docker pull regry.example.com/dockers/meteor:${METEOR_RELEASE}

    - date
    - echo "Step 2. Install NPM modules using meteor's version of NPM"
    - docker run --rm -e NODE_ENV=$NODE_ENV --volumes-from "${HOSTNAME}-build" -w "${CI_PROJECT_DIR}/" regry.example.com/dockers/meteor:${METEOR_RELEASE} bash -c "meteor npm i > ./_build.log 2>&1 || ( EC=$?; cat ./_build.log; exit $EC )"

Actual behavior

fails with error that there's no container with such name, but instead a container with incremental # suffix is created, such as xxxxxx-build-4

Expected behavior

either an optional flag in config.toml or previous behavior for build container is prefered, I imagine many of us had this type of approach utilized in many scripts that we use in produciton

Relevant logs and/or screenshots

Environment description

private runners in omnibus gitlab install

Used GitLab Runner version

10.5.0