Update README on https://hub.docker.com/r/jupyter/repo2docker
See original GitHub issueIf someone has push rights to https://hub.docker.com/r/jupyter/repo2docker I think it’d be good to:
- Manually push
quay.io/jupyterhub/repo2docker:2021.08.0
and alatest
tag to Docker Hub - Manually update the docker Hub readme to deprecate the Docker Hub image and point to quay.io
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
jupyter/repo2docker - Docker Image
Moved to quay.io/jupyterhub/repo2docker. This repository is deprecated and no longer receiving updates as of September 2021.
Read more >Changelog — repo2docker 2022.10.0+67.gab4c4f2 ...
Version 2022.10.0: Full changelog New features: Update Jupyter dependencies PR #1193 ... GitHub workflow build and push to Docker hub PR #1071 by...
Read more >repo2docker image - PrimeHub
repo2docker is a tool to simplify building a jupyter-notebook based image without giving a Dockerfile. We could put configuration files to make it...
Read more >Repo2Docker: make it easy to start from arbitrary docker image
Related GH issue: https://github.com/jupyter/repo2docker/issues/487 ... We can now provide a dockerhub image tag along our scientific publications, ...
Read more >https://pilot-hubs.2i2c.org/en/latest/_sources/how...
The image is built and pushed using [jupyterhub/repo2docker-action](https://github.com/jupyterhub/repo2docker-action) to the [2i2c-hubs-image ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah, I totally get it. I don’t mean to imply I’m unhappy with the decision. Fully support shifting to quay.io, especially given that we can’t even give ourselves enough permissions to update the README!
Thanks for updating the readme!
I don’t think you were in last months team meeting where we decide to move repo2docker to quay.io. Part of the reason was a lack of confidence in Docker Hub’s long term viability given Docker’s funding issues. However this is probably worth a team discussion… I’ll add it to today’s meeting agenda.