When the go-lang container recipes were first created there were issues
with strip and the resulting binaries. As such, strip was inhibited for
the various packages.
This variable is now set in the default classes, and tests show that
strip works on the binaries (saving up to 2M on disk for some binaries)
with no runtime issues found.
So we drop our explicit set of the inhibit and let the build proceed
by the defaults.
If issues are found, we can re-enable the setting or bbappends can
turn it back on for builds showing issues.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
If docker run --init is used docker expects docker-init to be
present, if not Docker fails to start the container with the
following error:
docker: Error response from daemon: exec: "docker-init": executable file not found in $PATH.
However, docker-init does not get deployed by default since commit
d19fda3743 ("docker: consolidate common depends/options"). Readd
docker-init through a PACKAGECONFIG RDEPENDS to make sure it gets
deployed by default again.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
The split between docker-ce and docker (moby) was initially
quite different, and docker-ce was more of a reference versus
a supported / working package.
Upstream has evolved such that both are valid options, and
may be chosen due to different requirements.
Rather than duplicating all the settings, we can move the
dependencies, init, rdepends, users, etc, into a .inc file and
share them.
For now, we keep the build separate, since depending on the
uprev status, they still can require different build options
and packaging.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
