when starting container with
$ docker pull confluxchain/conflux-rust
$ docker run -p 12537:12537 --rm --name cfx-node confluxchain/conflux-rust
following error occurs.
2023-03-22T18:45:28.330083726+00:00 INFO main conflux - Starting full client...
2023-03-22T18:45:28.330122797+00:00 INFO main client::comm - Working directory: Ok("/root/run")
./conflux.sh: line 8: 23 Illegal instruction /bin/conflux --config ./conflux.toml
(node:10) UnhandledPromiseRejectionWarning: Error: connect ECONNREFUSED 127.0.0.1:12537
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
(Use node --trace-warnings ... to show where the warning was created)
(node:10) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:10) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
./start.sh: line 10: fg: job has terminated
when starting container with $ docker pull confluxchain/conflux-rust $ docker run -p 12537:12537 --rm --name cfx-node confluxchain/conflux-rust
following error occurs.
2023-03-22T18:45:28.330083726+00:00 INFO main conflux - Starting full client... 2023-03-22T18:45:28.330122797+00:00 INFO main client::comm - Working directory: Ok("/root/run") ./conflux.sh: line 8: 23 Illegal instruction /bin/conflux --config ./conflux.toml (node:10) UnhandledPromiseRejectionWarning: Error: connect ECONNREFUSED 127.0.0.1:12537 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16) (Use
node --trace-warnings ...to show where the warning was created) (node:10) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag--unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:10) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. ./start.sh: line 10: fg: job has terminated