[Bug] IPFS block data is consuming 80% of the storage space

Bug report

I'm currently hosting my own graph-node on AWS EC2, and I've noticed that the IPFS block files are growing incredibly fast, taking up about 100 GB at the moment (while PostgreSQL is using only 28 GB). It seems like the graph-node is just seeding for the IPFS network, and I'd like to figure out how to stop that.

This is mydocker-compose.yml.

version: '3'
services:
  graph-node:
    image: graphprotocol/graph-node
    ports:
      - '8000:8000'
      - '8001:8001'
      - '8020:8020'
      - '8030:8030'
      - '8040:8040'
    depends_on:
      - ipfs
      - postgres
    extra_hosts:
      - host.docker.internal:host-gateway
    environment:
      postgres_host: postgres
      postgres_user: graph-node
      postgres_pass: ****
      postgres_db: graph-node
      ipfs: 'ipfs:5001'
      ethereum: 'mainnet:https://root.rootnet.live/'
      GRAPH_LOG: info
  ipfs:
    image: ipfs/kubo:v0.14.0
    ports:
      - '5001:5001'
    volumes:
      - ./data/ipfs:/data/ipfs
  postgres:
    image: postgres:14
    ports:
      - '5432:5432'
    command:
      [
        "postgres",
        "-cshared_preload_libraries=pg_stat_statements",
        "-cmax_connections=200"
      ]
    environment:
      POSTGRES_USER: graph-node
      POSTGRES_PASSWORD: ****
      POSTGRES_DB: graph-node
      # FIXME: remove this env. var. which we shouldn't need. Introduced by
      # <https://github.com/graphprotocol/graph-node/pull/3511>, maybe as a
      # workaround for https://github.com/docker/for-mac/issues/6270?
      PGDATA: "/var/lib/postgresql/data"
      POSTGRES_INITDB_ARGS: "-E UTF8 --locale=C"
    volumes:
      - ./data/postgres:/var/lib/postgresql/data

Relevant log output

No response

IPFS hash

No response

Subgraph name or link to explorer

No response

Some information to help us out

• Tick this box if this bug is caused by a regression found in the latest release.
• Tick this box if this bug is specific to the hosted service.
• I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

Linux

Iniziare dal docker-compose.yml fornito, in particolare dal servizio ipfs, dalla relativa immagine Kubo e dal volume ./data/ipfs. Tracciare il modo in cui graph-node utilizza quell'endpoint IPFS e determinare se la configurazione supportata può impedire una crescita illimitata dei blocchi senza interrompere il recupero dei contenuti richiesti; il lavoro è completo quando è stata documentata o implementata una mitigazione verificata, insieme ai relativi compromessi di archiviazione.