fix: ensure /var/run is a symlink to /run

[LukeShortCloud]

No description provided.

[LukeShortCloud]

The Playtron team has been testing using the ghcr.io/ublue-os/ucore-minimal:stable-nvidia image being installed to a raw image file via both Anaconda and, separately, via bootc-image-builder. Both result in failed services because they are unable to communicate with the system's DBus interface. We found that, for some reason, /run and /var/run were both different directories. By testing a change of /var/run to be a symlink that points to /run via a layered UBlue image, services are now working.

[LukeShortCloud]

We found that underlying issue was that installing some packages generated content in /var/run, thus making a new directory because it did not exist before. bootc automatically creates the /var/run to /run symlink only if /var/run does not exist. Otherwise, it will leave it as-is. This explains why Bluefin and others never ran into this problem. Using rm -r -f /var/run or ostree container commit at the end of our customized Containerfile fixed the issue. Apologies for the noise!

[LukeShortCloud]

By the way, on a related note, we were previously using ostree container commit everywhere but then dropped it as part of our transition to bootc due to the latest recommendation:

"You may find some references to this [ostree container commit command]; it is no longer very useful and is not recommended."

https://containers.github.io/bootc/bootc-images.html#the-ostree-container-commit-command

I guess the "correct" way forward is just to have RUN rm -r -f /var/run at the end of the Containerfile (or along with related commands that generate it).