Subql-node v1.6.0 and v1.5.2-4 docker broken

[wpank]

Prerequisites

• Are you running the latest version(s)?
• Did you check the debugging guide?
• Did you check the FAQs and Discussions?
• Are you reporting to the correct repository?
• Did you search for an existing issue or pull request?

Description

I'm working on some indexing for Polkadot staking extrinsics, and yesterday everything was working fine. I try it again today (without changing any code) and get:

❯ yarn start:docker
Pulling postgres       ... done
Pulling subquery-node  ... done
Pulling graphql-engine ... done
Building with native build. Learn about native build in Compose here: https://docs.docker.com/go/compose-native-build/
nominator-subql_postgres_1 is up-to-date
Recreating nominator-subql_subquery-node_1 ... done

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

when trying to run the docker image. When inspecting the health status, seems it tries to curl some endpoint that isn't available:

❯ docker inspect --format "{{json .State.Health }}" 31d7676fdf6f | jq
{
  "Status": "unhealthy",
  "FailingStreak": 13,
  "Log": [
    {
      "Start": "2022-07-28T14:08:09.246773885+02:00",
      "End": "2022-07-28T14:08:09.366173339+02:00",
      "ExitCode": 22,
      "Output": "  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\r  0    64    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\ncurl: (22) The requested URL returned error: 503\n"
    },

I tried a few different things, including a different rpc node, removing the dictionary, etc. What was weird is that subql-node -f . worked fine. I then tried downgrading the subql-node docker image to v1.5.2-4, which resulted in the same thing, and then v1.5.1, which then worked. So this was something introduced introduced in v1.5.2-4 and v1.6.0, which queries something that isn't returning right.

[cy6erninja]

Faced the same issue with onfinality/subql-node:latest (1.6.0). Downgrading to 1.5.1 indeed helped. Glad the fix is on its way 👍

[AtelyPham]

I'm facing the same problem, right now, I change the health test endpoint in docker-compose.yml to http://subquery-node:3000/health, and it work for me. But it's best if linked PR is merged.

[cy6erninja]

May I ask, how long does it take for the update to reach dockerhub?

[jiqiang90]

Hi @cy6erninja I think within this week will have a patch release for this, and new docker image will build and publish together

[stwiname]

This should be fixed with 1.6.1

[CocDap]

I m still facing this issue
Node version: v20.8.0