Grpciotimeout even after increasing max-inbound-message-size = 50000000

Getting this error
An exception was thrown during the upload-dar command

  • GRPCIOTimeout
    One reason for this to occur is if the size of DAR file being uploaded exceeds the gRPC maximum message size. The default value for this is 4Mb, but it may be increased when the ledger is (re)started. Please check with your ledger operator.
    always after uploading the dar on a ledger (particpant)
    that is running as a pod in minikube cluster and upload fails mostly dar size is 5 to 5.3 mb

daml ledger upload-dar --host=127.0.0.1 --port=4001 /Users/zinnia_india/Documents/qa_deployment/deleting_daml_backup/SOR-DAML/.packages/init/.daml/dist/sor-mvp-init-1.2.22.dar

and as you can see from the image below pasted down here and our laptop/macbook ram is 18 gb
k -n canton top pods
NAME CPU(cores) MEMORY(bytes)
daml-navigator-5b77f545cd-l7vgd 14m 1565Mi
zsor-domain-canton-domain-manager-77c88dc65b-cbtkr 10m 1105Mi
zsor-domain-canton-domain-mediator-584c6bd6fc-jvpqb 11m 1053Mi
zsor-domain-canton-domain-sequencer-6bfcf5d78b-cgbw7 77m 1501Mi
zsor-participant-canton-participant-67759db88f-c66gc 25m 2293Mi

k top nodes
NAME CPU(cores) CPU(%) MEMORY(bytes) MEMORY(%)
minikube 386m 3% 9581Mi 53% ’

In some article in daml forum it is said
You don’t need to pass --address unless you are running daml start on a different machine than the one running the daml ledger fetch-dar command. In this context, VMs and Docker containers count as separate machines from each other and the host, physical machine.

so it means pod and host count as different machines