-
Notifications
You must be signed in to change notification settings - Fork 76
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
Registry no longer exists for byoh provider #894
Comments
@dharmjit @jamiemonserrate @shivi28 Hello contributors, could you take a look at this? I guess the last commit to this project was 7 months ago. If it is, it would be great to inform the status of the project to others. Thank you. |
|
Apologies for the delay in responding folks. But this project is no longer being maintained. |
Does anyone know if there are provisioners that are supported which provide the same functionality as this one? |
Until someone adopts the project (let's hope), you can easily build your own
Push the resulting image to a registry, update the image reference in your |
What do you mean by adopt? Is there a process for adoption? I thought one would just fork it. |
What steps did you take and what happened:
It looks like some point in the past 4/5 days, the byoh provider images are no longer served by
projects.registry.vmware.com
:This issue implies there were some changes to the registry around that time. Please could you provide an alternative registry for the existing images?
What did you expect to happen:
For the docker pull to work.
Anything else you would like to add:
N/A
Environment:
N/A
The text was updated successfully, but these errors were encountered: