Data Recovery Help

Hi,
I installed seafile server version 11.03 with a rslave propagation mount point to a dedicated host folder on Ubuntu using below docker-compose file:

version: '3'
services:
  db:
    image: mariadb:10.11
    container_name: seafile-mysql
    environment:
      - MYSQL_ROOT_PASSWORD=gwur7qDa  # Requested, set the root's password of MySQL service.
      - MYSQL_LOG_CONSOLE=true
      - MARIADB_AUTO_UPGRADE=1
    volumes:
      - /home2/seafile/db:/var/lib/mysql:rslave  # Requested, specifies the path to MySQL data persistent store.
    networks:
      - seafile-net

  memcached:
    image: memcached:1.6.18
    container_name: seafile-memcached
    entrypoint: memcached -m 256
    networks:
      - seafile-net
  seafile:
    image: seafileltd/seafile-mc:latest
    container_name: seafile
    ports:
      - "80:80"
#     - "443:443"  # If https is enabled, cancel the comment.
    volumes:
      - /home2/seafile/data:/shared:rslave   # Requested, specifies the path to Seafile data persistent store.
    environment:
      - DB_HOST=db
      - DB_ROOT_PASSWD=..# Requested, the value should be root's password of MySQL service.
      - TIME_ZONE=Etc/UTC  # Optional, default is UTC. Should be uncomment and set to your local time zone.
      - SEAFILE_ADMIN_EMAIL=admin@shiny.com # Specifies Seafile admin user, default is 'me@example.com'.
      - SEAFILE_ADMIN_PASSWORD=..     # Specifies Seafile admin password, default is 'asecret'.
      - SEAFILE_SERVER_LETSENCRYPT=false   # Whether to use https or not.
      - SEAFILE_SERVER_HOSTNAME=docs.seafile.com # Specifies your host name if https is enabled.
    depends_on:
      - db
      - memcached
    networks:
      - seafile-net

networks:
  seafile-net:

I used seafile for 3 years without a glitch (version 6.3.4) and was excited when I got the latest version with my files running. Everything was looking great and folders / files have been created within the desired mount-points on the host.
But after a restart of the host I was surprised that the docker compose failed with error:

seafile      | *** Running /etc/my_init.d/01_create_data_links.sh...
seafile      | mv: failed to access '/shared/logs/var-log': Too many levels of symbolic links
seafile      | *** /etc/my_init.d/01_create_data_links.sh failed with status 1
seafile      |
seafile      | *** Killing all processes...

This occurred when starting the same containers used prior. The error would not be a big concern but the mountpoints used on the host do not seem to hold the required data as well. The directory structure is minimal and does not align with the expected volume loaded into seafile.
I think that there is a good chance that the data is still within the docker container but I do require some advise on how I can start the seafile docker container successfully.

Please advise,

Ronny