BAStos525

**UPD**: `Error: Container operations are only supported on Linux runners` caused by: ``` container: image: 7272721/i2-ci:nightly ``` What's is really into this image and if it's possible do not use...

Here is [logs of the failed CI job](https://github.com/BAStos525/soramitsu-iroha/actions/runs/3329114231/jobs/5508272886) that run on the M1 with builder image cached. Could you please help to understand what's the problem and how it could...

> It looks like a specific library fails to compile. We should try and run this outside docker, so we can get a clearer picture of what's going on. I...

> * Release workflows are triggered. Needs to re-target the branch? >  > * Follow [the guide](https://github.com/hyperledger/iroha/blob/4936869dda441d814b50c09a8995e62640ad4fa5/CONTRIBUTING.md#git-workflow) for the commit message format >  To update the branch was...

What do you mean under the wrong path to `config.json`? `/opt/iroha2-deploy/configs/peer` contains [this file](https://github.com/hyperledger/iroha/blob/iroha2-dev/configs/peer/config.json). At least, it works fine with `iroha2:stable` image.

The last one failed `hyperledger/iroha2:dev`: `DIGEST:sha256:e28ffd9e89f90b3982d1e5c222be104c62002bff7b43c98e447017cec7e462e4` Present `iroha2:stable` images works.

I tried again with this docker-compose.yaml where IROHA_TORII is declared as env var: ``` version: "2.4" services: iroha2: container_name: iroha2 image: hyperledger/iroha2:dev restart: always mem_limit: 14g environment: IROHA_PUBLIC_KEY: 'ed01201c61faf8fe94e253b93114240394f79a607b7fa55f9e5a41ebec74b88055768b' IROHA_PRIVATE_KEY:...

Also I noticed that `config.json` is required in any case: if [volume is not active](https://github.com/hyperledger/iroha/blob/274b96c6e075624219eaf8e4ea5f565dd8428beb/docker-compose.yml#L17), IROHA_TORII via env var doesn't work for local deployment as well.

> If the necessity for `config.json` is the case with the latest image after the fix, we have to reopen #1990 As far as I know, `config.json` is required by...

> Have you checked that the remote instance and your local machine have the same hashes of `hyperledger/iroha2:dev` ? > > BTW this can be a issue specific to the...