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

Fixes #38: Using persistent volume to hold registry data #78

Merged
merged 2 commits into from
Apr 24, 2020

Conversation

parauliya
Copy link
Contributor

In this fix we are using "/var/tinkerbell/registry" directory locally to persist the data of private registry we are creating to have worker and action images.

@parauliya parauliya changed the title Fix for Issue#38: Using persistent volume to hold registry data Fixes #38: Using persistent volume to hold registry data Apr 24, 2020
In this fix we are using "/var/tinkerbell/registry" directory locally to persist the data of registry
@gauravgahlot
Copy link
Contributor

@parauliya Can you rebase the branch, please?

@parauliya parauliya linked an issue Apr 24, 2020 that may be closed by this pull request
@parauliya
Copy link
Contributor Author

@parauliya Can you rebase the branch, please?

Done. Branch Updated.

@mmlb
Copy link
Contributor

mmlb commented Apr 24, 2020

This seems fine, though I don't like to assume we can grab a dir in /var. It would be nice to have support for a $PREFIX or similar so users can tailor where our files/dirs land. I'll open that up as a separate issue though.

@nathangoulding nathangoulding merged commit 42d5255 into tinkerbell:master Apr 24, 2020
@parauliya parauliya deleted the fix_issue_38 branch May 21, 2020 11:02
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

Successfully merging this pull request may close these issues.

Use persistent volume to hold registry data
4 participants