-
Notifications
You must be signed in to change notification settings - Fork 206
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
[Feature] Support other container image registries, including private ones #30
Comments
Thank you Alex! |
@KaiWedekind are your repos public and without auth, just not on docker.io, or are they also private? We have two use-cases and I’d like to support it in two steps. |
@alexellis I'm am using a self hosted GitLab and their container registry. My repos there are private. I was using this line in my .gitlab-ci.yaml to login. Ref
Build and push to the container registry works, it is just the deployment. |
Some help on using the Go API to support authenticated registry interactions: When used as a CRI provider, the CRI plugin has its own configuration for registry auth: https://github.com/containerd/cri/blob/master/docs/registry.md When using the Go client API for containerd, you can see from the |
I suspect that a nice experience might be to have users copy their The Docker config JSON file is also used in Kubernetes and can support multiple remotes. |
Thank you @estesp |
Added to Trello roadmap for 2020. |
PR #41 |
Many thanks @AkihiroSuda |
@KaiWedekind PTAL :) |
Description
Support other container image registries, including private ones
Detail
Context
Today faasd only has support for images on the docker.io/ public registry. Other backends for OpenFaaS support this feature including faas-netes and faas-swarm.
The text was updated successfully, but these errors were encountered: