Hacker News new | past | comments | ask | show | jobs | submit login

If you dont like running foreign code on your machine, you can run docker and then run foreign code on your machine.

Did anyone else catch this in the article? Doesn't it seem like this makes it even more likely to get infected? No one understands Docker in entirety let alone this random game. It seems like all this stuff should just be automatically done behind the scenes and yet it's not.




> It seems like all this stuff should just be automatically done behind the scenes and yet it's not.

...what stuff?


Whatever Docker is doing that your browser/OS/hardware isn't.

But that's the point. I have no idea what any of this stuff is actually doing. I'm just crossing my fingers that what I run isn't detrimental to my system. There's no actual understanding behind any of it anymore.


^ bot? Doesn't make any sense to me, OP link is not an article.


Their first line is a quote from the README.


Ah, ok. In any case I was TA with Pierre teaching that class at Chambéry this semester, to run the gamesaves from the student without being too worried about my files i just ran the thing inside a bubblewrap bash session:

bwrap --dev /dev --ro-bind /usr/bin /usr/bin --ro-bind /usr/lib /usr/lib --symlink usr/bin /bin --symlink usr/lib /lib64 --unshare-user --uid 256 --gid 512 --bind TP2 /TP2 /usr/bin/bash


Insert bwrap in lieu of docker and its the same thing. What the hell is bwrap?


Does no one think this is a problem? When even software engineers can't keep up with all these things, and your average citizen is completely clueless about how even the most basic of computer things work, do we not realize we are like the boiling frog in the pot?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: