Django + SQLite3 in Docker - Database automatically rolled back to initial state after new Docker build and start

I have a Django project which uses SQLite3 database running in Docker container.

Dockerfile:

# Base image
FROM python:3.10-slim-buster
# Set working directory
WORKDIR /app
# Copy the entire project directory
COPY . /app
# Install project dependencies
RUN pip install -r requirements_dev.txt
# Expose port
EXPOSE 8000
# Run the development server
CMD ["python", "doc_manager/manage.py", "runserver", "0.0.0.0:8000"]

docker-compose.yml:

version: '3'
services:
  web:
    build:
      context: .
      dockerfile: Dockerfile
    ports:
      - "8000:8000"
    volumes:
      - ./:/app/doc-manager-web

When I want to build/deploy new version in this set-up, I execute these 2 commands:

docker compose build
docker compose up

Both commands are successfully executed.

But, consider this use case:

1. I deploy the current version using the given set-up.
2. I perform some modifications in the database (CRUD operations). The database is now modified.
3. I then perform some changes in the code itself (not in the Dockerfile or in docker-compose.yml).
4. I re-run the docker compose build and docker compose up commands.

Then, I end up with the initial state of the database without the modifications I performed in step number 2.

How do I make sure that my SQLite3 database keeps it's modifications regardless of the code modifications I'll do in the future and regardless of how many times I re-build, stop and start again the whole Docker environment?

My SQLite3 database lives in the project's directory.

EDIT:
This is the folder structure of my Django project after putting the SQLite3 database file in the data/ folder.

└───doc_manager  # Main Django project folder
    ├───core  # Django app
    │   ├───migrations
    │   │   └───__pycache__
    │   ├───templates
    │   │   └───core
    │   └───__pycache__
    ├───data
    │   └───db.sqlite3  # The SQLite3 db file that is used in Django
    └───doc_manager

The SQLite database file is stored within the project directory, which gets overwritten each time you rebuild the Docker container.
Here's an updated Dockerfile and docker-compose.yml configuration to achieve this:

# Base image
FROM python:3.10-slim-buster
# Set working directory
WORKDIR /app
# Copy the entire project directory
COPY . /app
# Install project dependencies
RUN pip install -r requirements_dev.txt
# Run the development server
CMD ["python", "doc_manager/manage.py", "runserver", "0.0.0.0:8000"]

docker-compose.yml:

version: '3'
services:
  web:
    build:
      context: .
      dockerfile: Dockerfile
    ports:
      - "8000:8000"
    volumes:
      - db-data:/app/doc_manager/data
volumes:
  db-data: