# Panique docker synchro forgeron

**URL:** https://forum.duniter.org/t/panique-docker-synchro-forgeron/12382
**Category:** Duniter-v2s
**Created:** [31 July 2024 10:40 UTC](https://forum.duniter.org/t/panique-docker-synchro-forgeron/12382 "2024-07-31T10:40:20Z")
**Posts on this page:** 10
**Page:** 1

<div class="post-metadata">

### Author: ![syoul46](https://forum.duniter.org/user_avatar/forum.duniter.org/syoul46/32/7384_2.png) [@syoul46](https://forum.duniter.org/u/syoul46)
#### Post date: [31 July 2024 10:40 UTC](https://forum.duniter.org/t/panique-docker-synchro-forgeron/12382/1 "2024-07-31T10:40:20Z")

</div>

Coucou @HugoTrentesaux ,  
j’ai suivi la doc pour lancer un forgeron, et j’ai une panique:

```auto
Error: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
Node peer ID is ''.
Starting duniter with parameters: --name Soul_node --node-key-file /var/lib/duniter/node.key --public-addr /dns/g1.syoul.fr/tcp/30334 --listen-addr /ip4/0.0.0.0/tcp/30333 --rpc-cors all --rpc-methods Unsafe --validator --blocks-pruning 14400 --chain gdev -d /var/lib/duniter --unsafe-rpc-external
Error: NetworkKeyNotFound("/var/lib/duniter/node.key")
Generating node key file '/var/lib/duniter/node.key'...
thread 'main' panicked at node/src/command.rs:182:21:
unknown runtime
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
Node peer ID is ''.
Starting duniter with parameters: --name Soul_node --node-key-file /var/lib/duniter/node.key --public-addr /dns/g1.syoul.fr/tcp/30334 --listen-addr /ip4/0.0.0.0/tcp/30333 --rpc-cors all --rpc-methods Unsafe --validator --blocks-pruning 14400 --chain gdev -d /var/lib/duniter --unsafe-rpc-external
Error: NetworkKeyNotFound("/var/lib/duniter/node.key")
Generating node key file '/var/lib/duniter/node.key'...
thread 'main' panicked at node/src/command.rs:182:21:
unknown runtime
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
Node peer ID is ''.
Starting duniter with parameters: --name Syoul_smith --node-key-file /var/lib/duniter/node.key --public-addr /dns/g1.syoul.fr/tcp/30334 --listen-addr /ip4/0.0.0.0/tcp/30333 --rpc-cors all --rpc-methods Unsafe --validator --blocks-pruning 14400 --chain gdev -d /var/lib/duniter --unsafe-rpc-external
Error: NetworkKeyNotFound("/var/lib/duniter/node.key")
Generating node key file '/var/lib/duniter/node.key'...
thread 'main' panicked at node/src/command.rs:182:21:
unknown runtime
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
Node peer ID is ''.
Starting duniter with parameters: --name Soul_node --node-key-file /var/lib/duniter/node.key --public-addr /dns/g1.syoul.fr/tcp/30334 --listen-addr /ip4/0.0.0.0/tcp/30333 --rpc-cors all --rpc-methods Unsafe --validator --blocks-pruning 14400 --chain gdev -d /var/lib/duniter --unsafe-rpc-external
Error: NetworkKeyNotFound("/var/lib/duniter/node.key")
Generating node key file '/var/lib/duniter/node.key'...
thread 'main' panicked at node/src/command.rs:182:21:
unknown runtime
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
Node peer ID is ''.
Starting duniter with parameters: --name Soul_node --node-key-file /var/lib/duniter/node.key --public-addr /dns/g1.syoul.fr/tcp/30334 --listen-addr /ip4/0.0.0.0/tcp/30333 --rpc-cors all --rpc-methods Unsafe --validator --blocks-pruning 14400 --chain gdev -d /var/lib/duniter --unsafe-rpc-external
Error: NetworkKeyNotFound("/var/lib/duniter/node.key")
Generating node key file '/var/lib/duniter/node.key'...
thread 'main' panicked at node/src/command.rs:182:21:
unknown runtime
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
Node peer ID is ''.
Starting duniter with parameters: --name Soul_node --node-key-file /var/lib/duniter/node.key --public-addr /dns/g1.syoul.fr/tcp/30334 --listen-addr /ip4/0.0.0.0/tcp/30333 --rpc-cors all --rpc-methods Unsafe --validator --blocks-pruning 14400 --chain gdev -d /var/lib/duniter --unsafe-rpc-external
Error: NetworkKeyNotFound("/var/lib/duniter/node.key")
Generating node key file '/var/lib/duniter/node.key'...
thread 'main' panicked at node/src/command.rs:182:21:
unknown runtime
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
Node peer ID is ''.
Starting duniter with parameters: --name Soul_node --node-key-file /var/lib/duniter/node.key --public-addr /dns/g1.syoul.fr/tcp/30334 --listen-addr /ip4/0.0.0.0/tcp/30333 --rpc-cors all --rpc-methods Unsafe --validator --blocks-pruning 14400 --chain gdev -d /var/lib/duniter --unsafe-rpc-external
Error: NetworkKeyNotFound("/var/lib/duniter/node.key")
Generating node key file '/var/lib/duniter/node.key'...
thread 'main' panicked at node/src/command.rs:182:21:
unknown runtime
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
Node peer ID is ''.
Starting duniter with parameters: --name Soul_node --node-key-file /var/lib/duniter/node.key --public-addr /dns/g1.syoul.fr/tcp/30334 --listen-addr /ip4/0.0.0.0/tcp/30333 --rpc-cors all --rpc-methods Unsafe --validator --blocks-pruning 14400 --chain gdev -d /var/lib/duniter --unsafe-rpc-external
Error: NetworkKeyNotFound("/var/lib/duniter/node.key")
Generating node key file '/var/lib/duniter/node.key'...
thread 'main' panicked at node/src/command.rs:182:21:
unknown runtime
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
Node peer ID is ''.
Starting duniter with parameters: --name Soul_node --node-key-file /var/lib/duniter/node.key --public-addr /dns/g1.syoul.fr/tcp/30334 --listen-addr /ip4/0.0.0.0/tcp/30333 --rpc-cors all --rpc-methods Unsafe --validator --blocks-pruning 14400 --chain gdev -d /var/lib/duniter --unsafe-rpc-external
Error: NetworkKeyNotFound("/var/lib/duniter/node.key")
Generating node key file '/var/lib/duniter/node.key'...
thread 'main' panicked at node/src/command.rs:182:21:
unknown runtime
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
Node peer ID is ''.
Starting duniter with parameters: --name Soul_node --node-key-file /var/lib/duniter/node.key --public-addr /dns/g1.syoul.fr/tcp/30334 --listen-addr /ip4/0.0.0.0/tcp/30333 --rpc-cors all --rpc-methods Unsafe --validator --blocks-pruning 14400 --chain gdev -d /var/lib/duniter --unsafe-rpc-external
Error: NetworkKeyNotFound("/var/lib/duniter/node.key")
Generating node key file '/var/lib/duniter/node.key'...
thread 'main' panicked at node/src/command.rs:182:21:
unknown runtime
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
Node peer ID is ''.
Starting duniter with parameters: --name Soul_node --node-key-file /var/lib/duniter/node.key --public-addr /dns/g1.syoul.fr/tcp/30334 --listen-addr /ip4/0.0.0.0/tcp/30333 --rpc-cors all --rpc-methods Unsafe --validator --blocks-pruning 14400 --chain gdev -d /var/lib/duniter --unsafe-rpc-external
Error: NetworkKeyNotFound("/var/lib/duniter/node.key")
Generating node key file '/var/lib/duniter/node.key'...
thread 'main' panicked at node/src/command.rs:182:21:
unknown runtime
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
Node peer ID is ''.
Starting duniter with parameters: --name Soul_node --node-key-file /var/lib/duniter/node.key --public-addr /dns/g1.syoul.fr/tcp/30334 --listen-addr /ip4/0.0.0.0/tcp/30333 --rpc-cors all --rpc-methods Unsafe --validator --blocks-pruning 14400 --chain gdev -d /var/lib/duniter --unsafe-rpc-external
Error: NetworkKeyNotFound("/var/lib/duniter/node.key")
Generating node key file '/var/lib/duniter/node.key'...
thread 'main' panicked at node/src/command.rs:182:21:
unknown runtime
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
Node peer ID is ''.
Starting duniter with parameters: --name Soul_node --node-key-file /var/lib/duniter/node.key --public-addr /dns/g1.syoul.fr/tcp/30334 --listen-addr /ip4/0.0.0.0/tcp/30333 --rpc-cors all --rpc-methods Unsafe --validator --blocks-pruning 14400 --chain gdev -d /var/lib/duniter --unsafe-rpc-external
Error: NetworkKeyNotFound("/var/lib/duniter/node.key")

```

* * *

mon compose:

```auto
# Duniter smith node
services:
  duniter-smith:
    image: duniter/duniter-v2s-gdev:latest # <--- here is the image
    restart: unless-stopped
    ports:
      # prometheus endpoint
      - 127.0.0.1:9615:9615
      # rpc via websocket
      - 127.0.0.1:9944:9944
      # public p2p endpoint
      - 30334:30333 # <--- here is your public p2p port
    volumes:
      - duniter-data:/var/lib/duniter/
    environment:
      - DUNITER_CHAIN_NAME=gdev # <--- the network you want to connect to
      - DUNITER_NODE_NAME=Syoul_smith # <--- the name of your node on the network
      - DUNITER_VALIDATOR=true # <--- enable validator
      - DUNITER_PRUNING_PROFILE=light # <--- stays light
      - DUNITER_PUBLIC_ADDR=/dns/g1.syoul.fr/tcp/30334 # <--- your public p2p endpoint
      - DUNITER_LISTEN_ADDR=/ip4/0.0.0.0/tcp/30333

volumes:
  duniter-data:

```

---

<div class="post-metadata">

### Author: ![HugoTrentesaux](https://forum.duniter.org/user_avatar/forum.duniter.org/hugotrentesaux/32/6396_2.png) [@HugoTrentesaux](https://forum.duniter.org/u/HugoTrentesaux)
#### Post date: [1 August 2024 09:48 UTC](https://forum.duniter.org/t/panique-docker-synchro-forgeron/12382/2 "2024-08-01T09:48:56Z")

</div>

J’ai vu ça avec @1000i100 aussi, je pense que c’est lié à la dernière image poussée par @cgeek sur

> [@syoul46](#):
>
> `duniter/duniter-v2s-gdev:latest`

Je ne sais plus comment on avait réglé ça mais on avait réussi puisqu’il forge des blocs. Soit on avait changé d’image, soit on avait forcé la génération de la clé en supprimant le volume ou manuellement. En gros l’idée c’est que Duniter devrait générer une clé automatiquement si elle n’existe pas grâce au entrypoint de @Pini :

> [@syoul46](#):
>
> `Generating node key file '/var/lib/duniter/node.key'...`

Mais ça ne fonctionne pas avec l’argument “gdev”

> [@syoul46](#):
>
> `unknown runtime`

Donc comme la génération de clé n’a pas fonctionné, le nœud ne peut pas démarrer. @1000i100 tu pourrais aider @syoul46 ?

---

<div class="post-metadata">

### Author: ![syoul46](https://forum.duniter.org/user_avatar/forum.duniter.org/syoul46/32/7384_2.png) [@syoul46](https://forum.duniter.org/u/syoul46)
#### Post date: [8 August 2024 09:22 UTC](https://forum.duniter.org/t/panique-docker-synchro-forgeron/12382/3 "2024-08-08T09:22:49Z")

</div>

j’ai modifié mon compose avec l’avant dernière release :

` image: duniter/duniter-v2s-gdev:runtime-800`

là la synchro s’est exécutée nikel (et donc la génération de clé aussi).

* * *

Prochaine étape :

Je ne trouve pas de doc claire sur comment injecter ma clé membre dans mon noeud.  
`set session keys`

Quelqu’un pour m’aiguiller ?  
merci par avance

---

<div class="post-metadata">

### Author: ![Pini](https://forum.duniter.org/user_avatar/forum.duniter.org/pini/32/6819_2.png) [@Pini](https://forum.duniter.org/u/Pini)
#### Post date: [8 August 2024 10:32 UTC](https://forum.duniter.org/t/panique-docker-synchro-forgeron/12382/4 "2024-08-08T10:32:21Z")

</div>

Normalement tu devrais pouvoir trouver toutes infos dans ce fil : [Ğcli s'adapte au runtime 800 : nouveau parcours forgeron](https://forum.duniter.org/t/gcli-sadapte-au-runtime-800-nouveau-parcours-forgeron/11880)

L’association avec ton identité se fait via la configuration de `gcli`.

---

<div class="post-metadata">

### Author: ![syoul46](https://forum.duniter.org/user_avatar/forum.duniter.org/syoul46/32/7384_2.png) [@syoul46](https://forum.duniter.org/u/syoul46)
#### Post date: [9 August 2024 08:34 UTC](https://forum.duniter.org/t/panique-docker-synchro-forgeron/12382/5 "2024-08-09T08:34:04Z")

</div>

Merci @Pini , je vais regarder cela.

---

<div class="post-metadata">

### Author: ![matograine](https://forum.duniter.org/letter_avatar/matograine/32/5_5575768a8748004e209b776fc1b2916d.png) [@matograine](https://forum.duniter.org/u/matograine)
#### Post date: [1 January 2025 07:39 UTC](https://forum.duniter.org/t/panique-docker-synchro-forgeron/12382/6 "2025-01-01T07:39:13Z")

</div>

Pour info, le problème se reproduit avec l’image duniter/duniter-v2s-gdev-800 (modifiée il y a 10 jours sur DockerHub)

et avec duniter/duniter-v2s-gdev-800:801-0.8.1 (alors que je me souviens nettement l’avoir utilisée par le passé)

J’ai supprimé le volume avant de démarrer le conteneur.

```auto
duniter-smith-1 | Error: NetworkKeyNotFound("/var/lib/duniter/node.key")
duniter-smith-1 | Generating node key file '/var/lib/duniter/node.key'...
duniter-smith-1 | thread 'main' panicked at node/src/command.rs:185:21:
duniter-smith-1 | unknown runtime
duniter-smith-1 | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
duniter-smith-1 | Error: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
duniter-smith-1 | Node peer ID is ''.
duniter-smith-1 | Starting duniter with parameters: --name Matograine-smith --node-key-file /var/lib/duniter/node.key --public-addr /dns/gdev.matograine.fr/tcp/30333 --listen-addr /ip4/0.0.0.0/tcp/30333 --rpc-cors all --rpc-methods Unsafe --validator --blocks-pruning 14400 --chain gdev -d /var/lib/duniter --unsafe-rpc-external
duniter-smith-1 | Error: NetworkKeyNotFound("/var/lib/duniter/node.key")

```

---

<div class="post-metadata">

### Author: ![poka](https://forum.duniter.org/user_avatar/forum.duniter.org/poka/32/6827_2.png) [@poka](https://forum.duniter.org/u/poka)
#### Post date: [1 January 2025 14:33 UTC](https://forum.duniter.org/t/panique-docker-synchro-forgeron/12382/7 "2025-01-01T14:33:03Z")

</div>

Peux-tu nous partager ton docker-compose stp ?

---

<div class="post-metadata">

### Author: ![matograine](https://forum.duniter.org/letter_avatar/matograine/32/5_5575768a8748004e209b776fc1b2916d.png) [@matograine](https://forum.duniter.org/u/matograine)
#### Post date: [2 January 2025 06:37 UTC](https://forum.duniter.org/t/panique-docker-synchro-forgeron/12382/8 "2025-01-02T06:37:30Z")

</div>

Avec plaisir 🙂

```auto
services:
  duniter-smith:
    image: duniter/duniter-v2s-gdev-800:801-0.8.1 # <--- image Docker
    restart: unless-stopped
    ports:
      # prometheus endpoint for monitoring
      #- 127.0.0.1:9615:9615
      # private rpc endpoint (do not expose publicly)
      - 127.0.0.1:9944:9944
      # public p2p endpoint
      - 30333:30333 # <--- port p2p public
    volumes:
      - duniter-data:/var/lib/duniter/
    environment:
      - DUNITER_CHAIN_NAME=gdev # <--- réseau où se connecter
      - DUNITER_NODE_NAME=Matograine-smith # <--- le nom de votre noeud
      - DUNITER_VALIDATOR=true # <--- activer le noeud validateur
      - DUNITER_PRUNING_PROFILE=light # <--- conserver 256 blocs d'historique
      - DUNITER_PUBLIC_ADDR=/dns/gdev.matograine.fr/tcp/30333 # <--- endpoint p2p public
      - DUNITER_LISTEN_ADDR=/ip4/0.0.0.0/tcp/30333 # <--- adresse d'écoute p2p
volumes:
  duniter-data:

```

---

<div class="post-metadata">

### Author: ![Moul](https://forum.duniter.org/user_avatar/forum.duniter.org/moul/32/9145_2.png) [@Moul](https://forum.duniter.org/u/Moul)
#### Post date: [2 January 2025 12:35 UTC](https://forum.duniter.org/t/panique-docker-synchro-forgeron/12382/9 "2025-01-02T12:35:06Z")

</div>

Les erreurs :

> [@syoul46](#):
>
> ```auto
> Error: NetworkKeyNotFound("/var/lib/duniter/node.key")
> Generating node key file '/var/lib/duniter/node.key'...
> thread 'main' panicked at node/src/command.rs:182:21:
> unknown runtime
> 
> ```

> [@matograine](#):
>
> `Error: NetworkKeyNotFound("/var/lib/duniter/node.key")`

Est-ce que ce fichier existe dans vos conteneurs ?  
Ça semble être soit un problème à [générer ce fichier](https://git.duniter.org/nodes/rust/duniter-v2s/-/blob/6e8eafb526a0e793172109abdb23fe4ff276da3f/docker/docker-entrypoint#L32-35) soit à [déterminer de quel/lle runtime/monnaie il s’agit](https://git.duniter.org/nodes/rust/duniter-v2s/-/blob/582a46c228e9686f34a3e025dde06ea5dbe7887a/node/src/command.rs#L178-186), bien que ça soit spécifié dans la CLI de `docker` :

> [@matograine](#):
>
> `--chain gdev`

---

<div class="post-metadata">

### Author: ![HugoTrentesaux](https://forum.duniter.org/user_avatar/forum.duniter.org/hugotrentesaux/32/6396_2.png) [@HugoTrentesaux](https://forum.duniter.org/u/HugoTrentesaux)
#### Post date: [3 January 2025 11:21 UTC](https://forum.duniter.org/t/panique-docker-synchro-forgeron/12382/10 "2025-01-03T11:21:14Z")

</div>

> [@matograine](#):
>
> l’image duniter/duniter-v2s-gdev-800 (modifiée il y a 10 jours sur DockerHub)

Pas le temps de vérifier vers quoi elle pointe pour l’instant, on a peut-être écrasé trop de choses avec nos test 😭

Il faut que je documente précisément ce que signifie et d’où provient chaque bout dans `duniter/duniter-v2s-gdev-800:900-0.9.1` parce que je me perds un peu. Je pense que c’est :

- 800 → numéro du runtime genesis dans la branche network (cf doc de [!297](https://git.duniter.org/nodes/rust/duniter-v2s/-/merge_requests/297))
- 900 → je ne sais plus
- 0.9.1 → version du client dans la branche master, potentiellement fusionnée sur la branche de release réseau

> [@Moul](#):
>
> Ça semble être soit un problème à [générer ce fichier](https://git.duniter.org/nodes/rust/duniter-v2s/-/blob/6e8eafb526a0e793172109abdb23fe4ff276da3f/docker/docker-entrypoint#L32-35) soit à [déterminer de quel/lle runtime/monnaie il s’agit](https://git.duniter.org/nodes/rust/duniter-v2s/-/.blob/14b9f289b62b396da92bddc81b35609254cee9a9/node/src/command.rs#L178-186)

Comme tu dis, d’où la difficulté à debugger ça. Il faut que tester de zéro au calme, ce que je n’ai pas la possibilité de faire pour l’instant.