public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 1/1] wic: disable generation of python bytecode cache
Date: Sun, 13 Jul 2025 18:59:00 +0200	[thread overview]
Message-ID: <aHPl1I4EJuBCfYRb@abai.de> (raw)
In-Reply-To: <20250605145837.1384007-1-felix.moessbauer@siemens.com>

On 2025-06-05 16:58, 'Felix Moessbauer' via isar-users wrote:
> Wic is executed as root, so the python bytecode cache is also
> created as root. This is problematic as the cache is created inside the
> source tree in a folder__pycache__ next to the python script itself. By
> that, we end up with files belonging to root inside the repo source
> tree, which makes it impossible to delete the source tree as a regular
> user.
> 
> This problem became visible with the kas purge plugin that removes the
> fetched layers as a regular user (these layers are fetched and managed
> by kas). Also the read-only mounting of repos in kas does not help here,
> as the fetched repos are not mounted ro for obvious reasons.
> 
> Anyways, we should not create files inside the source tree that do not
> belong to the calling user. To fix this, we just disable the python
> cache for the wic task. This is the only task that executes a python
> script from the source tree as root.

If there is consensus on this, I'd like to merge this in the next days because
it provides a specific improvement.

Any broader / more optimal changes can be merged on top.

With kind regards,
Baurzhan

-- 
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/aHPl1I4EJuBCfYRb%40abai.de.

  parent reply	other threads:[~2025-07-13 16:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05 14:58 'Felix Moessbauer' via isar-users
2025-06-06  6:19 ` 'Heinisch, Alexander' via isar-users
2025-06-06  6:21   ` 'Jan Kiszka' via isar-users
2025-06-06  7:18     ` 'MOESSBAUER, Felix' via isar-users
2025-06-06  7:38       ` 'Jan Kiszka' via isar-users
2025-06-06  7:42         ` 'Heinisch, Alexander' via isar-users
2025-06-06  7:54           ` 'MOESSBAUER, Felix' via isar-users
2025-06-06  8:02             ` 'Heinisch, Alexander' via isar-users
2025-07-13 16:59 ` Baurzhan Ismagulov [this message]
2025-07-17 10:36 ` 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=aHPl1I4EJuBCfYRb@abai.de \
    --to=ibr@radix50.net \
    --cc=isar-users@googlegroups.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