sample-network's cc deploy step fails on k3s environment

[thejjw]

Hello,

I have tested fabric-operator with its sample-network, first with KIND and was able to confirm up to a point where chaincode deployment and invoke/query were successful.
Then I have tried k3s setup and it seems that cc deploy step keeps failing.
I tried k9s to verify the situation and it seems -ccaas- chaincode container cannot start, with d description says failed to pull and unpack image "docker.io/fabric-samples/asset-transfer-basic/chaincode-java:latest": failed to resolve reference "docker.io/fabric-samples/asset-transfer-basic/chaincode-java:latest": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed. I suppose its calling for a wrong image reference.
How could I fix this issue so that I can use chaincode with fabric-operator on k3s? Any help is appreciated please.

Thanks.

Here are some screenshots:
[1]

[2]

[thejjw]

Since I was able to run the similar via test-network-k8s when I re-setup k8s environment with k3s+docker, I tried the same. However, this time ./network up gets stuck while trying to launch Fabric CA. When I check via k9s it just shows pending forever without reporting actual error. I wonder what's the crucial difference between two since they seem so similar..

⚠️  - Launching Fabric CAs ...              
Waiting for deployment "org0-ca" rollout to finish: 0 of 1 updated replicas are available...  

[lonelymj]

Please ensure nerdctl is manage k3s's mirror library
export CONTAINERD_ADDRESS="unix:///run/k3s/containerd/containerd.sock"
There is an error in the official document

Need to be changed to：
export TEST_NETWORK_CONTAINER_CLI="nerdctl"

I hope it can help you！