Skip to content

rpm installing bareos-filedaemon fails on silverblue #2465

@Kn0lc

Description

@Kn0lc

Bareos component version

  1. fresh install on fedora 43 silverblue
  2. Repo file:
    [bareos]
    name=Backup Archiving Recovery Open Sourced (Fedora_43)
    baseurl=https://download.bareos.org/next/Fedora_43
    username=
    password=
    gpgcheck=1
    repo_gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-bareos-experimental
    enabled=1

Steps to reproduce

  1. sudo rpm-ostree install bareos-filedaemon

Expected results

sucessfull install

Actual results

Resolving dependencies... done
Checking out packages... done
Running systemd-sysusers... done
Running pre scripts... done
error: Running %prein for bareos-filedaemon: bwrap(/bin/sh): Der Kindprozess wurde mit Status 1 beendet; run journalctl -t 'rpm-ostree(bareos-filedaemon.prein)' for more information

journalctl -t 'rpm-ostree(bareos-filedaemon.prein)':
rpm-ostree(bareos-filedaemon.prein)[2074468]: /proc/self/fd/5: Zeile 9: /var/log/bareos/bareos-filedaemon-install.log: Datei oder Verzeichnis nicht gefunden
rpm-ostree(bareos-filedaemon.prein)[2079700]: mkdir: Verzeichnis »»/var/log«« konnte nicht angelegt werden: Das Dateisystem ist nur lesbar

Environment

- OS: `fedora 43 silverblue`

Relevant log output

Relevant traces output

Anything else?

silverblue uses osstree to generate immutable filesystem of the OS level file tree. for example /usr.
But /var/log isn't and if created manually /var/log/bareos/bareos-filedaemon-install.log and tested various rights. (including disabling selinux).
the new installed Programms using rpm-ostree install are available after a reboot by design. I think the filesystem looks different to the preinstall script that fails.
The rpm package for fedora 41 worked with Silverblue.

Metadata

Metadata

Assignees

Labels

bugThis addresses a bug

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions