This was pilot error in our test infrastructure. Argh, how do I unpush this? :-(
Installs fine now, many thanks!
Weird.. This was submitted two days ago, and is still not "visible" by dnf updates
. Apparently the upload → testing propagation already took 1½ days. I'll test this ASAP.
Thanks for your fast fix, @limb!
Awesome, this is the first-ever toolbox version that Just Works™ for me for both Fedora and Debian containers. I dropped all my hacks. Well done!
Works well and unbreaks cockpit-podman.
TestServices.testBasic
gets fixed by https://github.com/cockpit-project/cockpit/pull/14338I'm still investigating why the libvirt default network disappears. This happens upstream as well in rare occasions, but is some race condition.
Oops, this looks like a regression in sssd:
+ busctl call org.freedesktop.sssd.infopipe /org/freedesktop/sssd/infopipe/Users org.freedesktop.sssd.infopipe.Users FindByCertificate s -- "$(cat /var/lib/cockpittest/alice.pem)" | sed 's/^o "//; s/"$//'
?[0;1;31mCall failed: The name is not activatable?[0m
I tested downloading and unpacking the previous podman-1.9.3 and running it with toolbox-0.0.18-3.fc32.noarch and conmon-2.0.18-1.fc32.x86_64 , but that does not work either. I rebuilt my OSTree entirely without updates-testing, now with podman-1.9.3-1.fc32.x86_64, toolbox-0.0.18-2.fc32.noarch, and conmon-2.0.17-1.fc32.x86_64 and things work again.
This completely breaks toolbox --verbose enter
:
toolbox: /home is a symbolic link to /var/home
toolbox: calling org.freedesktop.Flatpak.SessionHelper.RequestSession
toolbox: creating container fedora-toolbox-32
Error: invalid config provided: Groups and privileged are mutually exclusive options
toolbox: failed to create container fedora-toolbox-32
This is happens on a system with rm -rf ~/.local/share/containers ~/.config/containers
. On my previously existing config and fedora toolboxes, toolbox enter
fails with
toolbox: invalid entry point PID of container sid
and I get all sorts of "permission denied" errors, like
+ echo toolbox: binding /etc/machine-id to /run/host/etc/machine-id
toolbox: binding /etc/machine-id to /run/host/etc/machine-id
+ [ ro = ]
+ mount_o=-o ro
+ mount --rbind -o ro /run/host/etc/machine-id /etc/machine-id
mount: drop permissions failed.
+ echo toolbox: failed to bind /etc/machine-id to /run/host/etc/machine-id
toolbox: failed to bind /etc/machine-id to /run/host/etc/machine-id
+ return 1
or
+ echo toolbox: removing password for user martin
toolbox: removing password for user martin
+ passwd --delete martin
passwd: Permission denied.
I verified that FIPS mode works again, thanks! https://github.com/cockpit-project/bots/pull/983
cockpit-bridge is missing patternfly.css, which breaks cockpit-composer and every other consumer of that. Tracked in https://github.com/cockpit-project/cockpit/issues/14229
cockpit-bridge is missing patternfly.css, which breaks cockpit-composer and every other consumer of that. Tracked in https://github.com/cockpit-project/cockpit/issues/14229
This broke FIPS mode -- but too late now. I reported it as https://bugzilla.redhat.com/show_bug.cgi?id=1845806
Meh, this breaks authentication against AD. But too late now, I'll file a bugzilla.
Gating tests fail, they need an update: https://src.fedoraproject.org/rpms/cockpit/pull-request/20
This is not a failure of cockpit itself though, just that we forgot to update the tests before releasing.
This failure of testUsed
is persistent:
+ parted -s /dev/sda mktable msdos
+ parted -s /dev/sda mkpart primary ext2 1M 25
+ udevadm settle
+ echo einszweidrei | cryptsetup luksFormat /dev/sda1
Cannot wipe header on device /dev/sda1.
This is an actual regression in Rawhide, I filed https://bugzilla.redhat.com/show_bug.cgi?id=1824878 for it.
Please ignore the previous comment, that was meant for cockpit-podman, not this update.
Indeed, completely broken, same error. It's a syntax error in the seccomp profile: