Why does a device need access to *.docker.com, *.docker.io

I am also trying to simplify the firewall requirements that I have to impose on customers. I first created our own Network Requirements back in August 2020, at the time docker.com and docker.io were on that list (although I can’t remember how they got on the list).

I can also see as noted above that it isn’t referenced in Network Setup on balenaOS - Balena Documentation

Please could @alanb128 or @alexgg (based on this post) confirm definitively that these domains are no longer needed for Balena devices to function and pull any container images? I assume the Balena team have moved to using a custom balena-cloud.com subdomain for the container image downloads?

Thanks