Is it possible to specify private registry when installing velero using helm

[HollyQM]

Scenario:
Trying to install velero deployment using helm with image specification to target to our private registry but the container image is always coming from velero/velero:v1.9.0. Please advise if any parameter we can use to let container image originate from required private registry.

tried command combination:

--set container.image.registry=acr4testagain.azurecr.io --set container.image.image=acr4testagain.azurecr.io/velerotest:v1.9.0 --set initContainers[0].name=velero-plugin-for-microsoft-azure --set initContainers[0].image=acr4testagain.azurecr.io/velerotest:v1.5.0

--set container.image.registry=acr4testagain.azurecr.io --set container.velero.image.image=acr4testagain.azurecr.io/velerotest:v1.9.0 --set initContainers[0].name=velero-plugin-for-microsoft-azure --set initContainers[0].image=acr4testagain.azurecr.io/velerotest:v1.5.0

can see deployment still showing container image from velero/velero:v1.9.0:

Containers:
velero:
Container ID:
Image: velero/velero:v1.9.0
Image ID:
Port: 8085/TCP
Host Port: 0/TCP
Command:
/velero
Args:
server
State: Waiting
Reason: PodInitializing

ASK:
is there anyway to install velero using helm with images coming from private registry? Will this work as it seems helm ls is not showing properly for this installation as well after specifying private registry. Please advise.