Use new docker image of substrate in CI about substrate-api-client HOT 7 CLOSED

After discussion: We could try to use the paritypr image one. Lets see if CI accepts that.

from substrate-api-client.

Unfortunately the change to the paritypr image #721 did not remove the warning above (see https://github.com/scs/substrate-api-client/actions/runs/7956482028). @haerdib can you check, if this warning is really introduced by the substrate node? Maybe I got this wrong ...

from substrate-api-client.

There does not seem to be an up-to-date Substrate docker atm: paritytech/polkadot-sdk#2750

I wonder if it's worth the effort to self-build a node, or if we wait for parity to fix this?

from substrate-api-client.

I would expect that Parity has some docker image, that let's you run a node, no? Or do you think they don't have that anymore? Are you sure it's not called differently or that there is another way of running a dummy substrate node?

from substrate-api-client.

If they do, I didn't find it in docker hub (see https://hub.docker.com/search?q=parity). And also I'd also expect them to update their doc accordingly, but they haven't: https://github.com/paritytech/polkadot-sdk/blob/master/substrate/docker/run.sh#L11

So I guess the above linked issue, especially the comment paritytech/polkadot-sdk#2750 (comment) is the issue here.

from substrate-api-client.

ok, I see. Thanks for checking. Then let's close this issue. Looks like there will be a new docker image eventually with the same name on dockerhub

from substrate-api-client.

Let's keep it so we don't forget about it. Maybe there will be a renaming or something.

Option: paritypr/substrate, which is used for zombienet. https://github.com/paritytech/polkadot-sdk/blob/5fc7622cb312f2d32ec8365012ee0a49622db8c8/substrate/zombienet/0001-basic-warp-sync/generate-warp-sync-database.toml#L4
This still seems to be updated. But no idea what kind of node is run there.

from substrate-api-client.