-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add descriptions to containers on DockerHub #11
Comments
In the interests of constructive criticism, here as a counter-example is the dockerhub site I maintain for UPC++ users. This is admittedly a much smaller software distribution, but I think the user-facing design principles for dockerhub's "choose your download" page remain similar. Annotated comparison for illustrative purposes: |
Hi Dan,
Indeed, we need to do a better job of providing documentation for users who start at dockerhub.com rather than the e4s.io <http://e4s.io/> download page where we describe the base images and guide them as to which image to choose. With multiple GPU architectures (Intel, AMD, NVIDIA) x multiple OSes (Amazon Linux, Ubuntu, RHEL) x versions (Ubuntu 18.04, 20.04, E4S 21.05, 21.08, 21.11) x type (base, gpu, full), the number of Docker images has increased lately.
Thanks,
- Sameer
… On Dec 6, 2021, at 12:41 PM, Dan Bonachea ***@***.***> wrote:
In the interests of constructive criticism, here as a counter-example is the dockerhub site <https://hub.docker.com/u/upcxx> I maintain for UPC++ users. This is admittedly a much smaller software distribution, but I think the user-facing design principles for dockerhub's "choose your download" page remain similar.
Annotated comparison for illustrative purposes:
<https://user-images.githubusercontent.com/7160884/144915832-7a7047c1-947d-4af2-a19d-4ad45d9861d6.png>
<https://user-images.githubusercontent.com/7160884/144915609-6760a86b-8b68-4049-8a34-416415bb5d32.png>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#11 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAUHIOPFZBRO7AHGC5AHKP3UPUNYJANCNFSM5JKODPBA>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there a reason that most of the E4S containers at dockerhub have an empty description/overview?
Speaking as a user, when I visit https://hub.docker.com/u/ecpe4s and see 107 different multi-GB docker containers where most/all have empty descriptions, it's very intimidating to find what I need. It's not even clear which of these actually contain full/partial E4S installs and which only contain precursors that can be used to build/install E4S. Even given my knowledge of E4S, looking only at dockerhub I was unable to identify the "best" docker container to recommend for UPC++ users on a Linux laptop without GPU support.
If the "best" E4S containers for end users are really 50+GB, then I think it would be valuable to provide a rich description of the contents and any system requirements. This would give the user confidence he's downloading something useful and not just wasting his time/data.
It's also notable that the vast majority of those 107 docker containers have not been updated in over a year; I'm guessing these are effectively "dead" and just left around for legacy reasons? It might also be valuable to partition the dockerhub account into one that contains only the full-featured containers maintained with the latest E4S installed (ie the "product" intended for end-users), and a separate dockerhub account that contains "everything else".
The text was updated successfully, but these errors were encountered: