search

projectatomic / atomic

Atomic Run Tool for installing/running/managing container images.
Other
524 stars 139 forks source link

System package installation failed due to read-only /usr #1220

Open kladiv opened 6 years ago

kladiv commented 6 years ago

Hi, i tried to install libffi-devel but got following issue:

# rpm-ostree install openssl-devel libffi-devel
Checking out tree 14d55f3... done
Enabled rpm-md repositories: epel base updates extras
rpm-md repo 'epel' (cached); generated: 2018-04-05 17:58:18

rpm-md repo 'base' (cached); generated: 2017-09-05 21:51:13

rpm-md repo 'updates' (cached); generated: 2018-04-04 18:30:34

rpm-md repo 'extras' (cached); generated: 2018-04-03 10:24:10

Importing metadata [===============================================================================================================] 100%
Resolving dependencies... done
Will download: 11 packages (2.9 MB)

  Downloading from base: [=======================================================================================================  ]  99%

Importing: [=======================================================================================================================] 100%
Applying 67 overlays... done
Running pre scripts... 0 done
Running post scripts... error: Running %post for libffi-devel: Executing bwrap(/bin/sh): Child process killed by signal 1; run `journalctl -t 'rpm-ostree(libffi-devel.post)'` for more information
# journalctl -t 'rpm-ostree(libffi-devel.post)'
-- Logs begin at Fri 2018-01-19 22:49:54 CET, end at Fri 2018-04-06 17:27:58 CEST. --
Apr 06 17:27:27 satellite2 rpm-ostree(libffi-devel.post)[22801]: /usr/share/info/dir: Read-only file system

Regards, Claudio

peterbaouoft commented 6 years ago

Hi, Thanks for the report! ~Atomic Host has a read-only /usr directory (except for /usr/local), and I believe~ ~your error was because the package tried to install files into /usr.~

In addition, for more help, I think it will be better to report this to rpm-ostree. This(atomic) repo is mainly for command atomic :-).

Thanks, Peter

EDIT: Sorry, I think I was wrong before for my reasoning. After more thinking, it seems like your error was happening during package installation, which could likely be another problem. Please take your time to report the this to rpm-ostree, thanks :-)