/var/lib/docker/overlay2/ gets bigger and bigger because of playwright-chrome

[akn01]

I only monitor three websites at intervals of 1.5 minutes. I have noticed that the /var/lib/docker/overlay2/ folder is constantly growing. Several GB of data accumulate in a single day. These are likely temporary files from playwright-chrome.

How can this be prevented?

Here is my docker-compose.yml file:

services:
  changedetection:
    image: ghcr.io/dgtlmoon/changedetection.io
    container_name: changedetection
    hostname: changedetection
    volumes:
      - changedetection-data:/datastore
    environment:
      - PLAYWRIGHT_DRIVER_URL=ws://browser-sockpuppet-chrome:3000
      - FETCH_WORKERS=1
      - MAX_SNAPSHOTS=5
    ports:
      - 5000:5000
    depends_on:
      browser-sockpuppet-chrome:
        condition: service_started
    restart: unless-stopped

  browser-sockpuppet-chrome:
    hostname: browser-sockpuppet-chrome
    image: dgtlmoon/sockpuppetbrowser:latest
    cap_add:
      - SYS_ADMIN
    restart: unless-stopped
    environment:
      - SCREEN_WIDTH=1920
      - SCREEN_HEIGHT=1024
      - SCREEN_DEPTH=16
      - MAX_CONCURRENT_CHROME_PROCESSES=1

volumes:
  changedetection-data:

As a workaround, I'm using a crontab script that stops and removes the Docker containers, cleans up unused resources, pulls the latest images, and then restarts the containers with the updated images, but this cannot be the long-term solution, as it doesn't address the root cause of the growing overlay2 storage issue.

Addendum: I have now discovered that core dumps are likely the cause. These are memory dumps from crashed processes. There are large files with names such as core.271, for example.

Addendum: To address this, I added the following to the browser-sockpuppet-chrome container configuration:

ulimits:
  core: 0

This setting disables core dumps for the container processes and prevents large space-consuming files from being written.

[mgrimace]

Thanks for this, I did this on a bare-metal (helper script) installation via:

• sudo systemctl edit changedetection.service
• add:

### Editing /etc/systemd/system/changedetection.service.d/override.conf
### Anything between here and the comment below will become the new contents of the file

[Service]
LimitCORE=0

### Lines below this comment will be discarded

• Save, exit, and restart services:

sudo systemctl daemon-reexec
sudo systemctl daemon-reload
sudo systemctl restart changedetection

• Then, the repeated same process for browserless.service via systemctl edit browserless.service

I'm hoping this will help the size creep of changedetection

[dgtlmoon]

If you look at the docker volumes it can show you what exactly changed in that volume

can you list that data?