s6
The s6 supervision suite. (by skarnet)
s6-overlay
s6 overlay for containers (includes execline, s6-linux-utils & a custom init) (by just-containers)
s6 | s6-overlay | |
---|---|---|
22 | 27 | |
726 | 3,523 | |
- | 1.3% | |
7.4 | 4.6 | |
9 days ago | about 1 month ago | |
C | Shell | |
ISC License | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
s6
Posts with mentions or reviews of s6.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-27.
- OpenRC is a dependency-based init system for Unix-like systems
-
are there any good reasons for me to avoid systemd
A (rare) good critique to systemd can be found here. Written by the developer behind s6, which happens to be scheduled to replace OpenRC on Alpine Linux. For completeness-sake, some of the main reasons why Alpine doesn't prefer systemd do not apply on most other distros.
-
A discussion about the Ultimate Linux Desktop
It got mass-adopted while being imperfect, so that's to be expected. Thankfully its inception and the criticism that followed have paved the way for the likes of dinit and s6.
-
Which do you use systemd or openrc? Why do you use what you use?
this page and this page, both by Laurent Bercot, creator of s6.
-
init software: What's the difference?
Of the two I have experience with, runit is simpler and thus easier to get the hang of than s6-rc/s6. Though the s6 (not s6-rc) docs at the author's site contain a lot of info (including apologetics and rationales) that applies almost equally well to runit
-
What do you guys think about this?
systemd: Yes; it's awaiting its "PipeWire". Thankfully, the likes of s6 and dinit are very promising. Though I can actually appreciate that systemd is addressed. As ultimately it helps in raising awareness that will benefit whatever software will replace it eventually.
-
The (GNU/)Linux rabbit hole has been a negative influence on my mental state
Arguably this is less troublesome to solve compared to the other concerns. As we're inevitably waiting for the system supervision suite that will be to systemd what PipeWire has been to PulseAudio. I'm very optimistic about this as both s6 and Dinit are shaping up lovely.
- Systemd 252 Released
-
Trouble with s6 services
Using the s6-service add command I added a service called "libvertd" when I ment to put "libvirtd". Now when I run s6-db-reload it spits out a error message saying "undefined service name libvertd". But I cant remove it using s6-service remove libvertd because that just spits out a generic help message and doesn't change anything. I also couldn't find documentation on https://skarnet.org/software/s6/ or https://skarnet.org/software/s6-rc/ as the command just *doesn't* exist on those pages. (also no man or info page).
- Alpine Linux is reducing dependencies on Busybox
s6-overlay
Posts with mentions or reviews of s6-overlay.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-10-07.
- S6-overlay: one *thing* per Docker container
-
Backup Grafana SQLite with Litestream using s6-overlay in a container app
FROM docker.io/grafana/grafana-oss:9.5.12-ubuntu # Set USER to root escalating priviliges to perform installation of litestream and s6-overlay USER root RUN apt-get -qq update && \ apt-get -qq install -y xz-utils \ && rm -rf /var/libs/apt/lists/* # https://github.com/benbjohnson/litestream-s6-example/blob/main/Dockerfile # Download the static build of Litestream directly into the path & make it executable. ADD https://github.com/benbjohnson/litestream/releases/download/v0.3.11/litestream-v0.3.11-linux-amd64.tar.gz /tmp/litestream.tar.gz RUN tar -C / -xvzf /tmp/litestream.tar.gz ARG S6_OVERLAY_VERSION="3.1.5.0" # Download the s6-overlay for process supervision. ADD https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-noarch.tar.xz /tmp RUN tar -C / -Jxpf /tmp/s6-overlay-noarch.tar.xz ADD https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-x86_64.tar.xz /tmp RUN tar -C / -Jxpf /tmp/s6-overlay-x86_64.tar.xz # Copy s6 init & service definitions. COPY etc/s6-overlay /etc/s6-overlay # Copy Litestream configuration file. COPY etc/litestream.yml /etc/litestream.yml # The kill grace time is set to zero because our app handles shutdown through SIGTERM. ENV S6_KILL_GRACETIME=0 # Sync disks is enabled so that data is properly flushed. ENV S6_SYNC_DISKS=1 # Reset USER to 472 to reset the escalated privileges USER 472 # # Run the s6 init process on entry. ENTRYPOINT [ "/init" ]
-
Letme Dockerize for you | share your projects
Learn S6-Overlay that allows to have one docker container for multiple processes... make immich docker compose not a two page 8 containers long? But just one clean container with healthcheck. Convince the devs to switch to it.
-
Code-server : Awesome VS Code container on browser (Useful for Fast Cloud Deploy - Fix Corporate Issues)
Custom base docker image with S6 overlay (for more details : just-containers/s6-overlay)
-
xinetd/inetd/systemd socket services in Docker?
https://github.com/just-containers/s6-overlay can do what you need.
-
Alpine Linux is reducing dependencies on Busybox
Used s6-overlay[1] to start a lot daemons in a docker-image for demo purposes - postgres, tomcat, mysql, php-fpm, apache (don't ask why ;) - s6 worked really well and was reliable and stable - I enjoyed it very much. It was also possible to reliable pass SIGTERM to the daemons in the image for clean shutdown and it was easily possible to configure logging to stdout with a prefix. Modelling dependencies (waiting on database before starting app etc.pp) is possible via shell-scripts. It's super flexible but out of the box it's more like a collection of powerful tools not a complete package - but that's good. It's in the tradition of djb daemontools and is very unix - as in doesn't talk a lot and you better know how each part works but - and that's really cool - it's modular and simple and once you get a grip on it you can easily reason about it. systemd takes a completely different approach and also solves a kind of differnt problem - this is like small pieces of lego that compose well instead of one big chunk of glib/dbus/glibc only c-code.
1: https://github.com/just-containers/s6-overlay
-
Do Docker Containers go thru a Boot Process
Every container has some entrypoint, whether it launches a single binary, runs a "process supervisor" like s6, or does some pre-setup before running a service, like a database.
-
Docker and dedicated user
If you *really* want to make your own containers with PUID/PGID support checkout "S6-overlay" and the linuxserver "baseimage". Somewhere in the startup they end up running:
-
Docker Build Process: Archive Extract onto / (root), overwrites destination directories and contents
FROM ubuntu:20.04 ARG S6_OVERLAY_VERSION=3.1.0.1 ARG DEBIAN_FRONTEND=noninteractive ENV TZ="America/New_York" RUN apt-get update && apt-get install -y xz-utils ADD https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-noarch.tar.xz /tmp RUN tar -C / -Jxpf /tmp/s6-overlay-noarch.tar.xz ADD https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-x86_64.tar.xz /tmp RUN tar -C / -Jxpf /tmp/s6-overlay-x86_64.tar.xz RUN apt-get autoclean && rm -rf /tmp/* ENTRYPOINT ["/init"]
-
Starting a service in Dockerfile
Not sure about unbound or what have inside the pihole base image, you may try to run the service in foreground or use some tiny init service for that container (I just learnt that s6 may work for that, but you must be aware how it should be used)
What are some alternatives?
When comparing s6 and s6-overlay you can also consider the following projects:
dinit - Service monitoring / "init" system
docker-php-nginx - Docker image with PHP-FPM 8.3 & Nginx 1.24 on Alpine Linux
systemd - The systemd System and Service Manager
docker-restic-cron - Automated Restic backups from Docker
init - KISS Linux - Init Framework
laravel-docker-production
tini - A tiny but valid `init` for containers
docker
jsonnet - Jsonnet - The data templating language
k3s - Lightweight Kubernetes
hummingbird - Hummingbird init system for Linux based operating systems.
tinypilot - Use your Raspberry Pi as a browser-based KVM.