1385
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 22 Apr 2026
1385 points (100.0% liked)
Technology
84143 readers
1977 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
Because jailing a container is even harder than jailing an application. "But a container is already jailed" you'll say - I don't trust any jail that I can't choose & configure myself.
How about: document the requirements for the execution environment (in industry this is called an interface definition document), based on which the gaming community can then generate their own container configs if they like, but no one has to run stuff in a container.
Fair enough.
Also a good solution but you will end up in a container anyway once the requirements will become too old to be satisfied on a current OS.
That might be - but depending on the platform, that container is trivial or not necessary at all (e.g. wine on Linux still runs 16 bit executables with just a config file). Also, until then, I can continue to run the game without worry. E.g. Unreal Tournament 99 still worked out of the box (last I tested) on Debian 12 - haven't tried it yet on Debian 13.