[BUG] Error: EBUSY: resource busy or locked when using volumes in docker-compose with playwright 1.19.0 and mcr.microsoft.com/playwright:v1.15.0-focal

[Fiona1Man]

Context:

• Playwright Version: 1.19.0
• Operating System: Linux in Docker
• Node.js version: v16.13.2
• Browser: Chromium
• Extra: using volumes in docker-compose
• The issue was not there with versions:
  • 1.16.3 for playwright
  • mcr.microsoft.com/playwright:v1.10.0-focal

Code Snippet
Dockerfile:

FROM mcr.microsoft.com/playwright:v1.15.0-focal

RUN mkdir /app
WORKDIR /app

ENV PATH /app/node_modules/.bin:$PATH

COPY package.json package-lock.json /app/
RUN npm install && npx playwright install

COPY . /app/

in docker-compose.yml:

version: '3'

services:
  app:
    build: .
    command: 'bash'
    tty: true
    volumes:
      - /tmp/e2e-output:/tmp/e2e-output

in playwright.config.ts:

import { PlaywrightTestConfig } from '@playwright/test'

const config: PlaywrightTestConfig = {
  testDir: 'e2e',
  workers: 3,
  outputDir: '/tmp/e2e-output',
  use: {
    headless: false,
    screenshot: 'only-on-failure',
  },
  reporter: [['json'], ['list']],
}

export default config

in package.json:

...
"scripts": {
    "boot": "playwright install",
    "test": "dotenv-flow -- playwright test",
    "browser": "dotenv-flow -- playwright test --headed",
    "format": "eslint --cache --cache-strategy content --fix ."
  },
...

Describe the bug
After building the docker image and run with npm run test inside of docker container,
got this error:

Error: EBUSY: resource busy or locked, rmdir '/app/test-results'

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! mapx-e2e@0.1.0 test: `dotenv-flow -- playwright test "report"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the mapx-e2e@0.1.0 test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2022-02-15T05_02_32_297Z-debug.log

and inside of log, there is nothing useful

[frezot]

Faced same problem when use volume mapping

    volumes:
      - node_modules:/opt/uitests/node_modules

      - './src/:/opt/uitests/src'
      - './screenshots/:/opt/uitests/screenshots'
      - './test-results/:/opt/uitests/test-results'
      - './allure-results/:/opt/uitests/allure-results'
      - './.npmrc:/opt/uitests/.npmrc'
      - './docker-yarn.lock:/opt/uitests/yarn.lock'
      - './package.json:/opt/uitests/package.json'
      - './tsconfig.json:/opt/uitests/tsconfig.json'
      - './playwright.config.ts:/opt/uitests/playwright.config.ts'

volumes:
  node_modules:

It's important for comfortable usage

PW-developers, could you please change rmdir './test-results' on rimraf './test-results/**.*'

[Nav-2d]

I am facing the same issue and getting the following error:

$ playwright test
Running 28 tests using 4 workers
Error: EBUSY: resource busy or locked, rmdir '/app/src/tests/e2e/test-results'

[aslushnikov]

@Nav-2d do you mount a volume as test-results as well?

[Nav-2d]

@aslushnikov - Yes that's correct. Something like this:

docker run --rm --ipc=host --volume /$(pwd)/tests/e2e/test-results:/app/tests/e2e/test-results $IMAGE_TAG

[mzedel]

We also base our testing image on the playwright docker image and mount a folder to keep the test results (seen here)...
The last working tag we used was mcr.microsoft.com/playwright:v1.18.1 - just in case that might narrow down the timeframe the change was introduced...

As a general note: thank you so much for all the work on playwright - our e2e tests have gotten so much more reliable since we made the switch!

[Nav-2d]

@aslushnikov - Apologies I am pinging here again but I was wondering what is the status on this? Our whole org. is kinda stuck from upgrading to 1.19+ and using all the new goodies. We use the same docker volume architecture across all the repos.

As always, thank you for such a great tool!

[aslushnikov]

Yep I can repro. Turns out before 1.19 the test-results folder never actually was removed, so old results were piling in.

As of 2b55ada, we consider failure to clean up test results folder a fatal error. Let me see what we can do here.

[akselikap]

You can get around this issue pretty easily by defining outputDir in playwright.config to something like reports/test-results and then simply mounting the reports dir as a volume.