Docker - Error initialising Private Transaction Manager

[sorcer1122]

Hi, I tried to pull Docker containers on Ubuntu 20.04 and node container is constantly crashing with the following error

uname -a gives '...5.4.0-105-generic #119-Ubuntu SMP Mon Mar 7 18:49:24 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux'

Latest docker

Docker-compose is v2.6.1

Any ideas how to fix it?

[piotrhalickihah]

Do you have
PRIVATE_CONFIG=ignore docker-compose up -d
settings?

[sorcer1122]

@piotrhalickihah yes, I installed it as per the official instruction.

[piotrhalickihah]

Can you check what is the result of
docker exec env | grep PRIVATE_CONFIG

[sorcer1122]

docker exec requires at least 2 arguments

[sorcer1122]

I also tried to run 'docker exec [my_container_name] env | grep PRIVATE_CONFIG but received 'Error response from daemon: Container my_container_name is restarting'

[piotrhalickihah]

echo export PRIVATE_CONFIG=ignore > .env
source .env && docker-compose up -d

[sorcer1122]

Thanks, much better now but getting another error 'Cannot start mining without etherbase err="etherbase must be explicitly specified"
Fatal: Failed to start mining: etherbase missing: etherbase must be explicitly'

[piotrhalickihah]

Can you post the result of echo export commend

[sorcer1122]

[sorcer1122]

Seems like I am now facing this problem - #43

Tried to change quorum to 21.7.1 - did not help

[BA-MikeJ]

Hi, now your container keeps restarting during this error too? If not, could you show me the list of processes - the output of the command: docker exec <container-id> ps
However, if it keeps restarting and you cannot execute this command, I suggest you replace all dynamic variables in entrypoint, like this:

entrypoint:
  - /bin/sh
  - -c
  - |
    DDIR=/qdata/dd
    GENESIS_FILE="/network/genesis.json"
    CONSENSUS_RPC_API="istanbul"
    NETWORK_ID=190260
    GETH_ARGS_istanbul="--emitcheckpoints --istanbul.blockperiod 10 --mine --miner.threads 1 --syncmode full"
    if [ ! -f /qdata/dd/control_file ]; then
      mkdir -p /qdata/dd/keystore
      mkdir -p /qdata/dd/geth
      geth --datadir /qdata/dd init /network/genesis.json
      echo "Created" > /qdata/dd/control_file
    fi
    geth \
      --identity node1-istanbul-debug \
      --datadir /qdata/dd \
      --bootnodes enode://ac6b1096ca56b9f6d004b779ae3728bf83f8e22453404cc3cef16a3d9b96608bc67c4b30db88e0a5a6c6390213f7acbe1153ff6d23ce57380104288ae19373ef@54.146.254.245:21000 \
      --verbosity 5 \
      --networkid 190260 \
      --http \
      --http.corsdomain "*" \
      --http.vhosts "*" \
      --http.addr 0.0.0.0 \
      --http.port 8545 \
      --http.api admin,eth,debug,miner,net,shh,txpool,personal,web3,quorum,istanbul \
      --port 21000 \
      --nousb \
       --emitcheckpoints --istanbul.blockperiod 10 --mine --miner.threads 1 --syncmode full

[sorcer1122]

Thanks. Sadly, the container constantly restarts. I tried to change entrypoints but it did not help, still getting the same error and the container keeps restarting.

[BA-MikeJ]

please share the log (preferably text, not a screenshot) from the beginning of the container startup, maybe we'll find something there.

[BA-MikeJ]

and additional please share the docker version docker --version

[sorcer1122]

Docker version 20.10.17, build 100c701
docker.txt

[BA-MikeJ]

This line show that you're using chain with id 1 instead the one that is defined in genesis.json.

{"log":"INFO [07-08|06:44:32.729] Initialised chain configuration          config=\"{ChainID: 1 Homestead: 1150000 DAO: 1920000 DAOSupport: true EIP150: 2463000 EIP155: 2675000 EIP158: 2675000 Byzantium: 4370000 IsQuorum: false Constantinople: 7280000 TransactionSizeLimit: 0 MaxCodeSize: 0 Petersburg: 7280000 Istanbul: 9069000, Muir Glacier: 9200000, Berlin: \u003cnil\u003e YOLO v3: \u003cnil\u003e PrivacyEnhancements: \u003cnil\u003e PrivacyPrecompile: \u003cnil\u003e Engine: ethash}\"\n","stream":"stderr","time":"2022-07-08T06:44:32.729240597Z"}

Do you have the latest changes from the repository? Please also share output from command cat network/testnet/genesis.json | grep chain
You can try also remove all data in container docker-compose down --volumes (be careful in which folder you do this, so you don't delete other data)