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

Not build from Dockerfile with insecure registry #126

Open
DmitriyMurzin opened this issue Jun 15, 2018 · 4 comments
Open

Not build from Dockerfile with insecure registry #126

DmitriyMurzin opened this issue Jun 15, 2018 · 4 comments

Comments

@DmitriyMurzin
Copy link

DmitriyMurzin commented Jun 15, 2018

IMG not build from Dockerfile with insecure registry in section FROM

Dockerfile:
FROM http://registry.local.com:5000/glassfish-app:88

Error:
failed to solve: invalid reference format

or

Dockerfile:
FROM registry.local.com:5000/glassfish-app:88

Error:

 => ERROR docker-image://registry.local.com:5000/glassfish-app:88 
failed to solve: failed to do request: Head https://registry.local.com:5000/v2/glassfish-app/manifests/88: http: server gave HTTP response to HTTPS client
@jessfraz
Copy link
Collaborator

Can you not add self signed certs, we have info in the docs :) insecure is v bad

@jessfraz jessfraz reopened this Jun 15, 2018
@DmitriyMurzin
Copy link
Author

Im love insecure local registry!((

@ekristen
Copy link

@jessfraz I would love to see --insecure-registry flags on build and pull too! It's especially helpful for local development and testing when I don't want to put nginx or something else in front of the registry to serve https.

@Constantin07
Copy link

I agree, in local development/testing generating self signed certs is an overhead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants