You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think I also ran into this mismatch. The Dockerfile in the github repo refers to a debian bullseye base image, see here, but when running the container pulled from dockerhub, the sources.list have buster in there
docker run -it continuumio/miniconda3
(base) root@401d1aaaae79:/# cat /etc/apt/sources.list
# deb http://snapshot.debian.org/archive/debian/20210721T000000Z buster main
deb http://deb.debian.org/debian buster main
# deb http://snapshot.debian.org/archive/debian-security/20210721T000000Z buster/updates main
deb http://security.debian.org/debian-security buster/updates main
# deb http://snapshot.debian.org/archive/debian/20210721T000000Z buster-updates main
deb http://deb.debian.org/debian buster-updates main
Great if this could be fixed, so that using the miniconda base image allows to get the latest versions for other packages.
I'm trying to solve an issue with continuumio/miniconda3 and noticed that the dockerfiles in the Github repository (Debian image), https://github.com/ContinuumIO/docker-images/blob/master/miniconda3/debian/Dockerfile, does not match the one at Docker-Hub (Debian), https://hub.docker.com/r/continuumio/miniconda3/dockerfile.
Any idea why this is happening?
For the records, here is the dockerfile (copy-paste) from Github:
, here is the dockerfile from Docker-Hub:
.
The text was updated successfully, but these errors were encountered: