docker-volume-hetzner
nydus
Our great sponsors
| docker-volume-hetzner | nydus | |
|---|---|---|
| 5 | 3 | |
| 102 | 1,091 | |
| - | 5.2% | |
| 7.5 | 9.3 | |
| 26 days ago | 2 days ago | |
| Go | Rust | |
| MIT License | 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.
docker-volume-hetzner
-
Can any Hetzner user, please explain there workflow on Hetzner?
we use https://github.com/costela/docker-volume-hetzner which is really stable.
CSI support for Swarm is in beta as well and already merged in the Hetzner CSI driver (https://github.com/hetznercloud/csi-driver/tree/main/deploy/...). There are some rough edges atm with Docker + CSI so I would stick with docker-volume-hetzner for now for prod usage.
Disclaimer: I contributed to both repos.
- Hetzner Cloud - is Volumes reliable? With Volumes mounted as /var/lib/docker for example
-
For Swarm mode users: What features do you miss/need from Kubernetes ecosystem?
The big one which would be nice: CSI support. This is currently being worked on, though. This said the current volume plugin landscape is not that dire once you realize that the local volume driver which arguably has a confusing name can work with NFS,CIFS,etc. out of the box as long as you can use fuse mounts. Besides that, we are quite happy with our setup where we use the community volume driver for our cloud provider - https://github.com/costela/docker-volume-hetzner/
-
Ask HN: Have You Left Kubernetes?
6. Volumes: Hetzner Cloud Plugin, see https://github.com/costela/docker-volume-hetzner
Reasons that we would dabble in k8s again:
1. A lot of projects are k8s only (see OpenFaaS for example)
- I do like it
nydus
-
Ask HN: Have You Left Kubernetes?
If you're pulling big images you could try kube-fledged (it's the simplest option, a CRD that works like a pre-puller for your images), or if you have a big cluster you can try a p2p distributor, like kraken or dragonfly2.
Also there's that project called Nydus that allows starting up big containers way faster. IIRC, starts the container before pulling the whole image, and begins to pull data as needed from the registry.
https://github.com/senthilrch/kube-fledged
https://github.com/dragonflyoss/Dragonfly2
https://github.com/uber/kraken
https://nydus.dev/
- Increase the speed of NPM install by more than 8 times
-
new "EROFS over Fscache" Linux container image architecture for CNCF Dragonfly Nydus
Nydus-fscache user guide: https://github.com/dragonflyoss/image-service/blob/master/docs/nydus-fscache.md
What are some alternatives?
plural - Deploy open source software on Kubernetes in record time. 🚀
awesome-hcloud - A curated list of awesome libraries, tools, and integrations for Hetzner Cloud
k8s-config-connector - GCP Config Connector, a Kubernetes add-on for managing GCP resources
crossplane - The Cloud Native Control Plane
swarmsible - Ansible based Tooling and production grade example Docker Stacks. Updated with new learnings from running Docker Swarm in production
cli - A command-line interface for Hetzner Cloud
Dragonfly2 - Dragonfly is an open source P2P-based file distribution and image acceleration system. It is hosted by the Cloud Native Computing Foundation (CNCF) as an Incubating Level Project.
docker-volume-sshfs - sshfs docker volume plugin
terraform-cdk - Define infrastructure resources using programming constructs and provision them using HashiCorp Terraform
swarmsible-hetzner - Companion repository for https://github.com/neuroforgede/swarmsible with a focus on usage in the Hetzner cloud
external-dns - Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services