You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ci: dietpi-software test: workaround for failing MariaDB on Forky
Mount namespacing fails since systemd 259-rc1 with QEMU-emulation. This will cause a lot more services to fail, as common as sandboxing is, but doing a start with MariaDB.
Also merging QEMU-emulation relaeted workarounds together.
# Workarounds for QEMU-emulated RISC-V and 32-bit ARM containers
488
-
if((( $arch<3||$arch==11 ) &&$emulation))
470
+
# Workarounds for QEMU-emulated containers
471
+
if(($emulation))
489
472
then
490
-
# Failing services as PrivateUsers=true leads to "Failed to set up user namespacing", and AmbientCapabilities to "Failed to apply ambient capabilities (before UID change): Operation not permitted"
# Failing services as PrivateUsers leads to "Failed to set up user namespacing", and AmbientCapabilities to "Failed to apply ambient capabilities (before UID change): Operation not permitted"
# Forky: ProtectHome/ProtectSystem/PrivateTmp/...: "Failed to set up mount namespacing: Invalid argument": https://github.com/systemd/systemd/issues/39951
G_EXEC sed --follow-symlinks -i "/# Start DietPi-Software/i\sed -i 's/192\.168\.42\./$(G_GET_NET ip | sed 's/[0-9]*$//')/g' /boot/dietpi/dietpi-software" rootfs/boot/dietpi/dietpi-login
530
523
fi
531
524
532
-
# Workaround for Apache2 on emulated RISC-V system
0 commit comments