Docker-compose up is not starting zeebe in windows 10 Linux sub-system

docker desktop is up and runing.

:~/zeebe-docker-compose/operate$ docker-compose up
Starting operate_operate_1 … error Starting operate_elasticsearch_1 …
Starting operate_kibana_1 …

ERROR: for operate_operate_1 Cannot start service operate: OCI runtime create failed: container_linux.go:346: starting container process caused “process_linux.go:449: container init caused “rootfs_linux.go:58: mounting \”/home/amitesh/zeebe-docker-compose/lib/application.yml\” to rootfs \"/var/lib/docker/overlay2/8b3c1239a127237b8bdefa5603ab56359aa33af4c23b9fe7eadfb42c11738fd3/merged\" at \"/var/lib/docker/overlay2/8b3c1239a127237b8bdefa5603ab56359aa33af4c23b9fe7eadfb42c11738fd3/merged/uStarting operate_elasticsearch_1 … done Starting operate_kibana_1 … done Starting operate_zeebe_1 … error
ERROR: for operate_zeebe_1 Cannot start service zeebe: OCI runtime create failed: container_linux.go:346: starting container process caused “process_linux.go:449: container init caused “rootfs_linux.go:58: mounting \”/home/amitesh/zeebe-docker-compose/operate/zeebe.cfg.toml\” to rootfs \"/var/lib/docker/overlay2/de1ae71be8a9a373fb13416e3d7e3fe87c36ef8cb64bbd501bb0fd5ac23e019f/merged\" at \"/var/lib/docker/overlay2/de1ae71be8a9a373fb13416e3d7e3fe87c36ef8cb64bbd501bb0fd5ac23e019f/merged/usr/local/zeebe/conf/zeebe.cfg.toml\" caused \“not a directory\”"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

ERROR: for zeebe Cannot start service zeebe: OCI runtime create failed: container_linux.go:346: starting container process caused “process_linux.go:449: container init caused “rootfs_linux.go:58: mounting \”/home/amitesh/zeebe-docker-compose/operate/zeebe.cfg.toml\” to rootfs \"/var/lib/docker/overlay2/de1ae71be8a9a373fb13416e3d7e3fe87c36ef8cb64bbd501bb0fd5ac23e019f/merged\" at \"/var/lib/docker/overlay2/de1ae71be8a9a373fb13416e3d7e3fe87c36ef8cb64bbd501bb0fd5ac23e019f/merged/usr/local/zeebe/conf/zeebe.cfg.toml\" caused \“not a directory\”"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

ERROR: for operate Cannot start service operate: OCI runtime create failed: container_linux.go:346: starting container process caused “process_linux.go:449: container init caused “rootfs_linux.go:58: mounting \”/home/amitesh/zeebe-docker-compose/lib/application.yml\” to rootfs \"/var/lib/docker/overlay2/8b3c1239a127237b8bdefa5603ab56359aa33af4c23b9fe7eadfb42c11738fd3/merged\" at \"/var/lib/docker/overlay2/8b3c1239a127237b8bdefa5603ab56359aa33af4c23b9fe7eadfb42c11738fd3/merged/usr/local/operate/config/application.yml\" caused \“not a directory\”"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
ERROR: Encountered errors while bringing up the project.

@Jango12345
“”/home/amitesh/zeebe-docker-compose/lib/application.yml\” to rootfs “/var/lib/docker/overlay2/8b3c1239a127237b8bdefa5603ab56359aa33af4c23b9fe7eadfb42c11738fd3/merged” at “/var/lib/docker/overlay2/8b3c1239a127237b8bdefa5603ab56359aa33af4c23b9fe7eadfb42c11738fd3/merged/usr/local/operate/config/application.yml” caused \“not a directory\””": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type"
does that error mean something to you? Did you changed the configuration of the docker-compose file?
There is something wrong in there for sure… Zeebe Operate container is trying to mount a directory and you are pointing to a file…

Could be this or related: https://medium.com/@Charles_Stover/fixing-volumes-in-docker-toolbox-4ad5ace0e572

See also here: Docker compose operate error