Laravel Seeders Give Errors At Random Spots

I am starting to get desperate, I don't know where to look any more. I now also tried MariaDB container and still the same problem. I did notice that when I delete the folder where the DB files are stored in the Linux shell (that folder is mounted using volume:s) the tables are still in the database when the DB is recreated by a new Mysql/Mariadb container at initialization. I tried to not use the volumes: to see if the tables would disappear, they didn't. So somehow my database is persistent even when deleted and relocated... This seems like a problem by it self... Yet I am not sure it is related. Furthermore the a php artisan migrate:reset is successful, the errors are only at seeding time.

I ran the seeder a couple of times, that last time they where succesful (if I run them again I am sure there will be errors). here are the random break points I encountered:

SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (`cake-shop`.`product_product_property`, CONSTRAINT `product_product_property_product_id_foreign` FOREIGN KEY (`product_id`) REFERENCES `product_products` (`id`))

SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (`cake-shop`.`product_prices`, CONSTRAINT `product_prices_product_id_foreign` FOREIGN KEY (`product_id`) REFERENCES `product_products` (`id`))

 SQLSTATE[42S02]: Base table or view not found: 1146 Table 'cake-shop.product_sales' doesn't exist (Connection: mysql, SQL: truncate table `product_sales`)

SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (`cake-shop`.`product_product_properties_property`, CONSTRAINT `product_product_properties_property_product_id_foreign` FOREIGN KEY (`product_id`) REFERENCES `product_products` (`id`))

SQLSTATE[42S02]: Base table or view not found: 1146 Table 'cake-shop.product_product_properties_property' doesn't exist 

And on the next try all seeders finish successfully... To me it feels like a Database issue. Yet having changed DB containers and even switched from Mysql to Mariadb I have no idea what to do anymore... any thoughts on the persisting of the tables (even after actual deletion of the files) would also be more then welcome...

can you please share your Docker-Compose.yml file

ofcourse:

services:
  mysql:
    #image: mysql:8.2.0
    image: mariadb
    environment:
      - MARIADB_ROOT_PASSWORD=test
      - MARIADB_DATABASE=cake-shop
      - MARIADB_USER=test
      - MARIADB_PASSWORD=test
      - MYSQL_ROOT_PASSWORD=test
      - MYSQL_DATABASE=cake-shop
      - MYSQL_USER=test
      - MYSQL_PASSWORD=test
    #entrypoint: ['/bin/sh', '-c', 'sed -i -e "/^skip-name-resolve/d" /etc/mysql/conf.d/docker.cnf && /usr/local/bin/docker-entrypoint.sh mysqld']
    #entrypoint: ['/bin/sh', '-c', 'sed -i -e "/^skip-name-resolve/d" /etc/my.cnf && /usr/local/bin/docker-entrypoint.sh mysqld']
    #entrypoint: ['/bin/sh', '-c', 'sed -i -e "/^skip-name-resolve/d" /etc/mysql/my.cnf && /usr/local/bin/docker-entrypoint.sh mariadbd']
    ports:
      - 3306:3306
    volumes:
      - '/home/cake/cake-shop/Runtime-Environment/tmp_db:/var/lib/mysql'
      - '/home/cake/cake-shop/Runtime-Environment/docker-compose-developers/mysql:/docker-entrypoint-initdb.d'
    networks:
      - cake-shop
    restart: always
    healthcheck:
        test: "/usr/bin/mysql --user=root --password=test --execute \"SHOW DATABASES;\""
        interval: 4s
        timeout: 40s
        retries: 10
  migrationsandtestseeders:
    image: serversideup/php:8.2-fpm-nginx
    volumes:
      - '/home/cake/cake-shop/Database/product:/var/www/html'
    networks:
      - cake-shop
    environment:
      - APP_DEBUG=true
      - DB_HOST=mysql
      - DB_PORT=3306
      - DB_USERNAME=test
      - DB_PASSWORD=test
      - DB_DATABASE=cake-shop
      - APACHE_DOCUMENT_ROOT=/var/www/html/public
    working_dir: /var/www/html
    entrypoint:  ["/bin/sh","-c"]
    command:
      - |
         composer update
         composer install
         cp .env.example .env
         php artisan key:generate
         php artisan config:cache
         php artisan route:cache
         php artisan migrate:reset
         php artisan db:seed
         tail -f /dev/null
    depends_on:
      mysql:
        condition: service_healthy
    links:
      - mysql
    healthcheck:
        test: "php artisan test"
        interval: 2s
        timeout: 20s
        retries: 10
networks:
  cake-shop:
    name: cake-shop.com

The fact that I thought the data returned was because I was working under the assumption that an error during seeding would be a breaking error. As it turns out seeding continues despite and error being thrown. This made that the data was in all the tables when I got an error during truncate().

This leaves performance issues in my mind. Which is strange since it use to work just fine. Thinking that Docker Desktop setting might be the problem.