NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
d83b5d628a
kumquat-buildroot/package/docker-engine/Config.in

58 lines
1.9 KiB
Plaintext
Raw Normal View History

docker-engine: new package Docker is a platform to build, ship, and run applications in portable containers. Signed-off-by: Christian Stewart <christian@paral.in> [Thomas: drop LIBRARY_PATH, as suggested by Christian.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-07-24 23:10:28 +02:00
config BR2_PACKAGE_DOCKER_ENGINE
bool "docker-engine"
package/go: rename BR2_PACKAGE_HOST_GO_{ARCH_SUPPORTS,CGO_LINKING_SUPPORTS} The hidden Config.in option BR2_PACKAGE_HOST_GO_ARCH_SUPPORTS name is not very clear as to whether it says whether Go is available for the target architecture or the host architecture. Until now, this was fine since there was support for host Go packages. But as we are about to introduce support for building host Go packages, we need to clarify the meaning of BR2_PACKAGE_HOST_GO_ARCH_SUPPORTS. Since it says whether the target architecture has support for Go or not, we rename it to BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS. And since BR2_PACKAGE_HOST_GO_CGO_LINKING_SUPPORTS is tightly related, we rename it to BR2_PACKAGE_HOST_GO_TARGET_CGO_LINKING_SUPPORTS. Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com> Tested-by: Adam Duskett <aduskett@gmail.com> [Thomas: entirely rewrite commit log] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-02-06 14:23:57 +01:00
depends on BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
depends on BR2_PACKAGE_HOST_GO_TARGET_CGO_LINKING_SUPPORTS
docker-engine: new package Docker is a platform to build, ship, and run applications in portable containers. Signed-off-by: Christian Stewart <christian@paral.in> [Thomas: drop LIBRARY_PATH, as suggested by Christian.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-07-24 23:10:28 +02:00
depends on BR2_TOOLCHAIN_HAS_THREADS
package/runc: add upstream security fix for CVE-2019-5736 The vulnerability allows a malicious container to (with minimal user interaction) overwrite the host runc binary and thus gain root-level code execution on the host. The level of user interaction is being able to run any command (it doesn't matter if the command is not attacker-controlled) as root within a container in either of these contexts: * Creating a new container using an attacker-controlled image. * Attaching (docker exec) into an existing container which the attacker had previous write access to. For more details, see the advisory: https://www.openwall.com/lists/oss-security/2019/02/11/2 The fix for this issue uses fexecve(3), which isn't available on uClibc, so add a dependency on !uclibc to runc and propagate to the reverse dependencies (containerd/docker-engine). Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-02-12 14:15:04 +01:00
depends on !BR2_TOOLCHAIN_USES_UCLIBC # docker-containerd -> runc
package/docker-engine: drop unused _DAEMON option Since commit de336584d2 (package/docker-engine: split docker-{cli, engine}, bump to v18.09.0), the docker-engine package only builds the daemon part, and the .mk file no longer use the _DAEMON option, so drop it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Tested-by: Christian Stewart <christian@paral.in> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-02-01 23:04:08 +01:00
depends on BR2_USE_MMU # docker-containerd
select BR2_PACKAGE_DOCKER_CONTAINERD # runtime dependency
select BR2_PACKAGE_DOCKER_PROXY # runtime dependency
select BR2_PACKAGE_IPTABLES # runtime dependency
select BR2_PACKAGE_SQLITE # runtime dependency
docker-engine: new package Docker is a platform to build, ship, and run applications in portable containers. Signed-off-by: Christian Stewart <christian@paral.in> [Thomas: drop LIBRARY_PATH, as suggested by Christian.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-07-24 23:10:28 +02:00
help
Docker is a platform to build, ship,
and run applications as lightweight containers.
https://github.com/docker/docker
if BR2_PACKAGE_DOCKER_ENGINE
config BR2_PACKAGE_DOCKER_ENGINE_EXPERIMENTAL
bool "build experimental features"
config BR2_PACKAGE_DOCKER_ENGINE_DRIVER_BTRFS
bool "btrfs filesystem driver"
depends on BR2_USE_MMU # btrfs-progs
depends on BR2_TOOLCHAIN_HAS_THREADS # btrfs-progs
select BR2_PACKAGE_BTRFS_PROGS
help
Build the btrfs filesystem driver for Docker.
config BR2_PACKAGE_DOCKER_ENGINE_DRIVER_DEVICEMAPPER
bool "devicemapper filesystem driver"
depends on BR2_TOOLCHAIN_HAS_THREADS # lvm2
depends on BR2_USE_MMU # lvm2
depends on !BR2_STATIC_LIBS # lvm2
package/lvm2: disable for musl toolchains lvm2 doesn't build with musl toolchains due to several assignment of read-only variable like stdin, stdout and stderr. Also, it use mallinfo function which is not available with musl. These issues has been reported upstream [2] but some of them remains even with the latest stable release 2.02.163. Fixes: http://autobuild.buildroot.net/results/3d4df873a3d4fa199e03d8aa8694eafeac474e5a [...] [1] http://lists.busybox.net/pipermail/buildroot/2016-August/170592.html [2] https://www.redhat.com/archives/linux-lvm/2016-February/msg00024.html Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-08-24 00:33:56 +02:00
depends on !BR2_TOOLCHAIN_USES_MUSL # lvm2
docker-engine: new package Docker is a platform to build, ship, and run applications in portable containers. Signed-off-by: Christian Stewart <christian@paral.in> [Thomas: drop LIBRARY_PATH, as suggested by Christian.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-07-24 23:10:28 +02:00
select BR2_PACKAGE_LVM2
select BR2_PACKAGE_LVM2_APP_LIBRARY
help
Build the devicemapper filesystem driver for Docker.
config BR2_PACKAGE_DOCKER_ENGINE_DRIVER_VFS
bool "vfs filesystem driver"
depends on BR2_USE_WCHAR # gvfs
depends on BR2_USE_MMU # gvfs
depends on BR2_TOOLCHAIN_HAS_THREADS # gvfs
select BR2_PACKAGE_GVFS
help
Build the vfs filesystem driver for Docker.
endif
Revert "runc: depend on linux headers >= 3.11 for O_TMPFILE" This reverts commit 905e976a6af224b3ed015c46fcea2d717c155f55. With the bump to 1.0.0-rc7, runc no longer needs O_TMPFILE. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-04-01 20:23:47 +02:00
comment "docker-engine needs a glibc or musl toolchain w/ threads"
package/go: rename BR2_PACKAGE_HOST_GO_{ARCH_SUPPORTS,CGO_LINKING_SUPPORTS} The hidden Config.in option BR2_PACKAGE_HOST_GO_ARCH_SUPPORTS name is not very clear as to whether it says whether Go is available for the target architecture or the host architecture. Until now, this was fine since there was support for host Go packages. But as we are about to introduce support for building host Go packages, we need to clarify the meaning of BR2_PACKAGE_HOST_GO_ARCH_SUPPORTS. Since it says whether the target architecture has support for Go or not, we rename it to BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS. And since BR2_PACKAGE_HOST_GO_CGO_LINKING_SUPPORTS is tightly related, we rename it to BR2_PACKAGE_HOST_GO_TARGET_CGO_LINKING_SUPPORTS. Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com> Tested-by: Adam Duskett <aduskett@gmail.com> [Thomas: entirely rewrite commit log] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-02-06 14:23:57 +01:00
depends on BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
depends on BR2_PACKAGE_HOST_GO_TARGET_CGO_LINKING_SUPPORTS
Revert "runc: depend on linux headers >= 3.11 for O_TMPFILE" This reverts commit 905e976a6af224b3ed015c46fcea2d717c155f55. With the bump to 1.0.0-rc7, runc no longer needs O_TMPFILE. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-04-01 20:23:47 +02:00
depends on !BR2_TOOLCHAIN_HAS_THREADS || BR2_TOOLCHAIN_USES_UCLIBC
package/docker-engine: drop unused _DAEMON option Since commit de336584d2 (package/docker-engine: split docker-{cli, engine}, bump to v18.09.0), the docker-engine package only builds the daemon part, and the .mk file no longer use the _DAEMON option, so drop it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Tested-by: Christian Stewart <christian@paral.in> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-02-01 23:04:08 +01:00
depends on BR2_USE_MMU
Reference in New Issue Copy Permalink