playground
Harbor
playground | Harbor | |
---|---|---|
1 | 74 | |
- | 22,643 | |
- | 2.7% | |
- | 9.7 | |
- | 3 days ago | |
Go | ||
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
playground
-
Let's make faster Gitlab CI/CD pipelines – From 14 to 3 mins
The dependency proxy in GitLab can help with caching the Docker images.
https://docs.gitlab.com/ee/user/packages/dependency_proxy/
When Docker Hub introduced rate limits last year, one way to mitigate its impact was to make the dependency proxy available for everyone.
https://about.gitlab.com/blog/2020/10/30/mitigating-the-impa...
https://about.gitlab.com/blog/2020/10/30/minor-breaking-chan...
Another way can be maintaining your own group which maintains all base images for your environment, and stores them in the GitLab package registry.
Using your own images can help enforce security policies, to avoid that containers introduce vulnerabilities (e.g. when always pulling :latest tag, or sticking to old tags). Reminds me of Infrastructure as Code security scanning, which can help detect things like this. Played with it when released in GitLab 14.5, examples in https://gitlab.com/gitlab-de/playground/infrastructure-as-co... + https://gitlab.com/gitlab-de/playground/infrastructure-as-co...
Depending on the languages and environments involved, builder images might be needed to reduce complexity with installing build tools. Like, C++ with gcc and controlling the exact version being used (major versions may introduce ABI breaking changes, I've seen it with armhf and gcc6 a while ago). Builder images also reduce the possibly for users to make mistakes in CI/CD before_script/script sections. An optimized pipeline may just include a remote CI/CD template with the magic happening in central maintained projects, using the builder images.
Another thought on builder images - multi arch images with buildx. I've read https://medium.com/@tomwillfixit/migrating-a-dockerized-gitl... yesterday, need to learn more :)
Harbor
-
Docker Private Registry using Harbor
cat << EOF wget \ https://github.com/goharbor/harbor/releases/download/v2.9.4/\ harbor-offline-installer-v2.9.4.tgz EOF
-
Signing container images: Comparing Sigstore, Notary, and Docker Content Trust
Now that you know a little more about Cosign, Notary, and DCT, we will take it one step further by using one of these tools: Cosign. For this example, we will use the simple Docker registry:2 reference image to run a simple registry. In a real-world scenario, a managed registry such as Harbor, Amazon ECR, Docker Hub, etc.
- Docker pull through cache to multiple upstreams, that you can also push to
-
tcp i/o timeout when installing network plugin in "high secure environment"
Have a look at harbor, you can also use it to follow the same methods for helm charts etc.
-
How to build a docker image and still use Watchtower
Or for something more advanced https://goharbor.io/
-
Scan selfhosted docker images for vulnerabilities automatically
Look at https://goharbor.io/
-
Docker has reversed its decision to sunset the “Docker Free Team” plan.
You can host your own image repo if your feeling feisty. Harbor is a graduated project from the CNCF and they are also working on a new implementation called Dragonfly. https://goharbor.io/
- We're no longer sunsetting the Free Team plan | Docker
-
Docker's deleting Open Source images and here's what you need to know
Does anybody know whether there could be something like an open/libre container registry?
Maybe the cloud native foundation or the linux foundation could provide something like this to prevent vendor lock-ins?
I was coincidentially trying out harbor again over the last days, and it seems nice as a managed or self-hosted alternative. [1] after some discussions we probably gonna go with that, because we want to prevent another potential lock-in with sonarpoint's nexus.
Does anybody have similar migration plans?
[1] https://goharbor.io
-
Iron Bank: Secure Registries, Secure Containers
2) Harbor instance registry
What are some alternatives?
gitlab
Portainer - Making Docker and Kubernetes management easy.
gitlab-runner
Dragonfly - This repository has be archived and moved to the new repository https://github.com/dragonflyoss/Dragonfly2.
workshops
phoneinfoga - Information gathering framework for phone numbers
chartmuseum - helm chart repository server
distribution - The toolkit to pack, ship, store, and deliver container content
ingress-nginx - Ingress-NGINX Controller for Kubernetes
Docker Swarm - Source repo for Docker's Documentation
clair - Vulnerability Static Analysis for Containers