On Mon, Mar 23, 2015 at 10:27 AM, Aristomenis Pikeas <pikeas_at_gmail.com> wrote:
> 3) I understand the reasons behind breaking S6 up into a large set of simple utilities, but the current state of affairs is pretty extreme. ;ss /usr/bin |grep s6-* | wc -l reports 55 different utilities. Have you considered breaking s6 up into multiple packages, for
I agree with this point. However it seems most of those little
programs don't hurt if they are left un-used. It means fewer problems
to create just one full and complete release of 's6-overlay'. Then
have to also maintain a 'lite' version too, with some fewer minimum
tools.
> 5) For major distributions and usage mediums (Ubuntu, docker, OS X, and perhaps Alpine/busybox), the docs should provide clearer steps for installation and usage.
Nobody has really had time to document the 's6-overlay' yet. But you
can try it by adding a few extra lines to your dockerfile. And please
start help testing it:
# Install s6-overlay
ADD
https://github.com/just-containers/s6-overlay-builder/releases/download/v1.8.4/s6-overlay-linux-amd64.tar.gz
/tmp/
RUN tar zxf /tmp/s6-overlay-linux-amd64.tar.gz -C / && rm
/tmp/s6-overlay-linux-amd64.tar.gz
ENTRYPOINT ["/init"]
> 9) This has already been discussed a bit, but I'd like to add another vote for allowing s6-svscan to run a command. As others have
Gorka and Laurent have implemented that feature especially for docker
in the 's6-overlay' project. It works well. Please try.
Received on Mon Mar 23 2015 - 11:03:41 UTC