• 0 Posts
  • 47 Comments
Joined 2 年前
cake
Cake day: 2023年6月20日

help-circle




  • Yeah, I used a 1070 on arch for years without any issue, recently switched over to an Intel arc gpu and that gave me way more problems (admittedly most of it was my “fault” for being on an old mbr scheme, needing to enable rebar, and needing to switch from xorg to wayland… but that’s just what happens when a graphics card is so stable you don’t feel the need to reinstall your os or change anything major). I am not hired by Nvidia nor do I support their business practices when it comes to making development on Linux difficult or creating proprietary standards like cuda, just stating my personal experience with their drivers.



  • People have always been out for themselves, it’s not the fault of religion and religion is not the solution. Religion can give an outlet to those looking for structure and community in their lives, this can both be used for good and exploited in equal measure. The reason it feels more common that people are out for themselves is 3-fold: the internet has caused a weird bubble culture where you feel the need to make a name for yourself within the social media you are consuming especially with a growing population where it’s harder than ever to feel like you even matter, a growing divide in economic class where the people at the bottom feel the need to pull themselves up any means necessary, and an increased amount of rich people being given a platform to preach their success/luck to anyone they want as an additional status symbol whether or not it’s moral or even true












  • If the script is working like that it implies that your working_dir is / inside the container, hence why your python script can write to ./data instead needing to say of /data with the absolute forward slash. To my knowledge volumes cannot be mounted that way because the working directory inside the container is constantly changing, but you can set the initial working directory to /data. If you don’t want the python script inside the data folder/working directory but still want to be able to call it without specifying a path to the script you’ll need to copy it into a bin folder. So in summary you would have the script in bin, your working directory would be /data which would be associated with your machine’s directory you used when starting the docker-compose and the script would just use the path ./

    Edit: another option if you can’t change the starting working directory is simply to cd first: cd /data && yourscript