Subql-starter’s docker-compose.yml can't run project properly report

[Index0011]

The default configures of subquery can not run properly in one’s own env. When I create a new project on my own env, the default docker-compose.yml file can not start the project properly. Maybe we can update the relatedd subql config?
here is the error logs when using default docker-compose-yaml:
......
Pulling postgres ... done
Pulling subquery-node ... done
Pulling graphql-engine ... done
Starting phala-world-subquery_postgres_1 ... done
phala-world-subquery_subquery-node_1 is up-to-date

ERROR: for graphql-engine Container "fbc5cb307514" is unhealthy.
ERROR: Encountered errors while bringing up the project.

[AtelyPham]

Hi team!

I'm facing the same error as above.

I'm trying to run SubQuery project locally (using yarn start:docker) and connect with my custom node (currently my node is running locally). But the SubQuery output said my graphql-engine is unhealthy. The log of my subquery-node container show connection failed (I attached 2 screenshots below).

Do you have any idea to debug or fix it? Thank you 🙏

Screenshots:

[AtelyPham]

Also found this issue #189.

I updated my docker-compose.yml and project.yaml accordingly:

docker-compose.yml

version: '3'

services:
	  postgres:
		# ...
	
	  subquery-node:
		# ...
	    environment:
	      NETWORK_ENDPOINT: ws://${DOCKER_GATEWAY_HOST:-host.docker.internal}:9944

	  graphql-engine:
		# ...
	    environment:
	      NETWORK_ENDPOINT: ws://${DOCKER_GATEWAY_HOST:-host.docker.internal}:9944
		

project.yaml

network:
	endpoint: ${NETWORK_ENDPOINT}

But the behaviour is still the same, connection_failed.

[AtelyPham]

Dup #1220

[stwiname]

This should be fixed with 1.6.1