1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Hello.
Looking at the issue below, it seems that you cannot pull images from ECR with IPv6 only.
I don't think the reason why IPv6 cannot be used has been made public.
I think AWS will probably support this in the future, but for now I think it's best to make ECR accessible via IPv4.
https://github.com/aws/containers-roadmap/issues/1340
Contenus pertinents
- demandé il y a 2 ans
- demandé il y a 2 ans
- demandé il y a 14 heures
- demandé il y a 4 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 10 mois
- Comment autoriser les tâches Amazon ECS à extraire des images d’un référentiel d’images Amazon ECR ?AWS OFFICIELA mis à jour il y a 7 mois
Thank you so much! Just a side note, now I have an interesting dilemma. AWS is starting to charge public IPv4 addresses at 1st February 2024. They want to encourage the acceleration of IPv6 adoption. That's why I'm here and considering the IPv4 pricing (not insignificant) I will do just that, stick with IPv6 only and replace ECR with some alternative unfortunately. I'm hoping AWS will add IPv6 support to ECR as soon as possible.
It's unfortunate that AWS charges for the use of IPv4 addresses and NAT gateways and doesn't support IPv6 in many of its services, making the transition to IPv6 impossible.