Re: error when try to use sudo command in recipe


Adrian Freihofer
 

Hi Simon

I guess in the deploy folder (build/tmp/deploy/...) you will find a tar
archive which can be used with e.g. docker import.

If you need to upload the OCI image to a container registry skopeo
might be used somehow like that:

bitbake "skopeo-native:do_addto_recipe_sysroot"
OCI_DIR="build/tmp/deploy/images/${MACHINE}/${TARGET_IMAGE}-
${MACHINE}.rootfs-oci"
oe-run-native skopeo-native skopeo login -u "${CI_REGISTRY_USER}" -p
"${CI_REGISTRY_PASSWORD}" "${CI_REGISTRY}" --authfile
${HOME}/.registry-auth.json
oe-run-native skopeo-native skopeo copy oci:${OCI_DIR}
docker://${CI_REGISTRY_IMAGE}:${CI_COMMIT_REF_SLUG}-${OCI_ARCH} --
authfile ${HOME}/.registry-auth.json

If you need to provide the container for different architectures
manifest-tool can do that. After uploading images to a registry the
manifest tool can convert all the per ARCH images into a multi arch
container image.

Regards,
Adrian

On Thu, 2023-02-09 at 10:45 -0800, SIMON BABY wrote:
Hello,
 
I was testing the meta-virtualization/recipes-demo/images/ app-
container. I was able to build the container. But I am not sure where
is the image created  and how do we run the image using docker
commands. I also see the .yaml files. 
On the target I can see /usr/bin/flask-app. Below is the folder
contents after bitbake.
 
bitbake app-container
 
build/tmp/work/armv8a-poky-linux/helloworld-flask$ ls
0.1-r0
/build/tmp/work/armv8a-poky-linux/helloworld-flask$ cd 0.1-r0/
build/tmp/work/armv8a-poky-linux/helloworld-flask/0.1-r0$ ls -ll
total 84
-rw-r--r--  1 tdydev tdydev    65 Feb  7 11:58 configure.sstate
drwxr-xr-x  3 tdydev tdydev  4096 Feb  7 12:10 deploy-debs
drwxr-xr-x  2 tdydev tdydev  4096 Feb  7 11:38 deploy-source-date-
epoch
-rwxrwxr-x  1 tdydev tdydev   518 Feb  2 14:24 flask-app
-rw-r--r--  1 tdydev tdydev   511 Feb  7 11:58 flask-app-service.yaml
-rw-r--r--  1 tdydev tdydev   178 Feb  7 11:58 flask-app.yaml
drwxr-xr-x  2 tdydev tdydev  4096 Feb  7 11:35 helloworld-flask-0.1
drwxr-xr-x  4 tdydev tdydev  4096 Feb  7 11:58 image
drwxr-xr-x  3 tdydev tdydev  4096 Feb  7 11:38 license-destdir
drwxr-xr-x  4 tdydev tdydev  4096 Apr  5  2011 package
drwxr-xr-x 10 tdydev tdydev  4096 Feb  7 12:10 packages-split
drwxr-xr-x  7 tdydev tdydev  4096 Apr  5  2011 pkgdata
drwxr-xr-x  7 tdydev tdydev  4096 Feb  7 11:58 pkgdata-pdata-input
drwxr-xr-x  7 tdydev tdydev  4096 Feb  7 11:58 pkgdata-sysroot
drwxrwxr-x  2 tdydev tdydev  4096 Feb  7 12:10 pseudo
drwxr-xr-x  5 tdydev tdydev  4096 Feb  7 12:10 recipe-sysroot
drwxr-xr-x  8 tdydev tdydev  4096 Feb  7 12:10 recipe-sysroot-native
drwxr-xr-x  2 tdydev tdydev  4096 Feb  7 11:35 source-date-epoch
drwxr-xr-x  2 tdydev tdydev 12288 





Regards
Simon


On Sun, Feb 5, 2023 at 4:00 PM SIMON BABY via lists.yoctoproject.org
<simonkbaby=gmail.com@...> wrote:
Hi Richard,

I added extra code in the recipe to print the sudo permissions to
compare with actual permissions.

Regards
Simon



Join yocto@lists.yoctoproject.org to automatically receive all group messages.