public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: martin.banov.dev@gmail.com
Cc: isar-users@googlegroups.com, mabo <mabo@universal-robots.com>,
	Daniel Machon <dama@universal-robots.com>
Subject: Re: [RFC PATCH v1] image-container-extension: exclude proc sys dev
Date: Mon, 4 Apr 2022 15:41:04 +0200	[thread overview]
Message-ID: <20220404154104.3773d35a@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20220404115420.31933-1-martin.banov.dev@gmail.com>

Am Mon,  4 Apr 2022 13:54:20 +0200
schrieb martin.banov.dev@gmail.com:

> From: mabo <mabo@universal-robots.com>
> 
> The patch prevents 'cp' from copying the kernel filesystems
> into the docker container.
> We had CI issues with 'cp' trying to copy /proc/<pid>/pagemap.

I would expect that to only run once that thing is ready to be
"shipped", so all those filesystems should not be mounted any longer.
But the whole mounting logic has been reworked and some of the
umounting might remain lazy ... So we can probably not rule out that
they might for whatever reason be mounted.
And it seems pretty clear that we only want "--one-file-system".

> Signed-off-by: mabo <mabo@universal-robots.com>
> Signed-off-by: Daniel Machon <dama@universal-robots.com>
> ---
>  meta/classes/image-container-extension.bbclass | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/meta/classes/image-container-extension.bbclass
> b/meta/classes/image-container-extension.bbclass index
> cdec463..f4e8d41 100644 ---
> a/meta/classes/image-container-extension.bbclass +++
> b/meta/classes/image-container-extension.bbclass @@ -29,9 +29,8 @@
> containerize_rootfs() { "${oci_img_dir}_unpacked"
>  
>      # add root filesystem as the flesh of the skeleton
> -    sudo cp -a "${rootfs}"/* "${oci_img_dir}_unpacked/rootfs/"
> -    # clean-up temporary files
> -    sudo find "${oci_img_dir}_unpacked/rootfs/tmp" -mindepth 1
> -delete
> +    sudo cp -axT "${rootfs}" "${oci_img_dir}_unpacked/rootfs/"
> +    

LGTM.

Henning

>      # pack container image
>      bbdebug 1 "pack container image"


  reply	other threads:[~2022-04-04 13:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 11:54 martin.banov.dev
2022-04-04 13:41 ` Henning Schild [this message]
2022-04-04 15:29 ` Henning Schild
2022-04-04 15:41   ` Baurzhan Ismagulov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220404154104.3773d35a@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=dama@universal-robots.com \
    --cc=isar-users@googlegroups.com \
    --cc=mabo@universal-robots.com \
    --cc=martin.banov.dev@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox