Release new image with ĞDev5 chainspecs

@HugoTrentesaux je sais pas pk, probablement dû à une erreur de manipulation de ma part, le peerid de mon noeud mirroir à changé:

12D3KooWPJGF2DevfeH3gDy4rKHTR4QcyNkMWuKMD7xNeSNXhRha

Où vois-tu ce peerid ? Quand je demande à mon noeud, il me répond 12D3KooWAVY7T3eqGxyjCPbKfMKrkT55XR6BuBxpW5sEEJYAJu3n

Dans les logs de mon noeud mirroir:

poka@v2s-poka:~/duniter-indexer$ docker compose logs duniter-rpc | head -n50
duniter-indexer-duniter-rpc-1  | Node key file '/var/lib/duniter/node.key' exists.
duniter-indexer-duniter-rpc-1  | Node peer ID is '12D3KooWPJGF2DevfeH3gDy4rKHTR4QcyNkMWuKMD7xNeSNXhRha'.
[...]
duniter-indexer-duniter-rpc-1  | 2023-03-10 12:35:58 🏷  Local node identity is: 12D3KooWPJGF2DevfeH3gDy4rKHTR4QcyNkMWuKMD7xNeSNXhRha    
[...]
duniter-indexer-duniter-rpc-1  | 2023-03-10 12:35:58 🔍 Discovered new external address for our node: /ip4/163.172.105.161/tcp/30333/ws/p2p/12D3KooWPJGF2DevfeH3gDy4rKHTR4QcyNkMWuKMD7xNeSNXhRha 

Haha oui désolé, j’avais mal lu, je parlais du mien. Le tien est effectivement 12D3KooWPJGF2DevfeH3gDy4rKHTR4QcyNkMWuKMD7xNeSNXhRha, il faudra modifier…

1 Like

It does not tell what are the embeded chainspecs of this image. Maybe we should instead use tags like:

  • duniter/duniter-v2s:latest-gdev
  • duniter/duniter-v2s:latest-gtest
  • duniter/duniter-v2s:latest-g1

This way it would be clear which network Duniter tries to join when started.

On GitLab container registry, we can store containers into channels/repositories:

  • gdev:latest
  • g1:latest
  • gtest:latest

See for instance Silkaj’s channels.

2 Likes

I’d prefer:

  • duniter/duniter-v2s-gdev:latest
  • duniter/duniter-v2s-gtest:latest
  • duniter/duniter-v2s-g1:latest
2 Likes

Why do you prefer this option? I personally would prefer Moul’s option with channels. But I do not want to configure GitLab container registry or modify CI myself.

At the moment I think it is good if early testers understand the concepts of runtimes / chainspecs / bootnodes well enough to be able to choose the good image depending on what they are trying to do.

As said in the other thread I think it’s easier for newcomers when the latest tag is the one to choose.

I won’t say otherwise. But it doesn’t seem to be the case right now.

I moved this topic in ĞDev category and added the todo tag because we still should update the embeded bootnodes in ĞDev chainspecs.

Did you fix your setup? Do you now have a RPC node?

I am only maintaining a smith node for now, so no RPC interface to share yet.

1 Like