You probably did this, but for anyone reading, if you copy commands from the internet, look up what all the commands and flags do to be sure you understand it fully, and then type it in yourself in a terminal instead of copy/paste. If you get an instruction to curl <something> | sh, split it into two steps, curl to get the script to a local file you can read, read it, then run if you know what it does. Do these things for anything you don’t trust 100%.
I did half of that. I looked at the commands to see what it did, what folders it made. Then I checked that the dockers pulled is the same from the official docker sites. I pasted the codes in rather than manual typing though. I’ve done this from sonarr, radar, audiobookshelf, jellyfin and sabnzbd.
The terminal commands to get dockers working I did copy directly from deepseek after checking it’s the same on docker’s site. Weird part is I tried to follow docker’s instructions first but it didn’t work. Then after looking at deepseek, it gave the same instructions from a different page of deepseek. So what I copied into command should have been the same.
Other than that I don’t really install anything as I’m quite paranoid about these stuff.
Good. To be honest I sometimes copy/paste too, but there is a possible trick to hide characters in the copied text with an automatic return at the end so when you paste you immediately run something you don’t intended. If I copy from some random shady blog I’d be more careful than from the official docker documentation I guess.
Nah I just ask deepseek. It set up a set of dockers for me in 2 minutes and also gave me commands to create my folder structures.
You probably did this, but for anyone reading, if you copy commands from the internet, look up what all the commands and flags do to be sure you understand it fully, and then type it in yourself in a terminal instead of copy/paste. If you get an instruction to curl <something> | sh, split it into two steps, curl to get the script to a local file you can read, read it, then run if you know what it does. Do these things for anything you don’t trust 100%.
I did half of that. I looked at the commands to see what it did, what folders it made. Then I checked that the dockers pulled is the same from the official docker sites. I pasted the codes in rather than manual typing though. I’ve done this from sonarr, radar, audiobookshelf, jellyfin and sabnzbd.
The terminal commands to get dockers working I did copy directly from deepseek after checking it’s the same on docker’s site. Weird part is I tried to follow docker’s instructions first but it didn’t work. Then after looking at deepseek, it gave the same instructions from a different page of deepseek. So what I copied into command should have been the same.
Other than that I don’t really install anything as I’m quite paranoid about these stuff.
Good. To be honest I sometimes copy/paste too, but there is a possible trick to hide characters in the copied text with an automatic return at the end so when you paste you immediately run something you don’t intended. If I copy from some random shady blog I’d be more careful than from the official docker documentation I guess.
That makes sense. What about AI answers, it feels unlikely for AI to do that.