Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERRO[0001] retrying read tcp x.x.x.x:nnnnn->131.253.33.219:443: read: connection reset by peer #9429

Open
cyraid opened this issue May 29, 2024 · 0 comments

Comments

@cyraid
Copy link

cyraid commented May 29, 2024

Expected behavior

No connection reset by peer messagers.

Actual behavior

When doing skaffold dev (happens on build I think too), during this phase:

Generating tags...
 - registry.gitlab.com/some/url-> ERRO[0001] retrying read tcp x.x.x.x:nnnnn->131.253.33.219:443: read: connection reset by peer 
registry.gitlab.com/some/url:debug-72c0d9df550ccc32f27264f3409d99259e7f011bde37b761bc651e26861141a1
Checking cache...

When going to http://131.253.33.219 I get:

<h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0f0xXZgAAAACQkR9ESn9ZR4NQX88z+lYRQ0gxQUEyMDIwNjE2MDI1AEVkZ2U=

It looks to be a Microsoft Services message as far as I'm seeing online? Possibly Azure? Is it skaffold attempting to connect to a microsoft service? Is it telemetry? 'Cause when I disable telemetry it seems to have gone away (so far anyway). Still happens when telemetry is disabled.

Information

  • Skaffold version: 2.12.0
  • Operating system: Windows 11 (but using WSL2)
  • Installed via: CURL if I remember.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant