All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenther Meyer <g.meyer@signum-media.de>
To: "meta-virtualization@lists.yoctoproject.org"
	<meta-virtualization@lists.yoctoproject.org>
Subject: Problems building an OCI container image
Date: Tue, 08 Nov 2022 16:44:56 +0100	[thread overview]
Message-ID: <2422477.irdbgypaU6@serenity> (raw)

[-- Attachment #1: Type: text/plain, Size: 1978 bytes --]

Hi,

I am trying to build some OCI-containers, but there are some things that are 
not really clear to me:

Issue one: When I build my container image, these are the resulting files:

example-container-qemux86-64.testdata.json -> example-container-
qemux86-64-20221108152401.testdata.json
example-container-qemux86-64-20221108152401.testdata.json
example-container-qemux86-64.manifest -> example-container-
qemux86-64-20221108152401.rootfs.manifest
example-container-qemux86-64-20221108152401.rootfs.manifest
example-container-qemux86-64.qemuboot.conf -> example-container-
qemux86-64-20221108152401.qemuboot.conf
example-container-qemux86-64-20221108152401.qemuboot.conf
example-container-qemux86-64-20221108152401.rootfs.tar.bz2
example-container-qemux86-64.tar.bz2 -> example-container-
qemux86-64-20221108152401.rootfs.tar.bz2
example-container-qemux86-64-20221108152401.rootfs-oci
example-container-qemux86-64-20221108152401.rootfs-oci.tar

So the question is, why are there only stable symlinks for some of the files 
and not for the rootfs-oci files? How can this be changed?


The second issue is the resulting tar-file. I thought, I could directly load it 
as an image, but that results in an error.
Investigating the content of the archive, I found, that the necessary content 
like index.json, oci-layout ad blob/* is not on the root level but inside a 
subfolder "example-container-qemux86-64-20221108152401.rootfs-oci/".

Is that intentional, if yes, why?
Because when I create an archive with the same files on the root level, it can 
directly be used with podman or other tools.


Issue number three:
Maybe this is not directly related, but I'm fairly new into this container 
stuff, so forgive me, if I'm wrong:
If I want to use a predeployed image with k3s, what is the name of the image 
that I have to use in the deployment yaml? Is it just the filename or is it 
something else? If the latter, how do I set the image name during the build?

Cheers,
Guenther

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2022-11-08 15:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 15:44 Guenther Meyer [this message]
2022-11-08 16:37 ` [meta-virtualization] Problems building an OCI container image Bruce Ashfield
2022-11-09 11:05   ` Guenther Meyer

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=2422477.irdbgypaU6@serenity \
    --to=g.meyer@signum-media.de \
    --cc=meta-virtualization@lists.yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.