This search should obviously return the official Docker Hub Redis image, https://hub.docker.com/_/redis, but it’s just a bunch of blogs.
On DuckDuckGo the first result is the Docker Hub image, which is what everyone would want.
This search should obviously return the official Docker Hub Redis image, https://hub.docker.com/_/redis, but it’s just a bunch of blogs.
On DuckDuckGo the first result is the Docker Hub image, which is what everyone would want.
idk… the first two results seem both relevant and authoritative.
You may not be a developer, but the first expected result with that query would be a link to https://hub.docker.com/_/redis
Google is really bad at this for some reason and will point you to blogs that as a dev I don’t care in the slightest. Hell, using the same query I cannot find a single link to dockerhub on my device, it’s extremely frustrating
I’m a developer and I’d much rather have the docs. Who the fuck can remember FROM reddis?
The usage docs for the docker image should be in the dockerhub readme.
But the first result to the query
docker redis imageshould be the dockerhub entry, followed maybe by blog posts and tutorials.Otherwise you can query something like
redis docorredis docker tutorial.It’s important to look at the dockerhub page to see the available tags (I usually prefer smaller images like alpine)
It’s a garbage blog that starts as an ad for Docker Hub, that’s clearly not what I want.
Clearly? Your keywords are docker and reddis… here is a page, from docker.com talking about that exact thing.
How can you automate the relevance of the page? manually review? block all blog (some blogs are good).
Google uses signals, like you clicking on other links, to determine the quality of results, so your terminal click is the high quality result.
You complain the first result is an ad for docker hub, but your stated desired result is … docker hub…
But couldnt they active their brain during development? Or have for the big websites that have something special a special case?
for example on docker you dont want ugly Blogs from them you want the images if you ask for docker IMAGENAME. They know the path paterns /ORG/IMAGENAME.
If you have issues then you will query docker how to use IMAGENAME or similar then the blog would be perfect. Otherwise useless information.
your taking your human level domain specific knowledge of a specific site structure - and generalizing it to a search engine. How is the search engine going to know the best result to give you?
If a search is for docker NAME image so google shows users
Which result is going to get more terminal, and high quality clicks from searchers?
Realizing that many of the people who are using docker daily are either going to already go to the hub directly, or do site:hub.docker.com in some quick search bar
The population of searchers who find the A result more beneficial is probably higher then the B result, most people prefer step by step instructions and some hand holding when searching. The pros who have a groove and rythem, I suspect, have more direct ways to get what they want.
While google can improve, i’m not seeing this as gore, the relevant result this user wanted was the 5th link, and the first 2 links both got them there as well.
ok boomer then use “docker pull” why are you Googling it
Probably to lookup what are the possible environment vars for the container.
The second one is relevant official documentation tho
I’m confused then. If you were looking for a docker image, why not start in hub.docker.com?
I’m not an expert in containers, but I know enough to know if I am looking for an image, I go to docker hub.