Private endpoint based storage account being accessed by custom docker edge transfer container whose IP are not whitelisted on the firewall rules of storage account

I have storage account with private endpoint setup and whitelisted IP of the edge device public IP in the firewall rules of the same. To copy data from the edge device to storage account there is a custom docker image based on GitHub code Iotedge file watcher that uses connection string and container name. This custom docker containers are used to upload data to private storage account using connection string and container name taken from the deployment manifest on IoT central devices. This docker containers along with iotedge agent and iotedge hub are on different network that host and their IP are not whitelisted in firewall rules of storage account. The only host IP and allow microsoft services/IoT apps are setup on the firewall of the storage account. Yet custom docker containers have accessed the blob container on this account and uploaded data in it. I am confused did the private endpoint setting not work ?