"docker compose up" fails

[pazz]

Have you checked that your issue isn't already filed?

• I read through FAQ and searched through the past issues, none of which addressed my issue.
• Yes, I have checked that this issue isn't already filed.

Bug description

The "recommended Approach" for local development fails

How to reproduce the bug

I am following the instructions under "Recommended Approach" in INSTALL.md but docker compose up fails on me.

Side-question: I used to just use the system-wide ruby environment and bundle exec jekyll serve as described in the jekyll docks. How come this theme became so demanding? (genuine question, not meant as a complaint). Is there a reason to keep the Gemfile.lock around? I noticed that when I deploy on our own gitlab server and build in CI, the build (using the dockre image provided here) fails unless I remove this file from the source first.

Error messages and logs

[~/website] bundle install          
[~/website] docker compose up
[+] Running 1/1
 ✔ Container website-jekyll-1  Recreated1.4s 
Attaching to jekyll-1
jekyll-1  | Entry point script running
jekyll-1  | fatal: not a git repository: /srv/jekyll/../.git/modules/website
jekyll-1 exited with code 128

What operating system are you using?

Linux

Where are you seeing the problem on?

Running locally with Docker (docker compose)

More info

This is on debian testing, docker just re-installed from the official repository:

Docker version 27.4.1, build b9d17ea