[Docker] Incubed server can't decode private private key on startup

[eshavkun]

Tried to run Incubed server using docker-compose.yml from this repo. Unfortunately it fails on startup saying Could not decode the private (see full log below). Tried different key JSON files (generated by geth, parity, myCrypto) with the same result:

incubed-server_1  | no config found (Error: ENOENT: no such file or directory, open 'config.json')! using defaults
incubed-server_1  | Error starting the server : Could not decode the private : ethUtil.sha3(...).replace is not a function { port: 8500,
incubed-server_1  |   chains: 
incubed-server_1  |    { '0x5': 
incubed-server_1  |       { rpcUrl: 'http://localhost:8545',
incubed-server_1  |         privateKey: '/secure/myKey.json',
incubed-server_1  |         minBlockHeight: 6,
incubed-server_1  |         registry: '0x85613723dB1Bc29f332A37EeF10b61F8a4225c7e',
incubed-server_1  |         registryRPC: '',
incubed-server_1  |         privateKeyPassphrase: '123456789' } },
incubed-server_1  |   logging: { colors: true } }
incubed-server_1  | error: Error starting the server Error: Could not decode the private : ethUtil.sha3(...).replace is not a function port=8500, rpcUrl=http://localhost:8545, privateKey=/secure/myKey.json, minBlockHeight=6, registry=0x85613723dB1Bc29f332A37EeF10b61F8a4225c7e, registryRPC=, privateKeyPassphrase=123456789, colors=true
in3-server_incubed-server_1 exited with code 1

[ligi]

also tried a json generated by WallETH
What kind of json is needed there? Is it some custom format for IN3?

[ltfschoen]

as discussed with @eshavkun, it appears that the IN3 Server repo https://github.com/slockit/in3-server was previously public, but now that it isn't, so we can't view or contribute to the code

[simon-jentzsch]

Thanks for the bug, we will fix it. As a workaround, you may also pass a raw private key as argument. (starting with 0x...)

[junaidev]

Its fixed in latest code.