• 1 Post
  • 111 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle
  • Did you get it running already? If so, happy to have helped :) It’s a bit tricky to move your downloaded games into the jail so that you don’t have to re-download, I think maybe it’s just easier to download them again as you start playing them. I started with a jail right from scratch so I only ever tried moving my games files between different jails, that was easier (but can still be done wrong).


  • On debian testing (trixie):

    $ cat bin/steam-jailed.sh

    #!/bin/sh
    firejail --private=/home/user/steamjail --profile=/etc/firejail/steam.profile ~/steam $1
    

    Sometimes an update breaks something, and I have to experiment with the profile settings, for which it helps to launch a bash with the same jail and start steam on the command line inside the jail to see output messages.

    #!/bin/sh
    firejail --private=/home/user/steamjail --blacklist=${HOME}/.inputrc --profile=/etc/firejail/steam.profile bash
    

    What happens most of the time is that a steam update depends on a newer system library that I didn’t yet install and I then have to do a system update - steam is shit at managing OS dependencies (i.e.: it doesn’t)
















  • While security has nothing to do with my disgust for docker and people advocating its use, docker adds a layer of complexity, which means it is not necessarily more secure.

    What is extremely bad about docker:

    1. it enables extremely shitty configuration control on the side of a developer. There are way too many developers who have a chaotic approach to configurations, and instead of being forced to write a proper installation and configuration guide from scratch, and thereby making themselves(!) aware of active configuration changes they made to make their system work, they just roll out the docker container they develop in, without remembering most of the configurations they made. Which, naturally, means that they are unable to assist in troubleshooting problems or reproduce issues that users might have.

    In general, if you can’t write a good user manual, or at least clearly identify needed dependencies and configurations, you should not be developing software for other people.

    1. it combines the disadvantages of a VM (shitty performance) and running directly on the host OS (sandboxing is not nearly as good as on a VM)

    2. it creates insane bloat, by completely bypassing the concept of shared libraries and making people download copies of software they already have on their system

    3. it adds a lot of security risks because the user would have to not only review the source code they are compiling and installing, but also would have to scan all the dependencies and what-not, and would basically have to trust the developer and/or anyone distributing an image that they did not add any malware.