dependency failed to start: container crapi-workshop exited

Describe the bug
After running "docker compose -f docker-compose.yml --compatibility up -d" I receive the error: dependency failed to start: container crapi-workshop exited (0)

To Reproduce
Steps to reproduce the behavior.

1. Use the commands listed on github:
   (curl -o docker-compose.yml https://raw.githubusercontent.com/OWASP/crAPI/main/deploy/docker/docker- compose.yml
   docker compose pull
   docker compose -f docker-compose.yml --compatibility up -d) with Network of the VM set to NAT. Behaviour of crapi: all containers start and no errors are received.
2. Shutdown the VM, change Network to internal network, and start VM. Use the last command and you'll receive the error.

Expected behavior
All containers should start.

Runtime Environment
Sytem/Environemnt information (e.g Output of docker -v and uname -a)
-Debian 11 running in VirtualBox 7
-Network of VM changed from the default NAT to Internal Network
-Docker Engine - Community Version: 23.0.1
-Docker Compose version v2.16.0
crapi-workshop log.txt

Start with docker-compose.yml and the attached crapi-workshop.log.txt, then reproduce the final docker compose command on Debian 11 in a VirtualBox VM using an Internal Network. Compare this run with NAT and inspect which dependency exits. Done means all containers start successfully in the reported network configuration.