fleet
nomad-driver-nspawn
Our great sponsors
fleet | nomad-driver-nspawn | |
---|---|---|
5 | 1 | |
2,438 | 50 | |
- | - | |
0.0 | 4.8 | |
- | 6 days ago | |
Go | Go | |
- | 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.
fleet
-
The 2024 Web Hosting Report
Docker didn’t have a default way to run on multiple hosts, and so in the wake of docker’s explosive adoption there was a rush of different solutions offered for scheduling containers across a fleet. One of the first well-adopted solutions was actually called fleet - it was part of CoreOS, whose team went on to be very influential throughout the container revolution. This was in the systemd era, and was basically seen as a multi-host systemd. It was very cool and it worked great!
-
The Container Orchestrator Landscape
Figure out how to revive https://github.com/coreos/fleet as something native in systemd?
-
Kubernetes is just Systemd distributed just like /etc is ETCD(istributed)
I guess what in trying to say is k8s is systemd distributed but more then. I see how in line fleet and systemd is though https://github.com/coreos/fleet/blob/master/Documentation/fleet-k8s-compared.md
-
We Don’t Use Docker (We Don’t Need It)
What you describe is essentially the original CoreOS fleet[0] project. It's distributed systemd init files.
[0] https://github.com/coreos/fleet#fleet---a-distributed-init-s...
I find it ironic half of k8s mojo, etcd, came out of this project as well.
nomad-driver-nspawn
-
We Don’t Use Docker (We Don’t Need It)
> Now imagine if only you could schedule to run systemd units using Nomad
With some tweaks to your unit files this is actually possible. Nomad has the concept of custom task drivers you can implement to make it schedule any kind of workload you like. I am maintaining a task driver which allows you to run systemd-nspawn containers with Nomad [1].
Using this task driver you can deploy your systemd units running inside a systemd-nspawn container into a Nomad cluster. If this sounds interesting to you I have written a how-to blog-post about this [2]
[1]: https://github.com/JanMa/nomad-driver-nspawn
What are some alternatives?
peg - Peg, Parsing Expression Grammar, is an implementation of a Packrat parser generator.
s6-overlay - s6 overlay for containers (includes execline, s6-linux-utils & a custom init)
confd - Manage local application configuration files using templates and data from etcd or consul
microprocessor-trend-data - Data repository for my blog series on microprocessor trend data.
borg - Search and save shell snippets without leaving your terminal
caxa - 📦 Package Node.js applications into executable binaries 📦
orange-cat
litestream - Streaming replication for SQLite.
croc - Easily and securely send things from one computer to another :crocodile: :package:
parsemail - Hanami fork of https://github.com/DusanKasan/parsemail
limetext - Open source API-compatible alternative to the text editor Sublime Text
bocker - Docker implemented in around 100 lines of bash