From 7d3da2acd77c71daeb6665f2b2ec278d659fe8c7 Mon Sep 17 00:00:00 2001 From: John Regan Date: Fri, 15 Apr 2016 09:19:47 -0500 Subject: [PATCH] Updating README for issue #144 --- README.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/README.md b/README.md index 239d490..c7c3891 100644 --- a/README.md +++ b/README.md @@ -15,6 +15,8 @@ - [Dropping privileges](#dropping-privileges) - [Container environment](#container-environment) - [Customizing `s6` behaviour](#customizing-s6-behaviour) +- [Known issues and workarounds](#known-issues-and-workarounds) + - [`/bin` and `/sbin` are symlinks](#bin-and-sbin-are-symlinks) - [Performance](#performance) - [Verifying Downloads](#verifying-downloads) - [Notes](#notes) @@ -331,6 +333,25 @@ It is possible somehow to tweak `s6` behaviour by providing an already predefine * `S6_KILL_GRACETIME` (default = 3000): How long (in milliseconds) `s6` should wait to reap zombies before sending a `KILL` signal. * `S6_LOGGING_SCRIPT` (default = "n20 s1000000 T"): This env decides what to log and how, by default every line will prepend with ISO8601, rotated when the current logging file reaches 1mb and archived, at most, with 20 files. +## Known issues and workarounds + +### `/bin` and `/sbin` are symlinks + +Some Linux distros (like CentOS 7) have started replacing `/bin` with a symlink +to `/usr/bin` (and the same for `/sbin -> /usr/sbin`). When you extract the +tarball, these symlinks are overwritten, so important programs like `/bin/sh` +disappear. + +The current workaround is to extract the tarball in two steps: + +``` +RUN tar xzf /tmp/s6-overlay-amd64.tar.gz -C / --exclude="./bin" --exclude="./sbin" && \ + tar xzf /tmp/s6-overlay-amd64.tar.gz -C /usr ./bin ./sbin +``` + +This will prevent tar from deleting those `/bin` and `/sbin` symlinks, and +everything will work as normal. + ## Performance And what about numbers? `s6-overlay` takes more or less **`904K`** compressed and **`3.4M`** uncompressed, that's very cheap! Although we already provide packaged base images, it is up to you which base image to use. And when it comes to how much time does it take to get supervision tree up and running, it's less than **`100ms`** #3!