Our great sponsors
fleet | bocker | |
---|---|---|
5 | 37 | |
2,438 | 11,092 | |
- | - | |
0.0 | 0.0 | |
- | over 6 years ago | |
Go | Shell | |
- | GNU General Public License v3.0 only |
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.
bocker
-
Show HN: Bocker-compose, the missing layer to Docker-compose
A (joke?) one-liner I came up with while thinking about solutions to centralized container management across multiple SSH hosts. Shame on me.
The name is inspired by bocker [0], albeit this doesn't re-implement docker-compose in bash, I found it to be fitting enough.
I'd love to see someone come up with a smarter and/or shorter way to do this.
[0] https://github.com/p8952/bocker
-
Barco: Linux Containers from Scratch in C
When I did a talk about docker I also wanted to show a bit of what it does under the hood without going through all the layers and without too much details. This ~120 lines of shell script is really good in providing just an intro into what's needed for containers: https://github.com/p8952/bocker/blob/master/bocker
- Build Your Own Docker with Linux Namespaces, Cgroups, and Chroot
-
Latest Zen Kernel......
i tried it and like the concnpt, but until it can be launched via a systemd userspace service (without previously manually booting it) among other problems i will keep using docker (or bocker)
-
The Staff Engineer's Path – Book Review
> But you couldn't reimplement podman in a few hundred lines of code.
You don't even need a few hundred: https://github.com/p8952/bocker
And then there's 'dokku' which IIRC, started as a bash version of Heroku.
> Not all ideas have the same quality.
They really do. I've heard all kinds of things in my career, but almost none I would want to dedicate a portion of my life building. Not because they are bad ideas or won't work, but because of the person with the idea or it just didn't interest me. Those people went on to be moderately successful (like hundreds of millions worth) but I'm glad I wasn't on that ride.
-
“Implement DNS in a Weekend”
Bocker is in this same category...docker clone in bash that's helpful in seeing what's really happening underneath with nsenter, namespaces, network bridging, cgroups, etc.
https://github.com/p8952/bocker
-
Ask HN: What is the best source to learn Docker in 2023?
Docker implemented in around 100 lines of bash: https://github.com/p8952/bocker
This is the most mindblowing example for enterprise security teams that think Docker is a new threat on a single tenant Linux host.
No, buddies, all this stuff is already there. If you were fine with your visibility before*, you're still fine. Go find a real problem while we play with our developer dopamine.
* NARRATOR: They shouldn't have been.
-
Containers are chroot with a Marketing Budget
Bocker[1] does a reasonably good job of showing the value of Docker was mostly in Docker hub.
[1] https://github.com/p8952/bocker
There is a cool project I've seen called "bocker" (https://github.com/p8952/bocker) which is something of a proof of concept of implementing Docker with bash, which speaks a bit to how Docker is indeed in many ways an amalgam of lower level primitives (such as chroot as you mentioned). Pretty neat!
- bocker: Docker implemented in around 100 lines of bash
What are some alternatives?
peg - Peg, Parsing Expression Grammar, is an implementation of a Packrat parser generator.
whalebrew - Homebrew, but with Docker images
confd - Manage local application configuration files using templates and data from etcd or consul
s6-overlay - s6 overlay for containers (includes execline, s6-linux-utils & a custom init)
borg - Search and save shell snippets without leaving your terminal
garden - Automation for Kubernetes development and testing. Spin up production-like environments for development, testing, and CI on demand. Use the same configuration and workflows at every step of the process. Speed up your builds and test runs via shared result caching
orange-cat
distroless - 🥑 Language focused docker images, minus the operating system.
croc - Easily and securely send things from one computer to another :crocodile: :package:
dockerfiles - Various Dockerfiles I use on the desktop and on servers.
limetext - Open source API-compatible alternative to the text editor Sublime Text
cloc - cloc counts blank lines, comment lines, and physical lines of source code in many programming languages.