From 6e8773aaa33dd55b7b3fc231a22967d1e324b1c8 Mon Sep 17 00:00:00 2001 From: Jess Frazelle Date: Sat, 16 Apr 2016 16:06:20 -0700 Subject: [PATCH] fix Signed-off-by: Jess Frazelle --- README.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 1632494..33c1ad0 100644 --- a/README.md +++ b/README.md @@ -3,7 +3,8 @@ Create fully static, including rootfs embedded, binaries that pop you directly into a container. **Can be run by an unprivileged user.** -This is based off a crazy idea from [@crosbymichael](https://github.com/crosbymichael) who first embedded an image in a binary :D +This is based off a crazy idea from [@crosbymichael](https://github.com/crosbymichael) +who first embedded an image in a binary :D **NOTE** @@ -11,6 +12,12 @@ You may have noticed you can't file an issue. That's because this is using a cra person's (aka my) fork of libcontainer and until I get the patches into upstream there's no way in hell I'm fielding issues from whoever is crazy enough to try this. + +**Nginx running with my user "jessie".** + +![nginx.png](nginx.png) + + ### Building This uses the new Golang vendoring so you need go 1.6 or @@ -106,12 +113,6 @@ The binary spawned does NOT need to oversee the container process if you run in detached mode with a PID file. You can have it watched by the user mode systemd so that this binary is really just the launcher :) -## Example - -Nginx running with my user "jessie". - -![nginx.png](nginx.png) - ## Caveats **Caps the binary needs to unpack and set