-
Notifications
You must be signed in to change notification settings - Fork 7.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Download Docker CE without logging in #6910
Comments
I know that this can feel like a nuisance, but we've made this change to make sure we can improve the Docker for Mac and Windows experience for users moving forward. As far as I can tell, the docs don't need changes, so I'll close this issue, but feel free to comment. |
Thank you for your response. I hope you’ll keep the direct download URL available for the foreseeable future. |
Um, what. Is Docker closed-source freeware all of a sudden?
Uhuh. You mean, force people to login with an email so we can target them with an ad campaign so we make money?? This feels dishonest. If you're trying to make money, say so. 'improve user experience' is the oldest, lamest excuse in the book... You just made the 'user experience' suck by putting it behind a login-wall. One click installers are not new...and you don't need e-mail specific identifiers to collect install logs. I'm calling a giant load of baloney on this one. |
I just want to download Docker, not to receive once again a metric ton of spam. |
Just loged in with a spam email address and will create with a new spam email address everytime i want to download it. |
Wow. This is a really shitty move. |
This not only feels like it, this IS a huge nuisance. This is stupid, change it back. |
I have a docker account already because I publish container images, but for consumers that just run images, this is a huge annoyance. Please reconsider this change. For now, it would appear the direct link still works without logging in, but I wouldn't count on that being valid much longer: https://download.docker.com/win/stable/Docker%20for%20Windows%20Installer.exe |
Jerks. |
Let's put it behind a loginwall! |
This is disgraceful. |
Here is the link for macOS |
Such a shame you guys force devs into your store to get what's already publicly available for download. Must be marketing department that thought that's a good move. |
Welp, this is enough motivation for me to keep my eyes open for an alternate to Docker. There's legitimately zero reason to hide it behind a login, and if there are good reasons I'd think this would be a great opportunity to share them. |
@Nexi89 Just for completeness, here is the link for the edge version as well |
Do you want to be Oracle? Because this is how you become Oracle. 👎 |
A download without the login requirement is a much better user experience IMO. |
Well, you know the market power of docker and try to get more information of your users. thats okay but it will not help to spread the docker love and it will not motivate people to develop more apps and services depending on docker, because noone wants to force his users into that marketing/registration shit. |
Yeah, this is an issue. Previously, Docker was free to download. Now I have to pay with my email address and information? Not cool. |
If Docker CE license is Apache 2.0 you must let people download it without asking for an account. |
@alexkit I don't think that's true. However, the Apache license does allow someone to create an account, download it, and then distribute it themselves, without requiring registration. So someone could create a github repo with the latest releases there, and that couldn't be stopped. If someone were to do that, then docker would get even less analytics about the number of downloads. |
Docker Toolbox can be an alternative as well. |
This makes for a really bad user experience. |
The point is that people are already looking for alternatives. Not sure this is what you really wanted... This reminds me of “Who Moved My Cheese”, look for early changes and start looking for “New Cheese” :) |
How ? How is this extra step and data collection helping the user in any way ? |
Thank the community for cri-o |
So this seems like a popular choice. Definitely don't walk it back ever; you know, pride and all. |
Uh-oh, guys, you finally got me to take care for other alternatives. |
What an absolute dick move. Whenever I want to download Docker I always download it via the Links provided on here. Prepare for even more anger should you take away the ability to directly download these files. Seriously Docker should know better. Here are the direct download links again: |
When including a Linux link for our users (Docker is a dependency of our tool), instead of the binary listings above, we have found it more helpful to send Linux users to the place in the docs where distro-specific Docker installation instructions branch out. This way they get instructions if they have old versions to uninstall first, want to use a package manager, etc.: https://docs.docker.com/install/#server And now as our ancestors on issue 6910 have taught us, here are links for end-of-thread convenience. Code blocks for easy copy pasta ( HTML: <a href="https://download.docker.com/mac/stable/Docker.dmg">Mac</a>
<a href="https://download.docker.com/win/stable/Docker%20for%20Windows%20Installer.exe">Windows</a>
<a href="https://docs.docker.com/install/#server">Linux</a> Markdown: [Mac](https://download.docker.com/mac/stable/Docker.dmg)
[Windows](https://download.docker.com/win/stable/Docker%20for%20Windows%20Installer.exe)
[Linux](https://docs.docker.com/install/#server) |
Sounds more like a good way to make people do that anyway. I know I personally create new issues if old ones are ignored. Ignoring the majority does not work, it never does. If you don't ignore an issue, on the other hand, and merely own up to the fact that you are committed to not fixing it and close the issue, instead of trying to motivate you to fix it I can just give up on your project altogether. |
I respectfully agree with most of the comments here, requiring registration/login for downloading docker is not good. It imposes things that not all people might agree with and it adds one more stop-wall for using your awesome software. Keep doing good things and do not be evil. |
Pretty soon you'll be able to use podman in Windows via WSL2. Then nobody will need "Docker Desktop", let alone want it. |
I just want to call out that this single change has resulted in every company I have worked at looking for alternatives to docker as they see it as a SECURITY RISK that they need to login like this. Simply put, a software developer's email at a company is sometimes seen as internal/security-sensitive information. Most devs don't need to be public-facing and so anything that adds spam or another email to their inbox just adds a distraction and a possible attack vector by hostiles (Technical Recruiters looking to pouch people, salespeople who think they are smart, active attacks on the company via Phishing emails, etc) willing to abuse it. Either way, companies don't want outside third parties emailing their devs while the devs are trying to stay in the zone and productive, and so any form of marketing email/spam sent to them is considered a hostile attack on their business. Companies don't want this BS, and clearly based on the responses here, neither do the developers that make the choice to use your tech or not. In the end, this has created an all-out war on docker in some of the places I have worked since this change was made; it has utterly destroyed the value proposition that docker had, and since there are other options in the market in many cases the competitive landscape is basically now saying that the freest and most open version of this tech is what is market competitive. So at this point, forcing people to log in to do this is just shooting yourself in the foot and closing you off from potential customers because you are not seeing the number of people who hear they have to login/register and simply say "F*ck it, I will use this other alternative" just so they don't have to deal with the BS this will generate, and no amount of market telemetry will tell you the sheer disgust devs - who in the end make the technology choices for the companies they represent - have for this BS. So I'm respectfully joining the chorus of developers telling you. So congrats, you pissed off a lot of devs who make the choice on if they use your companies tech or not, and shot yourself in the foot. You told every company that previously trusted you that you think you are too big and important to keep doing things the right way and allow their devs to work in peace because now a company has to factor in the added cost of dealing with random marketing emails from your company to their possibly already limited regulatory compliance budget. Yes, I have had actual talks with execs about this issue, and the kindest exec I ever knew swore for the first time I have never heard him do so while mentioning your company and this change. Congrats, you made a kind man I respect hate you. In the end, this change showed the world that you don't consider developer goodwill is the most important thing to have on the balance sheet. and by doing that you have shown that it's in our best interest as developers to not use your platform if we can do so, if we value our privacy and security and being interrupted by marketing spam. That's why devs are posting download links here. Simply put. You have pissed off people who are otherwise forced to use your product as some part of a third party dependency chain, and this makes us want to use them less, so you're hurting your partners and prior supporters, too. I sincerely hope you undo this terrible choice; If only for what docker could have been. |
Someone should keep a copy of this issue for the inevitable "The preventable death of Docker: Why did Docker fail as a project and how could it have been easily prevented?" article some day ;) |
Hi everyone! So, I’ve been following this thread since the start. With Docker’s new direction to go back to its roots and focus on developer tooling, we were given the “go ahead” to remove the login last month, and I’m happy to announce that the login has now been removed (w00t!) There might still be links pointing to the wrong location, so if you happen to find one, please open a ticket (or even greater: a pull request) to fix it (feel free to @ me on those for review/merge) |
Also a big shout-out to @nebuk89 for getting this done 🤗 |
Brilliant news, thank you @thaJeztah & @nebuk89 for following this and listening to the pain points of the community. |
What about the installation requirements? They seem bad to me. You should not be checking the OS version or type, you should be checking for individual subsystems already installed. |
I think that is a bit out of scope of the current issue's topic. As a sidenote, Ubuntu & Debian have different repo names or prerequisites for instance, so I don't think it's something they can change. Hey, if everything was equal in all Linux OSes for instance, everything would be better, but that's open-source for ya. On-topic: Awesome move listening to the community - it took a long while, but it seems you've finally realized how big this issue was, so big kudos! |
I'd have less problem with a password requirement if the "forgot password" link would send the promised email. Which it doesn't. |
Yes, that's off topic for this thread. I'll reply briefly, but if there's specific issues around that, it's better top open a ticket in the docker for mac or docker for windows issue tracker. The really TL;DR is that Docker Desktop tends to use (sometimes "bleeding edge") features that might not be available in specific versions, or not finalised yet in the platform (macOS/Windows). While I agree that "feature detection" would be good for this, we sometimes have to outweigh the pros/cons, also to make sure we don't "overcommit"; there's literally millions of active daily users of Docker Desktop, and a (relatively) small team of engineers. "YOLO'ing" packaging out the door for platform versions that we haven't completed work on / tested yet could lead to massive amount of bug-reports that we wouldn't be able to address in a timely fashion. That's not the experience we'd like you to get, so sometimes we need to make the unpopular decision to "not support" them. (It's definitely noted though!)
Linux distribution / packages are slightly different. First of all (as there has been some confusion about that in this thread), the whole discussion above never applied to those packages (as in: there's never been a password/registration required for our Linux packages at download.docker.com). Contrary to Docker Desktop (Docker for Mac/Win), which are built using open source components, but also contains proprietary code, our Community Edition Linux packages are, and have always been fully open source; all source-code and packaging scripts can be found on GitHub. There are parts of our packaging pipelines that are currently in private repositories; these pipelines integrated into various pipelines related to the enterprise products, which resulted in them not being as "flexible" as we want them to be (they grew to become quite complex). As a result adding new distros (or distro-versions) to our list of packages could not be done easily between releases. We currently have a team of engineers refactoring the pipelines; getting rid of integrations we no longer need, simplifying the process, and open-sourcing them. Once that's done, things should become more flexible. We'd still reserve the right to limit the list of distro's to build for (the number of Linux distributions that exist is massive, and we can't do all!), but we should be able to accept contributions to provide easier steps to build your own package. These things take time, so "hold on tight" while this is being worked on 🤗
We get thousands of registrations and password resets; it's possible there's been a hiccup. Make sure it's not blocked by a spam filter, and you're checking the primary e-mail account (lame answer, but these are still the most common reason for these e-mails to get lost). If you're absolutely sure those are not the cause; feel free to head to https://hub.docker.com/support/contact/ |
Let's all download Docker a few times to show our appreciation and bump up team's KPI 🤣 |
With #6910 (comment) and my answers in #6910 (comment), I think this issue is resolved, so let me close it 👍 |
Yeah, I'd love to know as well.
…On Sun, Apr 11, 2021 at 7:49 AM Ke Han ***@***.***> wrote:
I know that this can feel like a nuisance, but we've made this change to
make sure we can improve the Docker for Mac and Windows experience for
users moving forward.
As far as I can tell, the docs don't need changes, so I'll close this
issue, but feel free to comment.
hi there, you claimed that Docker needed to be downloaded with account on
2018, and the restrictions has been lifted since 2020.
so, mind to share with the community what are the "improvements" made due
to this restriction imposed previously?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6910 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIEMV3TKQIZVBLV274QVRTTIGEF5ANCNFSM4FF254HA>
.
|
Is there any way to run docker on windows without accepting service agreement and without any user accounts which is not deprecated like docker toolbox? |
WSL2. Just install via |
I don't think my windows version supports WSL2, but podman looks nice. Thanks UPD; podman can't actually run without WSL2 too. So I need either WLS2 or some remote server. Both are not what I'm looking for |
This might be a surprise to many but docker never ran natively on windows and never will. With docker desktop you could use WSL2 or externally created VM with docker installed on it. Even if you can't use WSL2 you can simply vagrant up Ubuntu VM and use podman remote to use it. |
Allow me to enlighten you a little bit on how Windows works: There's a version called LTSC which is basically an old version of Windows that doesn't support WSL2, it has way less bloat and it's made mainly for enterprise installs. Such version works like any LTS version where it will work as best as possible (and it does) while also receiving all security updates to date. I've been using LTSC as my daily driver without any issues aside from not being able to install Docker on WSL2, which is not a big deal as it's something a VM can deal with pretty easily. So, before blatantly calling someone's OS ancient and assume they're going to have "many issues" and saying "Upgrade", do a little bit of research. Plus, newer versions of Windows do have issues with updates. Win10 LTSC is Version 10.0.17763.2114 and it works so well that I haven't reinstalled my system (unlike other machines I have at home with the latest Win10) in a couple years so far. |
shocked_pikachu.jpeg On Saturday, April 27, 2019, 1:22:23 PM GMT+9, Tobe Osakwe ***@***.***> wrote:
Great work, y'all.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. /lifecycle locked |
Problem description
Docker for Mac and Docker for Windows cannot be downloaded without logging into Docker Store.
Problem location
Suggestions for a fix
It would be awesome if Docker for Mac and Docker for Windows could be downloaded without logging into Docker Store as not to make users jump through hoops. This was already previously possible, if I remember correctly.
The text was updated successfully, but these errors were encountered: