On Wed, 01.07.15 13:50, Johannes Ernst (johannes.er...@gmail.com) wrote: > Hey Martin, > > thanks, but: > > >> My container is degraded because systemd-tmpfiles-setup.service > >> failed. My understanding is that it should not run in the container > >> anyway. (Right?) > > > > It should run in a container; its purpose is both necessary, and I > > don't see why a container would have any difficulty with it. It runs > > just fine in both system and even unprivileged user containers here. > > Here is what fails: > > # /usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev > Failed to create file /sys/devices/system/cpu/microcode/reload: Read-only > file system
We should probably handle this case in a nicer way, and downgrade EROFS error for cases like this. Can you let me know which tmpfiles snippet actually adds this line, and what precisely it contains? i.e. look in /usr/lib/tmpfiles.d/ for the file that mentions "/sys/devices/system/cpu/microcode/reload", and figure out the package name it is shipped with, and paste the contents of the file here. Thanks, Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
