Zypper reports changed files in distrobox

English Virtualization
1

Hi,

When doing a distrobox upgrade and subsequent enter I find files changed by doing zypper ps -s. When doing a distrobox stop and distrobox enter the changed files stay. Is this expected behaviour or am I doing things backwards. How can I tell distrobox or the podman container to use the new version of the files?

Example zypper ps -s output:
image

Thanks in advance and kind regards,

Natasha

1 Like
2

Are these rootful podman containers?

Can’t think of how else the container could clobber up the host’s zypper files.

3

Yes, this container is rootful. The output is from within the container. In case of host updates, as per Micro-OS defaults the system is restarted. But still these files persist on being changed. I would expect them to adapt the change at some point so zypper ps -s would be empty.

4

Can’t be sure there isn’t some container ↔ host clobbering going on with a rootful container.

Just to understand your issue better, could you confirm whether:

  1. zypper ps on host is empty
  2. zypper ps on distrobox stop and distrobox enter remains non-empty.
5

(this is my work account)
Number 1 is correct… since transactional-update runs at regular intervals and reboots.
Number 2 is correct… this is exactly the problem I’m running into.

6

Ah okay. I’m assuming you’re using distrobox v1.6.1 and by the zypper ps output an init container?
If so, Luca and I had pushed quite a few changes/fixes to systemd/init distroboxes in the last few months, especially changing the way you enter init distroboxes (using su and a corresponding pam config for real login creating a proper systemd session as opposed to bash -l faux login).

Please check if the issue persists with the latest dev branch of distrobox. You should be able to install it in /usr/local/bin on MicroOS.

2 Likes
7

Experienced users should NEVER promote the use of plain su
ALWAYS use su -

This are basics…
https://wiki.mageia.org/en/Never_use_just_su

1 Like
8

Init distroboxes with the dev version (or next release) uses su <user> to login, it’s not possible to use the -l flag to clear environment variables as it would break the close integration to the host provided by distrobox.

In any case, no one is logging in as root using su, so it’s safe :slightly_smiling_face:

2 Likes
9

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.