test(fabric): fix fabric AIO couchdb No such file or directory

[petermetz]

Describe the bug

When I try to run the command that's in the Fabric connector's README.md, it
does not work for multiple reasons:

1. It does not specify the elevate permissions via the --privileged flag
2. The image at the current latest version (1.0.0-rc.3) seems broken altogether due to the Fabric CouchDB container image not being cached locally as intended.

To Reproduce

docker run --privileged -p 0.0.0.0:8545:8545/tcp -p 0.0.0.0:8546:8546/tcp -p 0.0.0.0:8888:8888/tcp -p 0.0.0.0:9001:9001/tcp -p 0.0.0.0:9545:9545/tcp ghcr.io/hyperledger/cactus-fabric-all-in-one:v1.0.0-rc.3

Expected behavior

The container should boot up without issues to the point where the healthcheck is passing and the ledger is operational.

Logs/Stack traces

2021-12-21-fabric-1-aio-tar-couchdb-crash.log

2021-12-21 23:51:49,022 INFO spawned: 'fabric-network' with pid 15217
Loaded image: hyperledger/fabric-peer:1.4.8
2021-12-21 23:51:49,236 DEBG 'fabric-network' stdout output:
Loaded image: hyperledger/fabric-peer:1.4.8

Loaded image: hyperledger/fabric-orderer:1.4.8
2021-12-21 23:51:49,448 DEBG 'fabric-network' stdout output:
Loaded image: hyperledger/fabric-orderer:1.4.8

Loaded image: hyperledger/fabric-ccenv:1.4.8
2021-12-21 23:51:50,200 DEBG 'fabric-network' stdout output:
Loaded image: hyperledger/fabric-ccenv:1.4.8

2021-12-21 23:51:50,200 INFO success: fabric-network entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Loaded image: hyperledger/fabric-tools:1.4.8
2021-12-21 23:51:51,103 DEBG 'fabric-network' stdout output:
Loaded image: hyperledger/fabric-tools:1.4.8

Loaded image: hyperledger/fabric-ca:1.4.9
2021-12-21 23:51:51,415 DEBG 'fabric-network' stdout output:
Loaded image: hyperledger/fabric-ca:1.4.9

tar: can't change directory to '/etc/hyperledger/fabric/fabric-couchdb/': No such file or directory
2021-12-21 23:51:51,428 DEBG 'fabric-network' stderr output:
tar: can't change directory to '/etc/hyperledger/fabric/fabric-couchdb/': No such file or directory

open /var/lib/docker/tmp/docker-import-640167045/repositories: no such file or directory
2021-12-21 23:51:51,489 DEBG 'fabric-network' stderr output:
open /var/lib/docker/tmp/docker-import-640167045/repositories: no such file or directory

2021-12-21 23:51:51,491 DEBG received SIGCHLD indicating a child quit
2021-12-21 23:51:51,491 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 140196757982560 for <Subprocess at 140196758149008 with name fabric-network in state RUNNING> (stdout)>
2021-12-21 23:51:51,492 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 140196757982512 for <Subprocess at 140196758149008 with name fabric-network in state RUNNING> (stderr)>
2021-12-21 23:51:51,492 INFO exited: fabric-network (exit status 1; not expected)

Screenshots

N/A

Cloud provider or hardware configuration:

dev machine

Operating system name, version, build:

Linux 5.11.0-43-generic x86_64
NAME="Ubuntu"
VERSION="20.04.3 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.3 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

Hyperledger Cactus release version or commit (git rev-parse --short HEAD):

1.0.0-rc.3

Hyperledger Cactus Plugins/Connectors Used

Fabric Connector Plugin

Additional context

• Came up during the migration to the GitHub Container Registry.
• It works just fine with 1.0.0-rc.2 so this must be a recently introduced bug in the Dockerfile

[petermetz]

@outSH Is this what you fixed in that other PR related to the Fabric AIO image? If yes, then we can close this one.

[outSH]

@petermetz Yes, this error is fixed in #1754

[petermetz]

@outSH Cool, thank you. I'm closing this issue then.