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

x509: certificate signed by unknown authority #13

Open
theiosx opened this issue Oct 18, 2017 · 1 comment
Open

x509: certificate signed by unknown authority #13

theiosx opened this issue Oct 18, 2017 · 1 comment

Comments

@theiosx
Copy link

theiosx commented Oct 18, 2017

Hi, I am trying to pull a container but forced with an issue.
Google did not help me :(

Docker version 1.12.6, build 0fdc778/1.12.6
Red Hat Enterprise Linux Server release 7.4 (Maipo)

# docker pull ybalt/ansible-tower
Using default tag: latest
Trying to pull repository registry.access.redhat.com/ybalt/ansible-tower ... 
Trying to pull repository registry.access.redhat.com/ybalt/ansible-tower ... 
Trying to pull repository docker.io/ybalt/ansible-tower ... 
sha256:a558fe26f8fe2420179bacc68e37f8e9e5cd0975507f194e55cdc8e880e3e3a7: Pulling from docker.io/ybalt/ansible-tower
cb56c90f0b30: Pulling fs layer 
0acc551e5716: Pulling fs layer 
8956dcd35143: Pulling fs layer 
908242721214: Waiting 
b44ff14dd3bb: Waiting 
39c5609e9c63: Waiting 
b6108ff4be91: Waiting 
572cdcfffef9: Waiting 
52757e050d59: Waiting 
fabf16e8e4f8: Waiting 
cdd2c0aa93f6: Waiting 
2f4347d07034: Waiting 
374614a06a1b: Waiting 
58e3a6a0326c: Waiting 
751d8b6dae4c: Waiting 
error pulling image configuration: Get https://dseasb33srnrn.cloudfront.net/registry-v2/docker/registry/v2/blobs/sha256/1d/1dac20c66caa8adc07a4cdbae91702fca8d96d648bda3dc5a96ae6a18155bf5a/data?Expires=1508323432&Signature=RYTj1qOf6mVB-yjtgmkQTA17a9BcFnSw48ww3wGXFEd0VvSn4U9JETOWsYglGMeEuFP9lv3CAfkuG9F1QCoZ3hFdZqby6NZoZhji855Q8XN5uBOIuvfEGpxj5jj7gW0mCYv2fk~1NWdvTrk9wAgxrnbOaZZnkQNn~g0DTbSxncQ_&Key-Pair-Id=APKAJECH5M7VWIS5YZ6Q: x509: certificate signed by unknown authority

Regards
iOsX

@arnabsinha4u
Copy link
Contributor

@theiosx Please check the certsd directory. This occurs when certs are not correctly deployed and docker daemon does not pick it up. Post making changes, dont forget to restart the daemon.

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

2 participants