- Newest
- Most votes
- Most comments
There was plenty of free RAM, almost no CPU usage, plenty of bandwidth (12.5 GBit/sec connection). The issue is not instance resources.
As you cited correctly it does not seems related to linux and docker version.
There can be multiple factors while pushing the image, like instance resources, bandwidth etc. As reboot was solving issue, i suspect the resource crunch may be issue earlier.
However to check and narrow down, can you try checking with higher instance type (which comes with more bandwidth -> https://aws.amazon.com/ec2/instance-types/ bandwidth is mentioned for each instance type).
when push is slow, can you check instance metrics and instance state using TOP, free -m commands and see if there is resource crunch.
Hi,
I have faced this issue a couple of times, and the last time I did, I found that I was executing three VPN clients in background, none of them were actually connected to any VPN though.
Once I closed them, I restared Docker daemon, and the speed came back. Push was normal after that.
See if that's your case too.
Cheers.
-- Álvaro
Relevant content
- asked 5 years ago
- asked 2 days ago
- asked 7 months ago
- AWS OFFICIALUpdated 4 days ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago