summaryrefslogtreecommitdiffstats
path: root/recipes-containers
Commit message (Collapse)AuthorAgeFilesLines
* lxc: enable fix apparmor feature name. A typo called it "apparmour", back in ↵Gianfranco Costamagna2018-05-091-1/+1
| | | | | | | commit 7a62620ea09f01c1f2a730cbb1264202276f2b87 Changing the default to the right value Signed-off-by: Gianfranco Costamagna <gianfranco.costamagna@abinsula.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc-opencontainers: Drop obsolete patchPaul Barker2018-05-092-86/+0
| | | | | | | | The upstream Makefile now calls `$(GO)` instead of just `go` so this patch isn't needed anymore. Signed-off-by: Paul Barker <pbarker@toganlabs.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc/containerd: fix build with go 1.9.xBruce Ashfield2018-04-207-31/+37
| | | | | | | | | | | | | | | go 1.9.x was triggering linkage errors on some build hosts due to missing symbols. | tmp/work/core2-64-poky-linux/runc-docker/1.0.0-rc5+gitAUTOINC+4fc53a81fb-r0/recipe-sysroot/usr/lib/../lib/libc.a(dl-reloc-static-pie.o): In function `elf_mac: | /usr/src/debug/glibc/2.27-r0/git/sysdeps/x86_64/dl-machine.h:59: undefined reference to `_DYNAMIC' | tmp/work/core2-64-poky-linux/runc-docker/1.0.0-rc5+gitAUTOINC+4fc53a81fb-r0/recipe-sysroot/usr/lib/../lib/libc.a(dl-reloc-static-pie.o): In function `elf_get: | /usr/src/debug/glibc/2.27-r0/git/elf/get-dynamic-info.h:48: undefined reference to `_DYNAMIC' By ensuring that our sysroot provided go binary and build flags make it into the build enviroment we can build properly with 1.9 and 1.10 Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* criu: refresh patches to fix QA warningYi Zhao2018-04-135-26/+16
| | | | | | | Refresh patches with devtool command to fix do_patch warning. Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* criu: fix build failure with newer glibc and kernelYi Zhao2018-04-132-0/+48
| | | | | | | | | | | | | | | | | | | | | | | | | With newer glibc(>= 2.26) and kernel(>=4.14), criu would fail to build: In file included from /buildarea/build/tmp/work/core2-64-poky-linux/criu/3.4+gitAUTOINC+a31c1854e1-r0/recipe-sysroot/usr/include/linux/aio_abi.h:31:0, from criu/cr-check.c:24: /buildarea/build/tmp/work/core2-64-poky-linux/criu/3.4+gitAUTOINC+a31c1854e1-r0/recipe-sysroot/usr/include/sys/mount.h:35:3: error: expected identifier before numeric constant MS_RDONLY = 1, /* Mount read-only. */ ^ CC criu/parasite-syscall.o CC criu/pipes.o CC criu/pie-util.o CC criu/pie-util-vdso.o CC criu/plugin.o /buildarea/build/tmp/work/core2-64-poky-linux/criu/3.4+gitAUTOINC+a31c1854e1-r0/git/scripts/nmk/scripts/build.mk:110: recipe for target 'criu/cr-check.o' failed make[2]: *** [criu/cr-check.o] Error 1 Backport a patch to fix it. Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* docker: restructure to build docker-proxy using provided MakefileBruce Ashfield2018-04-092-9/+73
| | | | | | | | | | | Rather than invoking go directly to build docker-proxy, we can use the libnetwork Make infrastructure. This picks up our exported go enviroment variables, and other sysroot flags. We also apply one patch to ensure that the cross-go toolchain is used, and that the proper build flags are used. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc: ensure that ${GO} is exported build/makeBruce Ashfield2018-04-051-1/+5
| | | | | | | | | | | | | | The runc makefile now uses $(GO) universally, but sets the variable as GO := go by default. This means that the host go will be used instead of our recipe sysroot variant. A simple export of the variable is not enough in all cases (due to Make assignments), so both export it AND pass it directly to the oe_make call. This fixes docker-runc builds on ARM64. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* containerd: uprev to v1.0.2Bruce Ashfield2018-04-023-32/+68
| | | | | | | | | | | | | | Uprev containerd to v1.0.2 for compatibility with recent docker (18.04+) builds. With this uprev we also significantly restructure the build to use more of the latest oe-core go build infrastructure, but non-standard parts of the build remain. We also allow containerd to be build with CGO enabled to avoid linkage errors with the oe provided go build infrastructure. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* docker-ce: introduce reference recipe/buildBruce Ashfield2018-04-021-0/+172
| | | | | | | | | | | | | | | | | | | This commit introduces a docker-ce reference recipe that is nearly identical to the docker_git recipe. The main difference between these two recipes is that one builds from moby and this one from the docker-ce repository itself. The different repositories mean that a different selection of commits are used and that the build locations change slightly. Although both docker_git and this recipe share nearly all their code, they will vary more in the future, and prematurely factoring them into a .inc file is not practical (until this proves useful). Future work: remove the individual libnetwork and cli repository fetches and build the components directly from the docker-ce repo. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* docker: uprev to 18.03.0Bruce Ashfield2018-04-022-84/+17
| | | | | | | | | | | | | | | | | Uprev the docker daemon, proxy and cli to 18.03.0. The SRCREVs for these updates come from the versions logged in the docker-ce 18.03.0 release. The docker-ce recipe has a pure docker-ce single repository build, but here, we continue to assemble the individual parts for maximum flexibility. Along with the uprev, we add new dependencies required to build the new version; libtool and pkcconfig (although unused by the recipe itself). Finally we switch to a Makefile based build of the cli to allow the commit and docker version to be properly captured in the docker executable. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc: uprev to 1.0.0-rc5Bruce Ashfield2018-04-028-482/+30
| | | | | | | | | | | | | | | | | | Uprev both variants of runc to v1.0.0-rc5. We drop patches that have made it into the upstream runc, and we also refresh the context of of two others. The docker and opencontainers variants are virtually identical, but we keep the two variants for now to protect against any future forks in the support. The runc-docker SRCREV comes from the docker-ce 18.04 logged commit, while runc-opencontainers is updated to the tip of the master branch. Runtime tested with docker on x86-64. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* k8s: uprev to v1.10 releaseBruce Ashfield2018-03-261-2/+2
| | | | | | | We pickup the new release features .. plus the ability to actually build with go1.10 Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* docker: make aufs dependency depend on distro featurePascal Bach2018-03-221-2/+3
| | | | | | | | Only include aufs-utils if the corresponding distro feature is enabled. Without that the aufs kernel driver is not included too. Signed-off-by: Pascal Bach <pascal.bach@siemens.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python3-docker-compose: remove deprecated python3-enum from RDEPENDSRicardo Salveti2018-03-141-1/+0
| | | | | | | The python3-enum package was removed and it is now part of core. Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* lxc: set systemdsystemunitdir with systemdRicardo Salveti2018-02-051-0/+2
| | | | | | | | systemd unit dir can be customized by the distro (e.g. usrmerge), so make sure the correct unit dir path is set on configure. Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* add python3-terminal RDEPENDS to docker-compose recipeValerio De Benedetto2018-01-181-0/+1
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* kubernetes: package kube-proxy separatelyBruce Ashfield2018-01-161-0/+2
| | | | | | | kube-proxy is required on all kubernetes nodes. Rather than it being in the catch-all package, we put it in an explicit package. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* criu: set CLEANBROKEN to 1Chen Qi2017-12-281-0/+2
| | | | | | | | | | | | Rebuilding criu would cause the following error. | make: .gitid: Command not found | make: *** [Makefile:260: clean-top] Error 127 Fix this problem by setting CLEANBROKEN to "1". Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* lxc: add missing RDEPENDSMark Asselstine2017-12-281-0/+2
| | | | | | | | | | | | | | When attempting to create a container using lxc-create -t download -n test -- no-validate --dist ubuntu --release \ xenial --arch amd64 the container creation will fail due to missing 'xz' and in the case of 'tar' due to invalid options if the busybox version of 'tar' is used. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* dnsmasq: add dnsmasq.d entries for lxc and libvirtMark Asselstine2017-12-282-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A while ago changes were merged to meta-openembedded to make /etc/dnsmasq.d (and specifically the files it contains) referenced when the main instance of dnsmasq is run (see dnsmasq.service and commit ba665493a0dd [dnsmasq: allow for dnsmasq instances to reuse default dnsmasq.conf]). We, however, continued to modify the global configuration (/etc/dnsmasq.conf) to keep the main instance of dnsmasq from attaching to virbr0 and lxcbr0, by using 'bind-dynamic'. This approach is problematic, since it is common that other instances of dnsmasq will make use of the global configuration file and may have incompatible options. We see this for example when attempting to start lxc-net which will attempt to use 'bind-interface' which is incompatible with 'bind-dynamic' that we were adding to the global configuration. Here we remove our change to the global configuration (leaving it mostly empty as it should be) and instead have lxc and libvirt packages instruct the global instance not to bind to virbr0 and lxcbr0 by adding configuration files to /etc/dnsmasq.d (setting except-interface). The added benefit to this approach is that if lxc or libvirt are not part of an image the global configuration will not be modified in such a way as to expect that they are present. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc-docker: Allow "run start ..." to daemonize with $SIGUSR1_PARENT_PIDJason Wessel2017-12-112-0/+132
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The runc-docker has all the code in it to properly run a stop hook if you use it in the foreground. It doesn't work in the back ground because there is no way for a golang application to fork a child exit out of the parent process because all the golang threads stay with the parent. This patch has three parts that happen ONLY when $SIGUSR1_PARENT_PID is set. 1) At the point where runc start would normally exit, it closes stdin/stdout/stderr so it would be possible to daemonize "runc start ...". 2) The code to send a SIGUSR1 to the parent process was added. The idea being that a parent process would simply exit at that point because it was blocking until runc performed everything it was required to perform. 3) The code was copied which performs the normal the signal handling block which is used for the foreground operation of runc. -- More information -- When you use "runc run " it is running in the "foreground", in the sense it takes over your existing terminal. The runc-docker doesn't have a way to start it with "runc run&" where you can send it to the background and have everything work. With this commit, it does allow you to do that and have all the stop hooks fire at the time what ever runc started exits. Lets take a quick look at what "runc run" does today: * Starts a whole pile of threads * Sets up all name spaces * Starts child process for container and leaves it paused at image activation * runs start hooks * executes "continue" for container process * waits for container app to exit * executes stop hooks Now lets look at "runc create/start" does today: runc create * Starts a whole pile of threads * Sets up all name spaces * Starts child process for container and leaves it paused at image activation * exits -- [ NOTE: this is our problem! ] runc start * runs start hooks * executes "continue" for continue process At this point when the container app exits nothing is waiting for it to run any kind of hooks. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* lxc: add back the rdepends on glibc-utilsJackie Huang2017-12-011-0/+3
| | | | | | | | | | | | | | | | | The rdepends on glibc-utils was removed without reason in the following commit: """ e73608d56e498a7075e7a3e5550aafd76987d7aa lxc: 2.0.0 -> 2.0.8 """ And it causes failure: /usr/libexec/lxc/lxc-net: line 125: getent: command not found So add the dependency back. Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* kubernetes: add iproute2 tc to kubelet RDEPENDSBruce Ashfield2017-11-281-1/+1
| | | | | | | kubelet needs 'tc' at runtime, so we add iproute2-tc to the rdepends list. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* oci-image-tools: make Config.User mapping errors a warningBruce Ashfield2017-11-172-1/+32
| | | | | | | | | | | | | | | | | | Rather than throwing an error if we can't map a user to a uid, output a warning. We aren't actually running the code, but are just extracting it .. so the user not existing isn't an issue. With this, we avoid the not-so-useful traces like this: config.User: unsupported format github.com/opencontainers/image-tools/image.(*config).runtimeSpec oci-image-tools/0.2.0-dev+gitAUTOINC+4abe1a166f-r0/oci-image-tools-0.2.0-dev+gitAUTOINC+4abe1a16 6f/src/import/vendor/src/github.com/opencontainers/image-tools/image/config.go:109 <...> src/import/cmd/oci-image-tool/main.go:57 runtime.main /usr/lib64/go/src/runtime/proc.go:185 runtime.goexit /usr/lib64/go/src/runtime/asm_amd64.s:2337 Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* oci-systemd-hook: Always pass through all the cgroup mountsJason Wessel2017-11-142-0/+77
| | | | | | | | If the root name space has additional cgroup mounts, pass them to the container. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* kubernetes: correct install pathDariusz Pelowski2017-10-171-1/+1
| | | | | | | install needs to go to ${D}, not the host path, so we fix up the offending install lines. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc: use SRCPV not SRCREVBruce Ashfield2017-10-161-1/+1
| | | | | | | | | | | Ricardo Salveti <ricardo@opensourcefoundries.com> pointed out that runc-docker was not getting a proper PV due to the use of SRCREV in the variable. By switching to SRCPV, we get the right PV for both variants of runc. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc: Merge common metadata into inc filePaul Barker2017-10-163-8/+4
| | | | | Signed-off-by: Paul Barker <pbarker@toganlabs.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc: Drop inherit goarchPaul Barker2017-10-161-2/+0
| | | | | | | The go bbclass already inherits goarch. Signed-off-by: Paul Barker <pbarker@toganlabs.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc-docker: Drop unused EXTRA_FLAGSPaul Barker2017-10-161-2/+0
| | | | | | | This variable isn't picked up by the runc Makefile anyway as it isn't exported. Signed-off-by: Paul Barker <pbarker@toganlabs.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc-opencontainers: Drop unnecessary do_compile_prependPaul Barker2017-10-161-7/+0
| | | | | | | The "vendor/src" symlink is already created in do_compile in runc.inc. Signed-off-by: Paul Barker <pbarker@toganlabs.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc-docker: Disable building recvttyPaul Barker2017-10-122-0/+27
| | | | | | | | | The recvtty demo/reference application has cross compilation issues when targeting aarch64 platforms. As it is just a demo application and is not usually used, we can just patch the Makefile to disable building this application. Signed-off-by: Paul Barker <pbarker@toganlabs.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* docker/containerd: Export GOARCH to fix build in arm64Aníbal Limón2017-10-092-0/+2
| | | | | | | | | | | | | | | | | | If the GOARCH isn't set CGO took the ARCH from the host and tries to use -m64 flag that isn't available in aarch64 compiler. ... | # github.com/opencontainers/runc/libcontainer/system | aarch64-linaro-linux-gcc: error: unrecognized command line option '-m64' | # github.com/containerd/console | aarch64-linaro-linux-gcc: error: unrecognized command line option '-m64' | Makefile:60: recipe for target 'shim-static' failed ... Signed-off-by: Aníbal Limón <anibal.limon@linaro.org> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* containers: introduce kubernetes orchestrationBruce Ashfield2017-10-051-0/+98
| | | | | | | | | | | | | | Introducing the kubernets components for container orchestration. The packaging introduced here creates the framework for more advanced kubernetes configurations. By itself, it doesn't do much but it makes the components available to be configured and deployed as master/worker nodes. It integrates with the previously introduced cni and cri-o components available in meta-virt. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc: Don't override GOARCH or GOROOTPaul Barker2017-10-051-3/+0
| | | | | | | | | | These variables are now set correctly by go.bbclass in oe-core. Changing them to point at the native sysroot just leads to build errors in some cases, for example when the target and host have matching GOARCH but not matching c libraries. Signed-off-by: Paul Barker <pbarker@toganlabs.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc: Use correct go cross-compilerPaul Barker2017-10-054-1/+177
| | | | | | | | The makefiles for both providers of runc need to be patched in similar ways to ensure that we use the binaries from go-cross and not go-native. Signed-off-by: Paul Barker <pbarker@toganlabs.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc: Drop obsolete patchPaul Barker2017-10-051-48/+0
| | | | | | | This patch hasn't been used in a long time. Signed-off-by: Paul Barker <pbarker@toganlabs.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc-opencontainers: go.bbclass compile fixesPaul Barker2017-10-041-1/+3
| | | | | | | | These fixes are needed due to updates to go.bbclass in oe-core. See commit 01a8d4537012ad93dc8510e9b762acdc8c4536c7 for more information. Signed-off-by: Paul Barker <pbarker@toganlabs.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc-opencontainers: Update to v1.0.0-rc4Paul Barker2017-10-041-4/+3
| | | | | Signed-off-by: Paul Barker <pbarker@toganlabs.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* containers: cri-o: kubernetes runc backendBruce Ashfield2017-10-023-0/+303
| | | | | | | | | | | | | | | | To prepare for native kubernetes support without docker on a target, we integrate the cri-o incubator project. cri-o is meant to provide an integration path between OCI conformant runtimes and the kubelet. Specifically, it implements the Kubelet Container Runtime Interface (CRI) using OCI conformant runtimes. The scope of cri-o is tied to the scope of the CRI. This initial introduction is build + packaging only. It is expected that configuration and deployment tweaks are done at the distro level. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* oci-runtime-tools: fix multi hook specificationBruce Ashfield2017-09-202-1/+205
| | | | | | | | | | | | | | | | | | | | The following commit: commit df3a46feb971386f922c7c2c2822b88301f87cb0 Author: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com> Date: Tue Aug 1 17:39:39 2017 +0800 implement add/set function for hooks items Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com> Breaks the ability to specify multiple hooks with the same path (i.e. a shell script that does different things based on arguments). The author's intent with the change is unclear, so rather than fix it, we revert it for now. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* oci-runtime-tools: update to 0.1.0Bruce Ashfield2017-09-201-2/+7
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python3-docker-compose: add version 1.16.1 + dependenciesPascal Bach2017-09-152-0/+63
| | | | | | | | | This requires some packages as well as the pypi.bbclass from meta-python. It uses Python 3 as I don't think it makes sense to use Python 2 anymore. Signed-off-by: Pascal Bach <pascal.bach@siemens.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* oci-image-tools: fix LICENSE file locationBruce Ashfield2017-09-141-1/+1
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* docker-distribution: adjust to new go.bbclassBruce Ashfield2017-09-141-0/+4
| | | | | | | We want to build in ${S}, so we now require an explicit cd ${S} to avoid landing in the build directory. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* nets, docker, runc, oci-*tools: go.bbclass compile fixesJason Wessel2017-09-1413-76/+80
| | | | | | | | | | | | | | | | | | Recently in the oe-core the go.bbclass changed and requires the defition of the GO_IMPORT variable. This was intended to simplify how the compilation works with go packages and it is still a work in progress. This patch set makes the recipes compatible to generate the same end result as before using the new go.bbclass from oe-core. Any patches that were included in the recipes had to have the paths adjusted because the new go.bbclass manipulates the notion of S to be S + "src" + "$GO_IMPORT" internally for the purpose of unpack, patch and compile. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* oci-image-tools: uprev to 0.2.0-devBruce Ashfield2017-09-131-2/+2
| | | | | | | To work with OCI spec v1.0 images/containers we need to update our tools. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* criu: uprev to version 3.4Mark Asselstine2017-09-105-98/+52
| | | | | | | | | | | | | | | | | | | | Our current version of criu is about a year old and has some compilation issues with the latest gcc (currently it is unbuildable). Since the version of criu and the kernel version are fairly tightly coupled it wouldn't be surprising of this old criu would also be exhibiting some runtime issues with our fairly new kernel version. With the above in mind we uprev to criu v3.4 which was recently released. This requires several of the patches to be updated (mostly context). We are able to drop the selinux related change as RSS prevents the situation this was working around from happenning. This was validated using https://criu.org/Simple_loop (and a few variants). Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* Revert "criu: Correct the installation directory for python modules"Bruce Ashfield2017-09-102-31/+0
| | | | This reverts commit 90c1046b58c50f127ea711d83874a1dc4b68f7ed.
* singularity: Added dependency to e2fsprogs-mke2fsAlexandru Tiniuc2017-09-051-1/+1
| | | | | | | | | | While the recipe was functional under an image based on core-image- full-cmdline, when tested with core-image-minimal runtime issues appeared: Singularity was unable to create a filesystem within the container. This change fixes this issue. Signed-off-by: Alexandru Tiniuc <tiniuc.alexandru@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-16 03:17:05 +0000