English
« Back to projectatomic.io
Ask Your Question
0

atomic registry not working

asked 2017-05-17 09:20:34 +0000

chamindu gravatar image

I followed the quick start guide to install the atomic registry on an EC2 instance. After installation I cannot login to the web console. I get redirected to the oauth server and after entering any username and password it redirects back to the console with token but it says access denied. The logs contain the below messages

May 17 09:12:32 ip-172-31-8-203.us-west-2.compute.internal dockerd-current[5747]: I0517 09:12:32.262825 1 scheduler.go:160] Failed to schedule pod: default/docker-registry-1-deploy May 17 09:12:32 ip-172-31-8-203.us-west-2.compute.internal atomic-registry-master[11798]: I0517 09:12:32.262825 1 scheduler.go:160] Failed to schedule pod: default/docker-registry-1-deploy May 17 09:12:48 ip-172-31-8-203.us-west-2.compute.internal dockerd-current[5747]: 2017/05/17 09:12:48 Couldn't get user data: 403 Forbidden May 17 09:12:48 ip-172-31-8-203.us-west-2.compute.internal atomic-registry-console[11799]: 2017/05/17 09:12:48 Couldn't get user data: 403 Forbidden

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2017-06-13 17:53:58 +0000

jberkus gravatar image

There are some known issues around OATH in the current registry release. For now, we recommend using the all-in-one OpenShift Registry instead: http://www.projectatomic.io/blog/2017...

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Question Tools

Follow
1 follower

Stats

Asked: 2017-05-17 09:20:34 +0000

Seen: 702 times

Last updated: Jun 13