-
Notifications
You must be signed in to change notification settings - Fork 568
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
Job images can only be pulled from the Docker Registry #24
Comments
One question I have, is it working with privately-run Docker registries. If so, why not having Pachyderm to run their own registry at least in one node? I see a Also, that raises more questions, like should the registry work in high availability mode in the cluster? If not, maybe a Paxos-based approach might work. Or maybe by pulling the docker files from git could remove the need for the docker registry? Sorry if what I'am saying is nonsense, the project just looks really amazing and I got excited :) |
@versae We're thrilled that it excites you so much. Us too! :) We're about to push out pfs v0.4 in the next few hours and I think you'll really like it. It includes support for privately-run docker registries inside the cluster and it's in high-availability mode by default. We also will be rolling out a pretty in-depth integration with git that includes pulling docker files and bunch more cool stuff. |
This has been fixed for a while. You can pull containers from any registry you'd like. We had to temporarily unsupport the registry in the cluster due to some annoyances with certificates. |
* Increment version for 0.1.0-alpha release * Update CHANGELOG.md for 0.1.0-alpha release
No description provided.
The text was updated successfully, but these errors were encountered: