I cannot push my Docker container no matter what I try

[alpbintug]

I have a custom container that I'm trying to push but I am having errors with it.

When I first create a build, I get this error while pushing;

The push refers to repository [ghrc.io/alpbintug/bounhpccontainer]
5324914b4472: Layer already exists
e2554c2d377e: Layer already exists
a20dbc6c2cf4: Already exists
8054e9d6e8d6: Layer already exists
95eef45e00fa: Layer already exists
9e2de25be969: Layer already exists
bdddd5cb92f6: Layer already exists
0954b8076bb8: Layer already exists
4640d022dbb8: Layer already exists
aa750c79a4cc: Layer already exists
533a0a0442af: Layer already exists
86b19790fb81: Layer already exists
5aa98f172ba0: Layer already exists
9fe5ccccae45: Layer already exists
aece8493d397: Layer already exists
9a9dd462fc4c: Layer already exists
50f6b1e6ae94: Layer already exists
a60649e2fc0d: Layer already exists
unexpected status from HEAD request to https://ghrc.io/v2/alpbintug/bounhpccontainer/manifests/0.0.1: 429 Too Many Requests

But after I try to push the same build I get the following error;

The push refers to repository [ghrc.io/alpbintug/bounhpccontainer]
9e2de25be969: Waiting
aa750c79a4cc: Waiting
9a9dd462fc4c: Waiting
95eef45e00fa: Waiting
e2554c2d377e: Waiting
a60649e2fc0d: Waiting
50f6b1e6ae94: Waiting
5aa98f172ba0: Waiting
4640d022dbb8: Waiting
0954b8076bb8: Waiting
9fe5ccccae45: Waiting
86b19790fb81: Waiting
5324914b4472: Waiting
a20dbc6c2cf4: Waiting
aece8493d397: Waiting
533a0a0442af: Waiting
8054e9d6e8d6: Waiting
bdddd5cb92f6: Waiting
failed to do request: Head "https://ghrc.io/v2/alpbintug/bounhpccontainer/blobs/sha256:0954b8076bb83592b6bbe7911f6038d07e5d970266ac2b124a3313ea469bb599": malformed MIME header: missing colon: "bağlantı bağlanılan ana bilgisayar yanıt vermediğinden bir bağlantı kurulamadı."

Also, I am having trouble logging in to the ghrc.io, 80% of my login request are denied by the following error;

Error response from daemon: Get "https://ghrc.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

I also get this error while trying to login;

Error response from daemon: Get "https://ghrc.io/v2/": context deadline exceeded

I'm using Docker Desktop for Windows and using Google DNS on my PC. I don't have any private networking or not using any VPN services.

What can I do to fix this?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐