nomad-driver-containerd
charts
nomad-driver-containerd | charts | |
---|---|---|
2 | 30 | |
205 | 1,367 | |
2.0% | - | |
2.3 | 9.7 | |
9 days ago | over 1 year ago | |
Go | Smarty | |
GNU General Public License v3.0 or later | 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.
nomad-driver-containerd
-
Running Nomad for a Home Server
Author (https://github.com/Roblox/nomad-driver-containerd) here.
Not really, Podman and containerd are two different technologies, although both allow you to move away from Docker for various reasons (smaller CPU, memory footprint, better security etc). If you are invested into Red Hat container stack, podman makes more sense. However containerd is more universal.
K8s is already moving away from docker, and directly into containerd. Most recently they deprecated dockershim, and users now need to switch to containerd (since docker also uses containerd under the hood, and it doesn't make sense for the orchestration system to run a monolithic service like docker where it just need to launch the workloads)
Some reference links of k8s or PaaS build on top of k8s moving to containerd
charts
- Helm charts that bundles basic home server apps?
-
Getting Started with Kubernetes Questions
Spinning up workloads in kubernetes is much different than just spinning up a container in docker or even with docker compose. If someone has not already packaged it in a helm chart or some other kubernetes workload you'll have to develop one yourself. There are some nice library charts you can use as a base that should handle just about any random docker image you want to deploy. https://github.com/bjw-s/helm-charts/tree/main/charts/library/common there is also a repo of pre developed charts for common images. https://github.com/k8s-at-home/charts but be aware it was recently deprecated so it won't be receiving any updates.
-
Advice on system design best practices?
Take a look at https://github.com/k8s-at-home/charts (recently deprecated but still a fantastic resource) - there are charts for the popular Arrs , tools, etc. You could deploy each chart individually into a namespace, or you could create yourself an "umbrella" chart which pulls in all the necessary charts as dependencies.
-
With multiple custom apps, how do you manage your Helm charts?
Library charts. A very thorough example can be seen here and usages of it here.
-
Running into a problem with the k8s-at-home pod-gateway where the gateway-init container that's bootstrapping selected namespaces is unable to reach cluster DNS while pods in other namespaces can. Anyone run into this before?
Could it be related to this? https://github.com/k8s-at-home/charts/pull/1435/files
-
Struggling with Fireflyi-III installation
I'd submitted a helm chart at https://github.com/k8s-at-home/charts/tree/master/charts/stable/firefly-iii if you want to try out
- Plex on Kubernetes with hardware decoding... Victory
-
[Help!] K3s Sonarr failing with X509CertificateValidationService due to expired LetsEncrypt cert in Mono
I know /u/stefantigro means well but the way you are both doing the helm charts is not ideal, helm charts are meant to be shared, not as a means to install apps into your cluster from a local folder. While they can be, it's not a good pattern. Take the helm chart from here for example. This is a published helm chart you can install using the commands in the Readme and you only need to provide the configuration for your instance from the values.yaml file. You can take a look at the values I use for this helm chart here. You can also see I'm using an custom Sonarr image, this image is tailored to running in Kubernetes
-
Bounty for Homebridge TrueChart
There is a working Helm chart for k8s-at-home that should be a good starting point. The biggest hurdle I see is that homebridge can conflict with SCALE's mDNS service as seen in this linked post.
-
Been self-hosting close to half a year now. All running on a k3s cluster of raspberry pis. Thank you to this subreddit for all the help and great ideas!
There's an actual helm chart published here.
What are some alternatives?
nerdctl - contaiNERD CTL - Docker-compatible CLI for containerd, with support for Compose, Rootless, eStargz, OCIcrypt, IPFS, ...
truecharts - Community App Catalog for TrueNAS SCALE [Moved to: https://github.com/truecharts/charts]
pirsch - Pirsch is a drop-in, server-side, no-cookie, and privacy-focused analytics solution for Go.
kube-plex - Scalable Plex Media Server on Kubernetes -- dispatch transcode jobs as pods on your cluster!
k0s - k0s - The Zero Friction Kubernetes
MagicMirror - MagicMirror² is an open source modular smart mirror platform. With a growing list of installable modules, the MagicMirror² allows you to convert your hallway or bathroom mirror into your personal assistant.
gocast - GoCast is a tool for controlled BGP route announcements from a host
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
Fly CDN - A set of useful libraries for Edge Apps. Run locally, write tests, and integrate it into your deployment process. Move fast and maybe don't break things? Because, gosh darnit, you're an adult.
frigate - Frigate is a tool for automatically generating documentation for your Helm charts
hcl - HCL is the HashiCorp configuration language.
kubevirt - Kubernetes Virtualization API and runtime in order to define and manage virtual machines.