Aren't you at all curious why it failed though? (If not, no harm no foul -- I certainly know time diagnosing a bug is always in short supply, from personal experience). What if it's a symptom of something important that might happen later even in Fedora 41?
Sometimes it just feels like containers are used as justification for devs to blow off bug reports. As a dev I want to understand why a failure occurs.
Agreed there -- it's good for onboarding devs and ensuring consistent build environment.
Once an app is 'stable' within a docker env, great -- but running it outside of a container will inevitably reveal lots of subtle issues that might be worth fixing (assumptions become evident when one's app encounters a different toolchain version, stdlib, or other libraries/APIs...). In this age of rapid development and deployment, perhaps most shops don't care about that since containers enable one to ignore such things for a long time, if not forever....
But like I said, I know my viewpoint is a losing battle. I just wish it wasn't used so much as a shortcut to deployment where good documentation of dependencies, configuration and testing in varied environments would be my preference.
And yes, I run a bare-metal 'pet' server so I deal with configuration that might otherwise be glossed over by containerized apps. Guess I'm just crazy but I like dealing with app config at one layer (host OS) rather than spread around within multiple containers.
Call me crusty, old-fart, unwilling to embrace change... but docker has always felt like a cop-out to me as a dev. Figure out what breaks and fix it so your app is more robust, stop being lazy.
I pretty much refuse to install any app which only ships as a docker install.
No need to reply to this, you don't have to agree and I know the battle has been already lost. I don't care. Hmmph.
UK should declare him an enemy of the state w/a standing arrest warrant with talk like that. Would serve him right to never be allowed over their airspace again.
Keyboard media keys (Fn + F keys, eg. vol mute, +/-, brightness etc.) do NOT yet work in mainline kernel. There is some good work going on over here on github but it's preliminary.
Also note kernel 6.10 broke the bottom display it would appear; I'm using kernel 6.13-rc4 currently.
I think it's a 'too soon?' thing... her home planet of Alderan(?) had just been blown to... well, asteroids earlier (well, previous movie, but still...)
If you happen to be trying to do this on a laptop with dual-graphics and the GPU is NVIDIA, it took me a while to find that one often can get proper GPU support by adding this just before wine (as in, right before it on the same command line):
Excellent. Resist.