-
Notifications
You must be signed in to change notification settings - Fork 42
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
specify required permissions on quay configuration files (PROJQUAY-6517) #137
Conversation
Any thoughts @HammerMeetNail or @jonathankingfc ? Sorry to tag y'all directly, but with no contributing.md I'm not sure if I'm missing any steps, and would love to get either this merged, or a better path forward for ourselves & others affected by this issue. (#136) |
@BadgerOps Thanks for the PR, I just triggered CI. When you get a moment, can you rebase the branch? |
914f96b
to
552ddbe
Compare
Actually, ignore that request, I was able to do it without any conflicts. |
Thanks for jumping on this @HammerMeetNail ! Happy to help the next person who's working in a fun environment 🤣 |
Hey, yeah, we talked about this today. I believe @harishsurf will be picking this up and reviewing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
552ddbe
to
709683e
Compare
/retest |
As mentioned in #136 with a hardened RHEL 8 instance with global umask of
0077
the mirror-registry fails to install, due to the quay pod not being able to access the{{ quay_root }}/quay-config
directory.This PR adds explicit mode for the directory and
config.yaml
to allow a successful offline quay install with mirror-registry on a hardened environment.