On Tue, Jul 12, 2022 at 8:27 AM Vasileios Anagnostopoulos
<[email protected]> wrote:
>
> Skip the inclusion of the parent directory in the tar file.
> Most tools expect a tar file without it. An example of this
> use case is skopeo, where the skopeo copy oci-archive command
> will not work with the generate tar file.

The tar file was never actually intended to be used in that way, hence
why the directory is maintained.  It is just there for easier
transport of the oci image directory, and the existing workflow is
that multiple of these are copied and untar'd .. with this, they'll
clobber each other and break.

We could potentially create a new mode to support this .. I need to
think on it a bit more first.

Bruce

>
> Signed-off-by: Vasileios Anagnostopoulos 
> <[email protected]>
> ---
>  classes/image-oci-umoci.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/classes/image-oci-umoci.inc b/classes/image-oci-umoci.inc
> index f941795..771f288 100644
> --- a/classes/image-oci-umoci.inc
> +++ b/classes/image-oci-umoci.inc
> @@ -107,7 +107,7 @@ IMAGE_CMD:oci() {
>
>      # make a tar version of the image direcotry
>      if [ -n "${OCI_IMAGE_TAR_OUTPUT}" ]; then
> -       tar -cf "$image_name.tar" "$image_name"
> +       tar -cf "$image_name.tar" -C "$image_name" .
>      fi
>
>      # We could make this optional, since the bundle is directly runnable via 
> runc
> --
> 2.34.1
>
>
> 
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#7450): 
https://lists.yoctoproject.org/g/meta-virtualization/message/7450
Mute This Topic: https://lists.yoctoproject.org/mt/92331697/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to