9 ms·
Docker desktop, unlike the docker command line tool and dockerd server, is not free software, and isn't even source available. It also transmits a HUGE amount o
by sneak 6y ago
Docker desktop, unlike the docker command line tool and dockerd server, is not free software, and isn't even source available. It also transmits a HUGE amount of sensitive data about your system to Docker without your consent, so it's spyware.
I can't really recommend avoiding this software any higher than I do. If you work on any sort of private codebases or under NDA, this thing is a liability magnet.
Install the free software command line tool via a package manager (not brew, that one is also spyware) and set
DOCKER_HOST="ssh://root@remotehost.example.com"
in your environment.
Don't develop with nonfree software and tools.
- nickjj 6y ago> It also transmits a HUGE amount of sensitive data about your system to Docker without your consent, so it's spyware. [...] If you work on any sort of private codebases or under NDA, this thing is a liability magnet. Can you please share a full list of what gets transmit with and without having the "Send usage statistics" option enabled? I'm assuming you have this data available because the wording of your reply is so specific.
- sneak 6y agoCrash it and look in $TMPDIR for a zip it uploads.
- wildrhythms 6y agoThe creation of a .zip file in $TMPDIR does not imply uploading.
- sneak 6y agoYou're right. The software uploading the zip is what plainly indicates uploading.
- GordonS 6y agoIt's been a long time since I had Docker Desktop crash on me (it seems to be very stable these days), but I was sure there was an optional "send crash report" button?
- sneak 6y agoIt sends spy data even when it doesn't crash, too.
- yladiz 6y agosneak, the commenter didn't ask how to reproduce it, they asked what it sends. What is in the zip file and what exactly does it upload when it crashes? Are you certain that it uploads the whole zip file upon a crash?
- sneak 6y agoThe commenter asked for free research, which I'm not about to reproduce for them (at a minimum it takes the time to format/reinstall a machine), so rather than not answer I told them precisely what they need to do to get the data they desire.
- nickjj 6y ago> The commenter asked for free research, which I'm not about to reproduce for them Not really. You specifically wrote that anyone using Docker Desktop is now liable for breaking NDAs and that a "HUGE" amount of sensitive data about your system is being sent to Docker without consent. I mean, I'm taking for granted here that you didn't wake up yesterday with intent to write those sentences without having ever done the research yourself at least once. You're the one making these claims. If you've done the research, why not just post it here so other folks can verify what you're saying? What I'm getting from your latest reply is you're trying to make it sound way worse than it is and are using a lack of information to guide folks into thinking the worst case scenario by filling in the gaps with their own interpretation of what you wrote. Transmitting a crash dump is much different than them sending sensitive data without your consent, especially considering you can turn the "send usage stats" option off which no longer sends crash dumps, and the dump itself is only sent on a crash. Also the help text under the option says that it sends crash dumps too. Your original reply made it seem like every time you run a container with a volume, the contents of your source code is sent to Docker because in a lot of people's minds that's a "HUGE" amount of sensitive data and ties into your "private code base" and NDA liability sentence before.
- sneak 6y ago> I'm taking for granted here that you didn't wake up yesterday with intent to write those sentences without having ever done the research yourself at least once. You're the one making these claims. If you've done the research, why not just post it here so other folks can verify what you're saying? I have provided specific instructions for verifying precisely what I'm saying. I'm not going to spend hours reproducing this simply because I'm being cross-examined in a comment. It is immaterial to me if you believe my reports of the truth or not.
- jfk13 6y ago> Don't develop with nonfree software and tools. Don't try to dictate to others how they should work, as though you're some kind of oracle on the topic. I'll decide (together with my employer, when appropriate) what software and tools to use, based on a range of factors. Free-ness may be one of those factors, but it doesn't get to unconditionally veto everything else.
- cmeacham98 6y agoIt's just a strong recommendation, GP isn't pretending to have authority over HN commenters. This type of 'command as suggestion' construct is pretty common in modern english.
- deleted 6y ago[deleted]
- sneak 6y agoNo, it's not a suggestion, it's definitely a command. Don't use nonfree tools, or you'll become a sharecropper ripe for abuse, such as the complete and utter "it's our computer now, fucko, even though you paid for it" nonsense demonstrated in TFA. Free software can't behave like this because the moment it tries we'll simply patch it out. See also: vscodium, ungoogled chromium.
- ratww 6y ago> vscodium Wow, I had no idea this existed. Thanks for mentioning it. I block the telemetry with settings and with Little Snitch, but this is what I needed from the beginning.
- vikbytes 6y agoJust as a warning, if you use vscodium you will not be able to use some extensions, including Remote-SSH.
- 6y ago
- thwave 6y ago> not brew, that one is also spyware how is brew spyware?
- sneak 6y agoIt transmits your on-device activity to Google without consent. It includes a unique tracking identifier generated on install that never changes, like a supercookie. Every time you run brew, it transmits this to Google, which allows Google to assemble a city-level tracklog of your device based on client IP geolocation, along with a list of all the packages you have installed, and when. It does this silently, and without obtaining any sort of consent, which is why most people are unaware that homebrew is spying on them.
- sofixa 6y agoWhy to Google?
- sneak 6y agoYou'd have to ask the homebrew developers that. Every time I've ever seen anyone question their decision to embed Google spyware in their product, however, the GitHub issues are closed and locked, so I don't know if you'll have very good luck. I stopped trying to convince them to behave ethically and simply use nixpkgs now instead (which incidentally in my experience works better) and do my best to inform people about the facts so they can make their own decisions (something I wish homebrew would do, instead of deciding for them to use their computer to spy).
- deleted 6y ago[deleted]
- ratww 6y agoIt uses Google Analytics.
- 6y ago
- driverdan 6y agoI opened this ticket 3.5 years ago and they still violate GDPR https://github.com/docker/for-mac/issues/2122 https://github.com/docker/for-mac/issues/2122