cachemachine
docker-volume-hetzner
| cachemachine | docker-volume-hetzner | |
|---|---|---|
| 1 | 5 | |
| 5 | 102 | |
| - | - | |
| 3.4 | 7.5 | |
| about 1 year ago | 9 days ago | |
| Python | Go | |
| MIT License | MIT License |
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.
cachemachine
-
Ask HN: Have You Left Kubernetes?
> we found the start times with Kubernetes too slow
Just curious if you could elaborate here? I work with k8s on docker, and we're also going to be spinning up ephemeral containers (and most of the other things you say) with jupyter notebooks. We're all in on k8s, but since you might be ahead of me, just wondering what hurdles you have faced?
Our big problem was fetching containers took too long since we have kitchen sink containers that are like 10 GB (!) each. They seem to spin up pretty fast though if the image is already pulled. I've worked on a service that lives in the k8s cluster to pull images to make sure they are fresh (https://github.com/lsst-sqre/cachemachine) but curious if you are talking about that or the networking?
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
What are some alternatives?
nydus - Nydus - the Dragonfly image service, providing fast, secure and easy access to container images.
plural - Deploy open source software on Kubernetes in record time. 🚀
k8s-config-connector - GCP Config Connector, a Kubernetes add-on for managing GCP resources
awesome-hcloud - A curated list of awesome libraries, tools, and integrations for Hetzner Cloud
crossplane - The Cloud Native Control Plane
cli - A command-line interface for Hetzner Cloud
docker-volume-sshfs - sshfs docker volume plugin
swarmsible-hetzner - Companion repository for https://github.com/neuroforgede/swarmsible with a focus on usage in the Hetzner cloud
glusterfs-volume - Docker volume plugin on glusterfs
spire - Bugout knowledgebase module.