Ran this transaction offline with no problems:
Upgrade gnome-calendar-3.30.1-1.fc29.x86_64 @updates
Upgrade osinfo-db-20181101-1.fc29.noarch @updates
Upgrade plymouth-0.9.4-1.fc29.x86_64 @updates
Upgrade plymouth-core-libs-0.9.4-1.fc29.x86_64 @updates
Upgrade plymouth-graphics-libs-0.9.4-1.fc29.x86_64 @updates
Upgrade plymouth-plugin-label-0.9.4-1.fc29.x86_64 @updates
Upgrade plymouth-plugin-two-step-0.9.4-1.fc29.x86_64 @updates
Upgrade plymouth-scripts-0.9.4-1.fc29.x86_64 @updates
Upgrade plymouth-system-theme-0.9.4-1.fc29.x86_64 @updates
Upgrade plymouth-theme-charge-0.9.4-1.fc29.x86_64 @updates
Upgrade texlive-base-7:20180414-25.fc29.x86_64 @updates
Upgrade texlive-lib-7:20180414-25.fc29.x86_64 @updates
Upgrade vim-common-2:8.1.511-1.fc29.x86_64 @updates
Upgrade vim-enhanced-2:8.1.511-1.fc29.x86_64 @updates
Upgrade vim-filesystem-2:8.1.511-1.fc29.noarch @updates
Upgrade vim-minimal-2:8.1.511-1.fc29.x86_64 @updates
Upgraded gnome-calendar-3.30.0-1.fc29.x86_64 @@System
Upgraded osinfo-db-20181011-1.fc29.noarch @@System
Upgraded plymouth-0.9.3-14.fc29.x86_64 @@System
Upgraded plymouth-core-libs-0.9.3-14.fc29.x86_64 @@System
Upgraded plymouth-graphics-libs-0.9.3-14.fc29.x86_64 @@System
Upgraded plymouth-plugin-label-0.9.3-14.fc29.x86_64 @@System
Upgraded plymouth-plugin-two-step-0.9.3-14.fc29.x86_64 @@System
Upgraded plymouth-scripts-0.9.3-14.fc29.x86_64 @@System
Upgraded plymouth-system-theme-0.9.3-14.fc29.x86_64 @@System
Upgraded plymouth-theme-charge-0.9.3-14.fc29.x86_64 @@System
Upgraded texlive-base-7:20180414-24.fc29.x86_64 @@System
Upgraded texlive-lib-7:20180414-24.fc29.x86_64 @@System
Upgraded vim-common-2:8.1.483-1.fc29.x86_64 @@System
Upgraded vim-enhanced-2:8.1.483-1.fc29.x86_64 @@System
Upgraded vim-filesystem-2:8.1.483-1.fc29.noarch @@System
Upgraded vim-minimal-2:8.1.483-1.fc29.x86_64 @@System
Problem: package strongswan-charon-nm-5.7.1-1.fc27.x86_64 conflicts with NetworkManager-strongswan < 1.4.2-1
Should be fixed by FEDORA-2018-aeb84f08f2
The oci-systemd-hook update makes it possible to run containers with systemd as PID 1. The problem in bug #1574316 only applies when using the --tty
option of docker run
, which is likely a different issue.
Walking back the previous feedback: docker is still flaky, see observations in https://bugzilla.redhat.com/show_bug.cgi?id=1574316
Able to run containers with /sbin/init as PID 1. There are problems with getting logs from the container, but this is not the subject of this bug.
The error message has not been displayed since applying this update.