Hello Bruce, unfortunately, there is not a single warning or error message whatsoever thrown. The first occasion, some error message is thrown, occurs during do_rootfs where it complains about the missing package "docker" - which is obviously missing as it has not been build.
As I mentioned in my original post, the docker package is being built when using the rpm backend though. Mark -----Ursprüngliche Nachricht----- Von: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] Im Auftrag von Bruce Ashfield Gesendet: Montag, 9. April 2018 16:30 An: Mark Junghanns; email@example.com Betreff: Re: [yocto] meta-virtualization -> docker not packaged when using PACKAGE_CLASSES ?= "package_deb" On 04/06/2018 09:13 AM, Mark Junghanns wrote: > Hello, > I encountered a funny behavior the other day. While trying to integrate > Docker into my image using the openembedded meta-virtualization layer, I > happened to not being able to get my image finalized. > > Usually I build with > PACKAGE_CLASSES ?= "package_deb". > > I also added > DISTRO_FEATURES_append = " virtualization" > > The build process aborts at some point within do_rootfs, stating something > like that the package 'docker' could not be found. I tracked down the problem > to docker's build/tmp/work/<something>/docker/<version>/deploy-debs/ > directory. I found the following packages: > > docker-contrib_17.06.0+gite639a70fbe999d96354a5bcf560231b7b8aa935c-r0_ > amd64.deb docker-distribution-dev_v2.6.2-r0_amd64.deb > docker-registry_v2.6.2-r0_amd64.deb > docker-dbg_17.06.0+gite639a70fbe999d96354a5bcf560231b7b8aa935c-r0_amd6 > 4.deb docker-distribution-ptest_v2.6.2-r0_amd64.deb > docker-distribution-dbg_v2.6.2-r0_amd64.deb > docker-ptest_17.06.0+gite639a70fbe999d96354a5bcf560231b7b8aa935c-r0_am > d64.deb > > > The package that is actually missing, is the docker package itself. I suppose > it would be named > docker_17.06.0+gite639a70fbe999d96354a5bcf560231b7b8aa935c-r0_amd64.deb. > > There is not any single warning or error thrown whatsoever during the build > of docker, it seems to just silently refusing to build the package. > > Yet, when change PACKAGE_CLASSES ?= "package_deb" to PACKAGE_CLASSES ?= > "package_rpm" it would build all required docker RPM-Packages just fine. At > the end of the day I way able to get a complete image with Docker integrated, > which is fine for the moment. Unfortunately I need to stick with the DEB > format for update reasons, so eventually I need to deal with this issue again. > > Has anyone seen this happening as well? Any idea, where and how to fix this? I've never seen this, but then again, I've also never used the .deb package backend. When you were building with .debs, and your image had "docker' in the image install .. was there any errors thrown due to the package not being created ? Bruce > > Thanks in advance for your help! > > Mark > -- _______________________________________________ yocto mailing list firstname.lastname@example.org https://lists.yoctoproject.org/listinfo/yocto -- _______________________________________________ yocto mailing list email@example.com https://lists.yoctoproject.org/listinfo/yocto