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

Connection refused for non-TLS registry URL #977

Closed
nonetheless opened this issue Jan 19, 2020 · 3 comments
Closed

Connection refused for non-TLS registry URL #977

nonetheless opened this issue Jan 19, 2020 · 3 comments
Labels
area/registry For all bugs having to do with pushing/pulling into registries in progress priority/p1 Basic need feature compatibility with docker build. we should be working on this next.

Comments

@nonetheless
Copy link

Actual behavior
When I use kaniko to build image and push it to a local registry (xx.xx.xx.xx:5000/tag:version), it will refuse the connection.
We should upgrade go-containerregistry version to deal it.

google/go-containerregistry@4711a5d

Expected behavior
A clear and concise description of what you expected to happen.

To Reproduce
Steps to reproduce the behavior:

  1. ...
  2. ...

Additional Information

  • Dockerfile
    Please provide either the Dockerfile you're trying to build or one that can reproduce this error.
  • Build Context
    Please provide or clearly describe any files needed to build the Dockerfile (ADD/COPY commands)
  • Kaniko Image (fully qualified with digest)

Triage Notes for the Maintainers

Description Yes/No
Please check if this a new feature you are proposing
Please check if the build works in docker but not in kaniko
Please check if this error is seen when you use --cache flag
Please check if your dockerfile is a multistage dockerfile
@tejal29 tejal29 added the area/registry For all bugs having to do with pushing/pulling into registries label Jan 22, 2020
@tejal29 tejal29 added this to the GA Release v1.0.0 milestone Jan 22, 2020
@tejal29 tejal29 added priority/p1 Basic need feature compatibility with docker build. we should be working on this next. in progress labels Jan 22, 2020
@tejal29
Copy link
Contributor

tejal29 commented Jan 22, 2020

Thanks looks like you already have a pr in progress.
Thanks

@antechrestos
Copy link
Contributor

@nonetheless @tejal29 I think that this issue is already fixed by #957 as I upgraded to the commit 34fb8ff which is more recent that 4711a5d

@tejal29
Copy link
Contributor

tejal29 commented Mar 18, 2020

Thanks @antechrestos for confirming!

@tejal29 tejal29 closed this as completed Mar 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/registry For all bugs having to do with pushing/pulling into registries in progress priority/p1 Basic need feature compatibility with docker build. we should be working on this next.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants