Files
docker-cli/components/engine/pkg
Akihiro Suda e8ed8e5184 gcplogs: forcibly set HOME on static UNIX binary
Fix #29344

If HOME is not set, the gcplogs logging driver will call os/user.Current() via oauth2/google.
However, in static binary, os/user.Current() leads to segfault due to a glibc issue that won't be fixed
in a short term. (golang/go#13470, https://sourceware.org/bugzilla/show_bug.cgi?id=19341)
So we forcibly set HOME so as to avoid call to os/user/Current().

Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp>
Upstream-commit: b86e3bee5aea8e72b7f08e104ebb5d6cb18f8890
Component: engine
2016-12-29 03:17:26 +00:00
..
2016-11-18 15:51:36 +08:00
2016-12-02 03:58:54 -08:00
2016-12-01 09:38:08 -08:00
2016-11-17 21:05:09 +00:00
2016-12-28 09:43:27 +08:00
2016-06-11 13:16:55 -07:00
2016-12-21 20:16:19 +08:00
2015-12-13 18:04:12 +02:00
2016-04-09 21:18:15 +08:00
2016-11-16 12:55:18 -05:00
2016-11-30 10:11:42 -08:00
2016-11-13 20:08:51 -08:00
2016-12-12 09:34:03 +01:00
2016-04-28 11:04:50 +08:00

pkg/ is a collection of utility packages used by the Docker project without being specific to its internals.

Utility packages are kept separate from the docker core codebase to keep it as small and concise as possible. If some utilities grow larger and their APIs stabilize, they may be moved to their own repository under the Docker organization, to facilitate re-use by other projects. However that is not the priority.

The directory pkg is named after the same directory in the camlistore project. Since Brad is a core Go maintainer, we thought it made sense to copy his methods for organizing Go code :) Thanks Brad!

Because utility packages are small and neatly separated from the rest of the codebase, they are a good place to start for aspiring maintainers and contributors. Get in touch if you want to help maintain them!