From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Antoine Petty <antoine.petty@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: SDK Container for app development is missing some applications
Date: Tue, 18 Mar 2025 22:47:28 +0100 [thread overview]
Message-ID: <75fe7029-caa3-4ec8-9b3a-4bfef778ba42@siemens.com> (raw)
In-Reply-To: <3daa7f3f-1a95-4fed-bcdc-5251908c776fn@googlegroups.com>
On 18.03.25 12:27, 'Antoine Petty' via isar-users wrote:
> For ISAR, it looks like I'm using a patched version of this 2022 commit
> at the moment https://github.com/ilbers/isar/
> commit/20af1e2798353b118fc3538da0d4cdd8866101d5 but due to upgrade to
> something more recent.
Could you please clarify the exact version in use in the end? kas is
reporting that revision while starting up (I strongly suspect you are
using kas).
>
> The `log.do_populate_sdk` file for this image recipe contains:
> ```
> DEBUG: Executing shell function do_populate_sdk
> umount: /workspace/project/build/tmp/deploy/sdkchroot/debian-bullseye-
> armhf/dev: not mounted
> umount: /workspace/project/build/tmp/deploy/sdkchroot/debian-bullseye-
> armhf/proc: not mounted.
> umount: /workspace/project/build/tmp/deploy/sdkchroot/debian-bullseye-
> armhf/sys: not mounted
> find: '/workspace/project/build/tmp/deploy/sdkchroot/debian-bullseye-
> armhf/root': Permission denied
> find: '/workspace/project/build/tmp/deploy/sdkchroot/debian-bullseye-
> armhf/etc/ssl/private': Permission denied
> find: '/workspace/project/build/tmp/deploy/sdkchroot/debian-bullseye-
> armhf/var/cache/ldconfig': Permission denied
> find: '/workspace/project/build/tmp/deploy/sdkchroot/debian-bullseye-
> armhf/var/cache/apt/archives/partial': Permission denied
> NOTE: Generating SDK container in docker-archive format
> DEBUG: prepare OCI container image skeleton
> DEBUG: pack container image
> DEBUG: Creating container image type: docker-archive
> DEBUG: Converting OCI image to docker-archive
> Getting image source signatures
> Copying blob sha256:[hash]
> Copying config sha256:[hash]
> Writing manifest to image destination
> Storing signatures
> DEBUG: Compressing image
> DEBUG: Shell function do_populate_sdk finished
> ```
> so it's interesting that there are so many errors here when it's looks
> happy during the build!
Yeah, but those are misleading.
I also asked for the wrong log files. We need to look at the recipe
<image-name>-sdk, task do_rootfs_install.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/75fe7029-caa3-4ec8-9b3a-4bfef778ba42%40siemens.com.
prev parent reply other threads:[~2025-03-18 21:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 16:49 'Antoine Petty' via isar-users
2025-03-14 17:49 ` 'Jan Kiszka' via isar-users
2025-03-17 10:33 ` 'Antoine Petty' via isar-users
2025-03-17 10:38 ` 'Antoine Petty' via isar-users
2025-03-17 15:38 ` 'Jan Kiszka' via isar-users
2025-03-18 11:27 ` 'Antoine Petty' via isar-users
2025-03-18 21:47 ` 'Jan Kiszka' via isar-users [this message]
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=75fe7029-caa3-4ec8-9b3a-4bfef778ba42@siemens.com \
--to=isar-users@googlegroups.com \
--cc=antoine.petty@siemens.com \
--cc=jan.kiszka@siemens.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