continuumio / docker-images Goto Github PK

View Code? Open in Web Editor NEW

809.0 91.0 281.0 571 KB

Repository of Docker images created by Anaconda

Home Page: https://hub.docker.com/u/continuumio/

Dockerfile 99.48% Makefile 0.52%

docker-images's Introduction

Anaconda and Miniconda Docker Images and Documentation

Docker images for Anaconda/Miniconda that are available from DockerHub:

https://hub.docker.com/r/continuumio/

Documentation for Anaconda Integrations, including Docker:

https://docs.anaconda.com/anaconda/user-guide/tasks/docker/

Package build images hosted on ECR can be found here:

https://gallery.ecr.aws/y0o4y9o3/anaconda-pkg-build

Package build images hosted on DockerHub can be found here:

https://hub.docker.com/r/continuumio/anaconda-pkg-build/tags?page=1&ordering=last_updated

image	description	version	pulls	stars
anaconda3	Container with a bootstrapped Anaconda installation
miniconda3	Container with a bootstrapped Miniconda installation
Anaconda Package Build	Container with a bootstrapped Anaconda installation with GCC

Updating and publishing Docker images

Docker images are updated by changing the appropriate Dockerfiles in each subdirectory. For Miniconda (miniconda3) and Anaconda Distribution (anaconda3) this is automatically done by renovate.

To publish a Docker image, a release has to be created. The scheme for the release tag name is specified in each workflow file, for example:

on:
  push:
    branches:
      - main
    tags:
      - 'anaconda3-*'

If an image with the same version needs to be republished, the version number should be amended with .postN where N is an integer.

Automatic updates using renovate

Docker images using the Miniconda or Anaconda Distribution installers can be updated using renovate.

Updates with sha256 checks

To update Dockerfiles that contain sha256 checks, the full URL and sha256 sums need to be provided for each installer:

# renovate datasource=custom.miniconda
ARG INSTALLER_URL="<URL to installer file>"
ARG SHA256SUM="<installer checksum>"

The sha variable must be in the line beneath the installer URL. For Anaconda Distribution, the datasource must be changed to custom.anaconda.

The variable names can have suffixes if there are multiple installers in one file, for example:

# renovate datasource=custom.miniconda
ARG INSTALLER_URL_LINUX64="<URL to linux-64 installer file>"
ARG SHA256SUM_LINUX64="<linux-64 installer checksum>"
# renovate datasource=custom.miniconda
ARG INSTALLER_URL_AARCH64="<URL to linux-aarch64 installer file>"
ARG SHA256SUM_AARCH64="<linux-aarch64 installer checksum>"

Simple version number updates

If not checksums are needed, the Dockerfile can be simplified:

# renovate: datasource=custom.miniconda depName=Linux-x86_64.sh
ARG INSTALLER_VERSION=<installer version>

Linux-x86_64.sh can be replaced by any installer suffix supported in the latest release.

docker-images's People

Contributors

Stargazers

Watchers

Forkers

zgrnk adgaudio elevate rgbkrk jakirkham erichhuang truffls kcompher bjodah xsongx ericadams-di msarahan kvnvodo ataniazov dfanchon zscore mdbishop briney gregkoytiger beingzy jiapei100 jfeala minkvsky intelivix rlugojr harisbeha tmulc18 nturaga outmanzhaohu marcellodesales evenstrangest hjkuijf sylarchen daviskirk dhj-io kosecki123 mwojcikowski openkbs yassyskywalker nontas digideskio anthony-coder leipzig tonystank3000 jessewei jobel-aqua jkhoogland tyler-thetyrant ssanbu08 trib3 kazeka wscholar wipadachan ashander jamesferry11 booyaa tcing hdfeos jbi35 matrixquery thoo contaconta ifarhankhan quantmatic mapcloud zwylnzm jjhelmus pldimitrov soulthym haru01 jn7163 shunderpooch gorbachev julin ahhn anthonyebert cglewis ianfiske kineticskunk snowch geojackass mpower4ru mrdivine www3838438 hayderimran7 sujit-fm xxxhycl2010 mrocklin ryankresse hrishikeshac nehaljwani mbargull wkbiz-github jgiret koash lcnja roychou121 navneet1075 kashenfelter zedyeung

docker-images's Issues

anaconda 4.4.0 has incorrect python version

I am using the anaconda3 docker. when trying to install python3.4, I get an error:
UnsatisfiableError: The following specifications were found to be in conflict:

python 3.4*
testpath -> python 2.7*
Use "conda info " to see the dependencies for each package.

It seems like python 2 is used inside the docker

When I use anaconda 4.3.1 everything works fine

Anaconda/Miniconda Docker images for Fedora, CentOS, RHEL

Not sure where/how to build a grid of anaconda versions vs OS versions w/ Docker images and Dockerfiles (e.g. Packer)
- dox does something like this (tox + docker => dox)
RPMs would be helpful
- context labeling
-<osname.majver> (./anaconda-fedora-22, ./miniconda-fedora-22)
fedora, centos, rhel, epel?

continuumio/anaconda docker image Kernel Dies

Not sure why this keeps happenning to me, but my kernel keeps dieing on my Docker image from continuumio/anaconda. I try running the container with the following command:
docker run -i -t -p 8888:8888 continuumio/anaconda /bin/bash -c "/opt/conda/bin/conda install jupyter -y --quiet && mkdir /opt/notebooks && /opt/conda/bin/jupyter notebook --notebook-dir=/opt/notebooks --ip='*' --port=8888 --no-browser"
and I end up with "an unexpected error has occurred", which I would presume relates to this:
conda/conda#3935

Should I try to re-install anaconda/update conda on my local machine before trying to use the container? Is the container using my local kernel of Python? Any help would be appreciated.

miniconda3 on alpine linux

Would it be possible to add a version of the dockerfile using alpine linux instead of full debian? This would make it much faster to download and upload.

See example for redis on alpine:
https://github.com/docker-library/redis/blob/6cb8a8015f126e2a7251c5d011b86b657e9febd6/3.2/alpine/Dockerfile

Can't install anything with gcc and pip in Miniconda 4.3.27

unable to execute 'x86_64-conda_cos6-linux-gnu-gcc': No such file or directory error: command 'x86_64-conda_cos6-linux-gnu-gcc' failed with exit status 1

Re-order PATH?

Currently the Dockerfiles for miniconda prepend the conda bin directory to the $PATH:

ENV PATH /opt/conda/bin:$PATH

miniconda
miniconda3

This causes problems if a conda package gets installed that has an executable that shadows an executable already in /usr/bin, for example. It seems like the conda directory should be placed after the $PATH. The default $PATH includes /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin.

Is there a reason for this ordering I'm not thinking of?

Miniconda 4.4.x docker image

It's been a few weeks since 4.4 has been released. Is it possible to update the Docker image to use it?

Please upgrade the Dockerfile to resolve build failures due to a bad conda release

Building Docker images based on the continuumio/anaconda3 image fail with:

unable to execute 'x86_64-conda_cos6-linux-gnu-gcc': No such file or directory
error: command 'x86_64-conda_cos6-linux-gnu-gcc' failed with exit status 1

This happens, for example when building menpo python module to include in the Docker image.

From what I can gather this is an issue with the 9/27 conda build having a bug. This has since been fixed and a new release is out on 10/2, if I followed the discussions on this correctly. However, the Dockerfile in this project hasn't been updated to include this new release.

I believe the 5.0.0.1 releases at https://repo.continuum.io/archive/ would fix this?

Please address container security issues in anaconda3 docker images

I was running the anaconda3:latest image through Anchore scanner and it flagged an incredible amount of security vulnerabilities many of which may stem from being based off of debian:8.5 as opposed to debian:8 or debian:8.9.

While most people probably don't run images unprotected on the internet, this container is rife with vulnerabilities.

There are:

52 High risk vulnerabilities
29 Medium risk vulnerabilities
114 Low risk vulnerabilities

Here's what it flagged:

Low Vulnerability found in package - bash (CVE-2016-9401 - https://security-tracker.debian.org/tracker/CVE-2016-9401)
Low Vulnerability found in package - bzip2 (CVE-2016-3189 - https://security-tracker.debian.org/tracker/CVE-2016-3189)
Low Vulnerability found in package - coreutils (CVE-2016-2781 - https://security-tracker.debian.org/tracker/CVE-2016-2781)
Low Vulnerability found in package - curl (CVE-2017-7407 - https://security-tracker.debian.org/tracker/CVE-2017-7407)
Low Vulnerability found in package - gcc-4.8-base (CVE-2017-11671 - https://security-tracker.debian.org/tracker/CVE-2017-11671)
Low Vulnerability found in package - gcc-4.9-base (CVE-2017-11671 - https://security-tracker.debian.org/tracker/CVE-2017-11671)
Low Vulnerability found in package - krb5-locales (CVE-2016-3119 - https://security-tracker.debian.org/tracker/CVE-2016-3119)
Low Vulnerability found in package - krb5-locales (CVE-2017-11462 - https://security-tracker.debian.org/tracker/CVE-2017-11462)
Low Vulnerability found in package - libbz2-1.0 (CVE-2016-3189 - https://security-tracker.debian.org/tracker/CVE-2016-3189)
Low Vulnerability found in package - libc-bin (CVE-2015-5180 - https://security-tracker.debian.org/tracker/CVE-2015-5180)
Low Vulnerability found in package - libc6 (CVE-2015-5180 - https://security-tracker.debian.org/tracker/CVE-2015-5180)
Low Vulnerability found in package - libcurl3 (CVE-2017-7407 - https://security-tracker.debian.org/tracker/CVE-2017-7407)
Low Vulnerability found in package - libcurl3-gnutls (CVE-2017-7407 - https://security-tracker.debian.org/tracker/CVE-2017-7407)
Low Vulnerability found in package - libgssapi-krb5-2 (CVE-2016-3119 - https://security-tracker.debian.org/tracker/CVE-2016-3119)
Low Vulnerability found in package - libgssapi-krb5-2 (CVE-2017-11462 - https://security-tracker.debian.org/tracker/CVE-2017-11462)
Low Vulnerability found in package - libk5crypto3 (CVE-2016-3119 - https://security-tracker.debian.org/tracker/CVE-2016-3119)
Low Vulnerability found in package - libk5crypto3 (CVE-2017-11462 - https://security-tracker.debian.org/tracker/CVE-2017-11462)
Low Vulnerability found in package - libkrb5-3 (CVE-2016-3119 - https://security-tracker.debian.org/tracker/CVE-2016-3119)
Low Vulnerability found in package - libkrb5-3 (CVE-2017-11462 - https://security-tracker.debian.org/tracker/CVE-2017-11462)
Low Vulnerability found in package - libkrb5support0 (CVE-2016-3119 - https://security-tracker.debian.org/tracker/CVE-2016-3119)
Low Vulnerability found in package - libkrb5support0 (CVE-2017-11462 - https://security-tracker.debian.org/tracker/CVE-2017-11462)
Low Vulnerability found in package - libstdc++6 (CVE-2017-11671 - https://security-tracker.debian.org/tracker/CVE-2017-11671)
Low Vulnerability found in package - libxml2 (CVE-2017-5969 - https://security-tracker.debian.org/tracker/CVE-2017-5969)
Low Vulnerability found in package - multiarch-support (CVE-2015-5180 - https://security-tracker.debian.org/tracker/CVE-2015-5180)
Low Vulnerability found in package - openssh-client (CVE-2015-6563 - https://security-tracker.debian.org/tracker/CVE-2015-6563)
Low Vulnerability found in package - openssh-client (CVE-2016-10009 - https://security-tracker.debian.org/tracker/CVE-2016-10009)
Low Vulnerability found in package - openssh-client (CVE-2016-10011 - https://security-tracker.debian.org/tracker/CVE-2016-10011)
Low Vulnerability found in package - openssh-client (CVE-2016-10012 - https://security-tracker.debian.org/tracker/CVE-2016-10012)
Low Vulnerability found in package - wget (CVE-2016-7098 - https://security-tracker.debian.org/tracker/CVE-2016-7098)
Medium Vulnerability found in package - bash (CVE-2016-0634 - https://security-tracker.debian.org/tracker/CVE-2016-0634)
Medium Vulnerability found in package - curl (CVE-2016-7141 - https://security-tracker.debian.org/tracker/CVE-2016-7141)
Medium Vulnerability found in package - gcc-4.9-base (CVE-2015-5276 - https://security-tracker.debian.org/tracker/CVE-2015-5276)
Medium Vulnerability found in package - krb5-locales (CVE-2015-2694 - https://security-tracker.debian.org/tracker/CVE-2015-2694)
Medium Vulnerability found in package - krb5-locales (CVE-2016-3120 - https://security-tracker.debian.org/tracker/CVE-2016-3120)
Medium Vulnerability found in package - krb5-locales (CVE-2017-11368 - https://security-tracker.debian.org/tracker/CVE-2017-11368)
Medium Vulnerability found in package - libblkid1 (CVE-2016-5011 - https://security-tracker.debian.org/tracker/CVE-2016-5011)
Medium Vulnerability found in package - libc-bin (CVE-2016-10228 - https://security-tracker.debian.org/tracker/CVE-2016-10228)
Medium Vulnerability found in package - libc-bin (CVE-2016-1234 - https://security-tracker.debian.org/tracker/CVE-2016-1234)
Medium Vulnerability found in package - libc-bin (CVE-2016-3075 - https://security-tracker.debian.org/tracker/CVE-2016-3075)
Medium Vulnerability found in package - libc-bin (CVE-2016-3706 - https://security-tracker.debian.org/tracker/CVE-2016-3706)
Medium Vulnerability found in package - libc-bin (CVE-2016-6323 - https://security-tracker.debian.org/tracker/CVE-2016-6323)
Medium Vulnerability found in package - libc-bin (CVE-2017-12132 - https://security-tracker.debian.org/tracker/CVE-2017-12132)
Medium Vulnerability found in package - libc-bin (CVE-2017-12133 - https://security-tracker.debian.org/tracker/CVE-2017-12133)
Medium Vulnerability found in package - libc6 (CVE-2016-10228 - https://security-tracker.debian.org/tracker/CVE-2016-10228)
Medium Vulnerability found in package - libc6 (CVE-2016-1234 - https://security-tracker.debian.org/tracker/CVE-2016-1234)
Medium Vulnerability found in package - libc6 (CVE-2016-3075 - https://security-tracker.debian.org/tracker/CVE-2016-3075)
Medium Vulnerability found in package - libc6 (CVE-2016-3706 - https://security-tracker.debian.org/tracker/CVE-2016-3706)
Medium Vulnerability found in package - libc6 (CVE-2016-6323 - https://security-tracker.debian.org/tracker/CVE-2016-6323)
Medium Vulnerability found in package - libc6 (CVE-2017-12132 - https://security-tracker.debian.org/tracker/CVE-2017-12132)
Medium Vulnerability found in package - libc6 (CVE-2017-12133 - https://security-tracker.debian.org/tracker/CVE-2017-12133)
Medium Vulnerability found in package - libcurl3 (CVE-2016-7141 - https://security-tracker.debian.org/tracker/CVE-2016-7141)
Medium Vulnerability found in package - libcurl3-gnutls (CVE-2016-7141 - https://security-tracker.debian.org/tracker/CVE-2016-7141)
Medium Vulnerability found in package - libgcrypt20 (CVE-2017-9526 - https://security-tracker.debian.org/tracker/CVE-2017-9526)
Medium Vulnerability found in package - libgnutls-deb0-28 (CVE-2011-3389 - https://security-tracker.debian.org/tracker/CVE-2011-3389)
Medium Vulnerability found in package - libgssapi-krb5-2 (CVE-2015-2694 - https://security-tracker.debian.org/tracker/CVE-2015-2694)
Medium Vulnerability found in package - libgssapi-krb5-2 (CVE-2016-3120 - https://security-tracker.debian.org/tracker/CVE-2016-3120)
Medium Vulnerability found in package - libgssapi-krb5-2 (CVE-2017-11368 - https://security-tracker.debian.org/tracker/CVE-2017-11368)
Medium Vulnerability found in package - libk5crypto3 (CVE-2015-2694 - https://security-tracker.debian.org/tracker/CVE-2015-2694)
Medium Vulnerability found in package - libk5crypto3 (CVE-2016-3120 - https://security-tracker.debian.org/tracker/CVE-2016-3120)
Medium Vulnerability found in package - libk5crypto3 (CVE-2017-11368 - https://security-tracker.debian.org/tracker/CVE-2017-11368)
Medium Vulnerability found in package - libkrb5-3 (CVE-2015-2694 - https://security-tracker.debian.org/tracker/CVE-2015-2694)
Medium Vulnerability found in package - libkrb5-3 (CVE-2016-3120 - https://security-tracker.debian.org/tracker/CVE-2016-3120)
Medium Vulnerability found in package - libkrb5-3 (CVE-2017-11368 - https://security-tracker.debian.org/tracker/CVE-2017-11368)
Medium Vulnerability found in package - libkrb5support0 (CVE-2015-2694 - https://security-tracker.debian.org/tracker/CVE-2015-2694)
Medium Vulnerability found in package - libkrb5support0 (CVE-2016-3120 - https://security-tracker.debian.org/tracker/CVE-2016-3120)
Medium Vulnerability found in package - libkrb5support0 (CVE-2017-11368 - https://security-tracker.debian.org/tracker/CVE-2017-11368)
Medium Vulnerability found in package - libmount1 (CVE-2016-5011 - https://security-tracker.debian.org/tracker/CVE-2016-5011)
Medium Vulnerability found in package - libncurses5 (CVE-2017-11112 - https://security-tracker.debian.org/tracker/CVE-2017-11112)
Medium Vulnerability found in package - libncurses5 (CVE-2017-11113 - https://security-tracker.debian.org/tracker/CVE-2017-11113)
Medium Vulnerability found in package - libncurses5 (CVE-2017-13728 - https://security-tracker.debian.org/tracker/CVE-2017-13728)
Medium Vulnerability found in package - libncurses5 (CVE-2017-13729 - https://security-tracker.debian.org/tracker/CVE-2017-13729)
Medium Vulnerability found in package - libncurses5 (CVE-2017-13730 - https://security-tracker.debian.org/tracker/CVE-2017-13730)
Medium Vulnerability found in package - libncurses5 (CVE-2017-13731 - https://security-tracker.debian.org/tracker/CVE-2017-13731)
Medium Vulnerability found in package - libncurses5 (CVE-2017-13732 - https://security-tracker.debian.org/tracker/CVE-2017-13732)
Medium Vulnerability found in package - libncurses5 (CVE-2017-13733 - https://security-tracker.debian.org/tracker/CVE-2017-13733)
Medium Vulnerability found in package - libncurses5 (CVE-2017-13734 - https://security-tracker.debian.org/tracker/CVE-2017-13734)
Medium Vulnerability found in package - libncursesw5 (CVE-2017-11112 - https://security-tracker.debian.org/tracker/CVE-2017-11112)
Medium Vulnerability found in package - libncursesw5 (CVE-2017-11113 - https://security-tracker.debian.org/tracker/CVE-2017-11113)
Medium Vulnerability found in package - libncursesw5 (CVE-2017-13728 - https://security-tracker.debian.org/tracker/CVE-2017-13728)
Medium Vulnerability found in package - libncursesw5 (CVE-2017-13729 - https://security-tracker.debian.org/tracker/CVE-2017-13729)
Medium Vulnerability found in package - libncursesw5 (CVE-2017-13730 - https://security-tracker.debian.org/tracker/CVE-2017-13730)
Medium Vulnerability found in package - libncursesw5 (CVE-2017-13731 - https://security-tracker.debian.org/tracker/CVE-2017-13731)
Medium Vulnerability found in package - libncursesw5 (CVE-2017-13732 - https://security-tracker.debian.org/tracker/CVE-2017-13732)
Medium Vulnerability found in package - libncursesw5 (CVE-2017-13733 - https://security-tracker.debian.org/tracker/CVE-2017-13733)
Medium Vulnerability found in package - libncursesw5 (CVE-2017-13734 - https://security-tracker.debian.org/tracker/CVE-2017-13734)
Medium Vulnerability found in package - libpcre3 (CVE-2015-3217 - https://security-tracker.debian.org/tracker/CVE-2015-3217)
Medium Vulnerability found in package - libpcre3 (CVE-2017-7186 - https://security-tracker.debian.org/tracker/CVE-2017-7186)
Medium Vulnerability found in package - libpcre3 (CVE-2017-7244 - https://security-tracker.debian.org/tracker/CVE-2017-7244)
Medium Vulnerability found in package - libsmartcols1 (CVE-2016-5011 - https://security-tracker.debian.org/tracker/CVE-2016-5011)
Medium Vulnerability found in package - libssl1.0.0 (CVE-2017-3735 - https://security-tracker.debian.org/tracker/CVE-2017-3735)
Medium Vulnerability found in package - libstdc++6 (CVE-2015-5276 - https://security-tracker.debian.org/tracker/CVE-2015-5276)
Medium Vulnerability found in package - libsystemd0 (CVE-2016-7796 - https://security-tracker.debian.org/tracker/CVE-2016-7796)
Medium Vulnerability found in package - libtasn1-6 (CVE-2017-10790 - https://security-tracker.debian.org/tracker/CVE-2017-10790)
Medium Vulnerability found in package - libtinfo5 (CVE-2017-11112 - https://security-tracker.debian.org/tracker/CVE-2017-11112)
Medium Vulnerability found in package - libtinfo5 (CVE-2017-11113 - https://security-tracker.debian.org/tracker/CVE-2017-11113)
Medium Vulnerability found in package - libtinfo5 (CVE-2017-13728 - https://security-tracker.debian.org/tracker/CVE-2017-13728)
Medium Vulnerability found in package - libtinfo5 (CVE-2017-13729 - https://security-tracker.debian.org/tracker/CVE-2017-13729)
Medium Vulnerability found in package - libtinfo5 (CVE-2017-13730 - https://security-tracker.debian.org/tracker/CVE-2017-13730)
Medium Vulnerability found in package - libtinfo5 (CVE-2017-13731 - https://security-tracker.debian.org/tracker/CVE-2017-13731)
Medium Vulnerability found in package - libtinfo5 (CVE-2017-13732 - https://security-tracker.debian.org/tracker/CVE-2017-13732)
Medium Vulnerability found in package - libtinfo5 (CVE-2017-13733 - https://security-tracker.debian.org/tracker/CVE-2017-13733)
Medium Vulnerability found in package - libtinfo5 (CVE-2017-13734 - https://security-tracker.debian.org/tracker/CVE-2017-13734)
Medium Vulnerability found in package - libudev1 (CVE-2016-7796 - https://security-tracker.debian.org/tracker/CVE-2016-7796)
Medium Vulnerability found in package - libuuid1 (CVE-2016-5011 - https://security-tracker.debian.org/tracker/CVE-2016-5011)
Medium Vulnerability found in package - libxml2 (CVE-2016-9318 - https://security-tracker.debian.org/tracker/CVE-2016-9318)
Medium Vulnerability found in package - libxml2 (CVE-2017-8872 - https://security-tracker.debian.org/tracker/CVE-2017-8872)
Medium Vulnerability found in package - mount (CVE-2016-5011 - https://security-tracker.debian.org/tracker/CVE-2016-5011)
Medium Vulnerability found in package - multiarch-support (CVE-2016-10228 - https://security-tracker.debian.org/tracker/CVE-2016-10228)
Medium Vulnerability found in package - multiarch-support (CVE-2016-1234 - https://security-tracker.debian.org/tracker/CVE-2016-1234)
Medium Vulnerability found in package - multiarch-support (CVE-2016-3075 - https://security-tracker.debian.org/tracker/CVE-2016-3075)
Medium Vulnerability found in package - multiarch-support (CVE-2016-3706 - https://security-tracker.debian.org/tracker/CVE-2016-3706)
Medium Vulnerability found in package - multiarch-support (CVE-2016-6323 - https://security-tracker.debian.org/tracker/CVE-2016-6323)
Medium Vulnerability found in package - multiarch-support (CVE-2017-12132 - https://security-tracker.debian.org/tracker/CVE-2017-12132)
Medium Vulnerability found in package - multiarch-support (CVE-2017-12133 - https://security-tracker.debian.org/tracker/CVE-2017-12133)
Medium Vulnerability found in package - ncurses-base (CVE-2017-11112 - https://security-tracker.debian.org/tracker/CVE-2017-11112)
Medium Vulnerability found in package - ncurses-base (CVE-2017-11113 - https://security-tracker.debian.org/tracker/CVE-2017-11113)
Medium Vulnerability found in package - ncurses-base (CVE-2017-13728 - https://security-tracker.debian.org/tracker/CVE-2017-13728)
Medium Vulnerability found in package - ncurses-base (CVE-2017-13729 - https://security-tracker.debian.org/tracker/CVE-2017-13729)
Medium Vulnerability found in package - ncurses-base (CVE-2017-13730 - https://security-tracker.debian.org/tracker/CVE-2017-13730)
Medium Vulnerability found in package - ncurses-base (CVE-2017-13731 - https://security-tracker.debian.org/tracker/CVE-2017-13731)
Medium Vulnerability found in package - ncurses-base (CVE-2017-13732 - https://security-tracker.debian.org/tracker/CVE-2017-13732)
Medium Vulnerability found in package - ncurses-base (CVE-2017-13733 - https://security-tracker.debian.org/tracker/CVE-2017-13733)
Medium Vulnerability found in package - ncurses-base (CVE-2017-13734 - https://security-tracker.debian.org/tracker/CVE-2017-13734)
Medium Vulnerability found in package - ncurses-bin (CVE-2017-11112 - https://security-tracker.debian.org/tracker/CVE-2017-11112)
Medium Vulnerability found in package - ncurses-bin (CVE-2017-11113 - https://security-tracker.debian.org/tracker/CVE-2017-11113)
Medium Vulnerability found in package - ncurses-bin (CVE-2017-13728 - https://security-tracker.debian.org/tracker/CVE-2017-13728)
Medium Vulnerability found in package - ncurses-bin (CVE-2017-13729 - https://security-tracker.debian.org/tracker/CVE-2017-13729)
Medium Vulnerability found in package - ncurses-bin (CVE-2017-13730 - https://security-tracker.debian.org/tracker/CVE-2017-13730)
Medium Vulnerability found in package - ncurses-bin (CVE-2017-13731 - https://security-tracker.debian.org/tracker/CVE-2017-13731)
Medium Vulnerability found in package - ncurses-bin (CVE-2017-13732 - https://security-tracker.debian.org/tracker/CVE-2017-13732)
Medium Vulnerability found in package - ncurses-bin (CVE-2017-13733 - https://security-tracker.debian.org/tracker/CVE-2017-13733)
Medium Vulnerability found in package - ncurses-bin (CVE-2017-13734 - https://security-tracker.debian.org/tracker/CVE-2017-13734)
Medium Vulnerability found in package - openssh-client (CVE-2015-5352 - https://security-tracker.debian.org/tracker/CVE-2015-5352)
Medium Vulnerability found in package - openssh-client (CVE-2015-6564 - https://security-tracker.debian.org/tracker/CVE-2015-6564)
Medium Vulnerability found in package - openssh-client (CVE-2016-3115 - https://security-tracker.debian.org/tracker/CVE-2016-3115)
Medium Vulnerability found in package - openssl (CVE-2017-3735 - https://security-tracker.debian.org/tracker/CVE-2017-3735)
Medium Vulnerability found in package - systemd (CVE-2016-7796 - https://security-tracker.debian.org/tracker/CVE-2016-7796)
Medium Vulnerability found in package - systemd-sysv (CVE-2016-7796 - https://security-tracker.debian.org/tracker/CVE-2016-7796)
Medium Vulnerability found in package - tar (CVE-2016-6321 - https://security-tracker.debian.org/tracker/CVE-2016-6321)
Medium Vulnerability found in package - udev (CVE-2016-7796 - https://security-tracker.debian.org/tracker/CVE-2016-7796)
Medium Vulnerability found in package - util-linux (CVE-2016-5011 - https://security-tracker.debian.org/tracker/CVE-2016-5011)
Medium Vulnerability found in package - zlib1g (CVE-2016-9840 - https://security-tracker.debian.org/tracker/CVE-2016-9840)
Medium Vulnerability found in package - zlib1g (CVE-2016-9842 - https://security-tracker.debian.org/tracker/CVE-2016-9842)
High Vulnerability found in package - bash (CVE-2016-7543 - https://security-tracker.debian.org/tracker/CVE-2016-7543)
High Vulnerability found in package - curl (CVE-2016-7167 - https://security-tracker.debian.org/tracker/CVE-2016-7167)
High Vulnerability found in package - libblkid1 (CVE-2016-2779 - https://security-tracker.debian.org/tracker/CVE-2016-2779)
High Vulnerability found in package - libbsd0 (CVE-2016-2090 - https://security-tracker.debian.org/tracker/CVE-2016-2090)
High Vulnerability found in package - libc-bin (CVE-2014-9761 - https://security-tracker.debian.org/tracker/CVE-2014-9761)
High Vulnerability found in package - libc-bin (CVE-2016-4429 - https://security-tracker.debian.org/tracker/CVE-2016-4429)
High Vulnerability found in package - libc-bin (CVE-2017-1000366 - https://security-tracker.debian.org/tracker/CVE-2017-1000366)
High Vulnerability found in package - libc-bin (CVE-2017-8804 - https://security-tracker.debian.org/tracker/CVE-2017-8804)
High Vulnerability found in package - libc6 (CVE-2014-9761 - https://security-tracker.debian.org/tracker/CVE-2014-9761)
High Vulnerability found in package - libc6 (CVE-2016-4429 - https://security-tracker.debian.org/tracker/CVE-2016-4429)
High Vulnerability found in package - libc6 (CVE-2017-1000366 - https://security-tracker.debian.org/tracker/CVE-2017-1000366)
High Vulnerability found in package - libc6 (CVE-2017-8804 - https://security-tracker.debian.org/tracker/CVE-2017-8804)
High Vulnerability found in package - libcurl3 (CVE-2016-7167 - https://security-tracker.debian.org/tracker/CVE-2016-7167)
High Vulnerability found in package - libcurl3-gnutls (CVE-2016-7167 - https://security-tracker.debian.org/tracker/CVE-2016-7167)
High Vulnerability found in package - libidn11 (CVE-2017-14062 - https://security-tracker.debian.org/tracker/CVE-2017-14062)
High Vulnerability found in package - libmount1 (CVE-2016-2779 - https://security-tracker.debian.org/tracker/CVE-2016-2779)
High Vulnerability found in package - libncurses5 (CVE-2017-10684 - https://security-tracker.debian.org/tracker/CVE-2017-10684)
High Vulnerability found in package - libncurses5 (CVE-2017-10685 - https://security-tracker.debian.org/tracker/CVE-2017-10685)
High Vulnerability found in package - libncursesw5 (CVE-2017-10684 - https://security-tracker.debian.org/tracker/CVE-2017-10684)
High Vulnerability found in package - libncursesw5 (CVE-2017-10685 - https://security-tracker.debian.org/tracker/CVE-2017-10685)
High Vulnerability found in package - libsmartcols1 (CVE-2016-2779 - https://security-tracker.debian.org/tracker/CVE-2016-2779)
High Vulnerability found in package - libsqlite3-0 (CVE-2017-10989 - https://security-tracker.debian.org/tracker/CVE-2017-10989)
High Vulnerability found in package - libtinfo5 (CVE-2017-10684 - https://security-tracker.debian.org/tracker/CVE-2017-10684)
High Vulnerability found in package - libtinfo5 (CVE-2017-10685 - https://security-tracker.debian.org/tracker/CVE-2017-10685)
High Vulnerability found in package - libuuid1 (CVE-2016-2779 - https://security-tracker.debian.org/tracker/CVE-2016-2779)
High Vulnerability found in package - libx11-6 (CVE-2016-7942 - https://security-tracker.debian.org/tracker/CVE-2016-7942)
High Vulnerability found in package - libx11-6 (CVE-2016-7943 - https://security-tracker.debian.org/tracker/CVE-2016-7943)
High Vulnerability found in package - libx11-data (CVE-2016-7942 - https://security-tracker.debian.org/tracker/CVE-2016-7942)
High Vulnerability found in package - libx11-data (CVE-2016-7943 - https://security-tracker.debian.org/tracker/CVE-2016-7943)
High Vulnerability found in package - libxml2 (CVE-2016-4448 - https://security-tracker.debian.org/tracker/CVE-2016-4448)
High Vulnerability found in package - libxrender1 (CVE-2016-7949 - https://security-tracker.debian.org/tracker/CVE-2016-7949)
High Vulnerability found in package - libxrender1 (CVE-2016-7950 - https://security-tracker.debian.org/tracker/CVE-2016-7950)
High Vulnerability found in package - login (CVE-2017-12424 - https://security-tracker.debian.org/tracker/CVE-2017-12424)
High Vulnerability found in package - mercurial (CVE-2017-9462 - https://security-tracker.debian.org/tracker/CVE-2017-9462)
High Vulnerability found in package - mercurial-common (CVE-2017-9462 - https://security-tracker.debian.org/tracker/CVE-2017-9462)
High Vulnerability found in package - mount (CVE-2016-2779 - https://security-tracker.debian.org/tracker/CVE-2016-2779)
High Vulnerability found in package - multiarch-support (CVE-2014-9761 - https://security-tracker.debian.org/tracker/CVE-2014-9761)
High Vulnerability found in package - multiarch-support (CVE-2016-4429 - https://security-tracker.debian.org/tracker/CVE-2016-4429)
High Vulnerability found in package - multiarch-support (CVE-2017-1000366 - https://security-tracker.debian.org/tracker/CVE-2017-1000366)
High Vulnerability found in package - multiarch-support (CVE-2017-8804 - https://security-tracker.debian.org/tracker/CVE-2017-8804)
High Vulnerability found in package - ncurses-base (CVE-2017-10684 - https://security-tracker.debian.org/tracker/CVE-2017-10684)
High Vulnerability found in package - ncurses-base (CVE-2017-10685 - https://security-tracker.debian.org/tracker/CVE-2017-10685)
High Vulnerability found in package - ncurses-bin (CVE-2017-10684 - https://security-tracker.debian.org/tracker/CVE-2017-10684)
High Vulnerability found in package - ncurses-bin (CVE-2017-10685 - https://security-tracker.debian.org/tracker/CVE-2017-10685)
High Vulnerability found in package - openssh-client (CVE-2015-5600 - https://security-tracker.debian.org/tracker/CVE-2015-5600)
High Vulnerability found in package - openssh-client (CVE-2016-1908 - https://security-tracker.debian.org/tracker/CVE-2016-1908)
High Vulnerability found in package - openssh-client (CVE-2016-6515 - https://security-tracker.debian.org/tracker/CVE-2016-6515)
High Vulnerability found in package - openssh-client (CVE-2016-8858 - https://security-tracker.debian.org/tracker/CVE-2016-8858)
High Vulnerability found in package - passwd (CVE-2017-12424 - https://security-tracker.debian.org/tracker/CVE-2017-12424)
High Vulnerability found in package - util-linux (CVE-2016-2779 - https://security-tracker.debian.org/tracker/CVE-2016-2779)
High Vulnerability found in package - zlib1g (CVE-2016-9841 - https://security-tracker.debian.org/tracker/CVE-2016-9841)
High Vulnerability found in package - zlib1g (CVE-2016-9843 - https://security-tracker.debian.org/tracker/CVE-2016-9843)
Negligible Vulnerability found in package - apt (CVE-2011-3374 - https://security-tracker.debian.org/tracker/CVE-2011-3374)
Negligible Vulnerability found in package - apt (CVE-2016-1252 - https://security-tracker.debian.org/tracker/CVE-2016-1252)
Negligible Vulnerability found in package - curl (CVE-2016-3739 - https://security-tracker.debian.org/tracker/CVE-2016-3739)
Negligible Vulnerability found in package - curl (CVE-2017-1000101 - https://security-tracker.debian.org/tracker/CVE-2017-1000101)
Negligible Vulnerability found in package - dpkg (CVE-2017-8283 - https://security-tracker.debian.org/tracker/CVE-2017-8283)
Negligible Vulnerability found in package - git (CVE-2017-15298 - https://security-tracker.debian.org/tracker/CVE-2017-15298)
Negligible Vulnerability found in package - git-man (CVE-2017-15298 - https://security-tracker.debian.org/tracker/CVE-2017-15298)
Negligible Vulnerability found in package - gnupg (CVE-2017-7526 - https://security-tracker.debian.org/tracker/CVE-2017-7526)
Negligible Vulnerability found in package - gpgv (CVE-2017-7526 - https://security-tracker.debian.org/tracker/CVE-2017-7526)
Negligible Vulnerability found in package - krb5-locales (CVE-2004-0971 - https://security-tracker.debian.org/tracker/CVE-2004-0971)
Negligible Vulnerability found in package - less (CVE-2014-9488 - https://security-tracker.debian.org/tracker/CVE-2014-9488)
Negligible Vulnerability found in package - libapt-pkg4.12 (CVE-2011-3374 - https://security-tracker.debian.org/tracker/CVE-2011-3374)
Negligible Vulnerability found in package - libapt-pkg4.12 (CVE-2016-1252 - https://security-tracker.debian.org/tracker/CVE-2016-1252)
Negligible Vulnerability found in package - libaudit-common (CVE-2015-5186 - https://security-tracker.debian.org/tracker/CVE-2015-5186)
Negligible Vulnerability found in package - libaudit1 (CVE-2015-5186 - https://security-tracker.debian.org/tracker/CVE-2015-5186)
Negligible Vulnerability found in package - libblkid1 (CVE-2015-5218 - https://security-tracker.debian.org/tracker/CVE-2015-5218)
Negligible Vulnerability found in package - libblkid1 (CVE-2015-5224 - https://security-tracker.debian.org/tracker/CVE-2015-5224)
Negligible Vulnerability found in package - libblkid1 (CVE-2017-2616 - https://security-tracker.debian.org/tracker/CVE-2017-2616)
Negligible Vulnerability found in package - libc-bin (CVE-2010-4051 - https://security-tracker.debian.org/tracker/CVE-2010-4051)
Negligible Vulnerability found in package - libc-bin (CVE-2010-4052 - https://security-tracker.debian.org/tracker/CVE-2010-4052)
Negligible Vulnerability found in package - libc-bin (CVE-2010-4756 - https://security-tracker.debian.org/tracker/CVE-2010-4756)
Negligible Vulnerability found in package - libc-bin (CVE-2015-8985 - https://security-tracker.debian.org/tracker/CVE-2015-8985)
Negligible Vulnerability found in package - libc6 (CVE-2010-4051 - https://security-tracker.debian.org/tracker/CVE-2010-4051)
Negligible Vulnerability found in package - libc6 (CVE-2010-4052 - https://security-tracker.debian.org/tracker/CVE-2010-4052)
Negligible Vulnerability found in package - libc6 (CVE-2010-4756 - https://security-tracker.debian.org/tracker/CVE-2010-4756)
Negligible Vulnerability found in package - libc6 (CVE-2015-8985 - https://security-tracker.debian.org/tracker/CVE-2015-8985)
Negligible Vulnerability found in package - libcryptsetup4 (CVE-2016-4484 - https://security-tracker.debian.org/tracker/CVE-2016-4484)
Negligible Vulnerability found in package - libcurl3 (CVE-2016-3739 - https://security-tracker.debian.org/tracker/CVE-2016-3739)
Negligible Vulnerability found in package - libcurl3 (CVE-2017-1000101 - https://security-tracker.debian.org/tracker/CVE-2017-1000101)
Negligible Vulnerability found in package - libcurl3-gnutls (CVE-2016-3739 - https://security-tracker.debian.org/tracker/CVE-2016-3739)
Negligible Vulnerability found in package - libcurl3-gnutls (CVE-2017-1000101 - https://security-tracker.debian.org/tracker/CVE-2017-1000101)
Negligible Vulnerability found in package - libexpat1 (CVE-2013-0340 - https://security-tracker.debian.org/tracker/CVE-2013-0340)
Negligible Vulnerability found in package - libgcrypt20 (CVE-2017-7526 - https://security-tracker.debian.org/tracker/CVE-2017-7526)
Negligible Vulnerability found in package - libglib2.0-0 (CVE-2012-0039 - https://security-tracker.debian.org/tracker/CVE-2012-0039)
Negligible Vulnerability found in package - libglib2.0-data (CVE-2012-0039 - https://security-tracker.debian.org/tracker/CVE-2012-0039)
Negligible Vulnerability found in package - libgssapi-krb5-2 (CVE-2004-0971 - https://security-tracker.debian.org/tracker/CVE-2004-0971)
Negligible Vulnerability found in package - libk5crypto3 (CVE-2004-0971 - https://security-tracker.debian.org/tracker/CVE-2004-0971)
Negligible Vulnerability found in package - libkrb5-3 (CVE-2004-0971 - https://security-tracker.debian.org/tracker/CVE-2004-0971)
Negligible Vulnerability found in package - libkrb5support0 (CVE-2004-0971 - https://security-tracker.debian.org/tracker/CVE-2004-0971)
Negligible Vulnerability found in package - libldap-2.4-2 (CVE-2015-3276 - https://security-tracker.debian.org/tracker/CVE-2015-3276)
Negligible Vulnerability found in package - libldap-2.4-2 (CVE-2017-14159 - https://security-tracker.debian.org/tracker/CVE-2017-14159)
Negligible Vulnerability found in package - libmount1 (CVE-2015-5218 - https://security-tracker.debian.org/tracker/CVE-2015-5218)
Negligible Vulnerability found in package - libmount1 (CVE-2015-5224 - https://security-tracker.debian.org/tracker/CVE-2015-5224)
Negligible Vulnerability found in package - libmount1 (CVE-2017-2616 - https://security-tracker.debian.org/tracker/CVE-2017-2616)
Negligible Vulnerability found in package - libpcre3 (CVE-2017-11164 - https://security-tracker.debian.org/tracker/CVE-2017-11164)
Negligible Vulnerability found in package - libpcre3 (CVE-2017-7245 - https://security-tracker.debian.org/tracker/CVE-2017-7245)
Negligible Vulnerability found in package - libpcre3 (CVE-2017-7246 - https://security-tracker.debian.org/tracker/CVE-2017-7246)
Negligible Vulnerability found in package - libpython-stdlib (CVE-2008-4108 - https://security-tracker.debian.org/tracker/CVE-2008-4108)
Negligible Vulnerability found in package - libpython2.7-minimal (CVE-2013-7040 - https://security-tracker.debian.org/tracker/CVE-2013-7040)
Negligible Vulnerability found in package - libpython2.7-minimal (CVE-2016-1000110 - https://security-tracker.debian.org/tracker/CVE-2016-1000110)
Negligible Vulnerability found in package - libpython2.7-stdlib (CVE-2013-7040 - https://security-tracker.debian.org/tracker/CVE-2013-7040)
Negligible Vulnerability found in package - libpython2.7-stdlib (CVE-2016-1000110 - https://security-tracker.debian.org/tracker/CVE-2016-1000110)
Negligible Vulnerability found in package - libsmartcols1 (CVE-2015-5218 - https://security-tracker.debian.org/tracker/CVE-2015-5218)
Negligible Vulnerability found in package - libsmartcols1 (CVE-2015-5224 - https://security-tracker.debian.org/tracker/CVE-2015-5224)
Negligible Vulnerability found in package - libsmartcols1 (CVE-2017-2616 - https://security-tracker.debian.org/tracker/CVE-2017-2616)
Negligible Vulnerability found in package - libsqlite3-0 (CVE-2017-13685 - https://security-tracker.debian.org/tracker/CVE-2017-13685)
Negligible Vulnerability found in package - libssl1.0.0 (CVE-2007-6755 - https://security-tracker.debian.org/tracker/CVE-2007-6755)
Negligible Vulnerability found in package - libssl1.0.0 (CVE-2010-0928 - https://security-tracker.debian.org/tracker/CVE-2010-0928)
Negligible Vulnerability found in package - libsystemd0 (CVE-2013-4392 - https://security-tracker.debian.org/tracker/CVE-2013-4392)
Negligible Vulnerability found in package - libudev1 (CVE-2013-4392 - https://security-tracker.debian.org/tracker/CVE-2013-4392)
Negligible Vulnerability found in package - libuuid1 (CVE-2015-5218 - https://security-tracker.debian.org/tracker/CVE-2015-5218)
Negligible Vulnerability found in package - libuuid1 (CVE-2015-5224 - https://security-tracker.debian.org/tracker/CVE-2015-5224)
Negligible Vulnerability found in package - libuuid1 (CVE-2017-2616 - https://security-tracker.debian.org/tracker/CVE-2017-2616)
Negligible Vulnerability found in package - login (CVE-2007-5686 - https://security-tracker.debian.org/tracker/CVE-2007-5686)
Negligible Vulnerability found in package - login (CVE-2013-4235 - https://security-tracker.debian.org/tracker/CVE-2013-4235)
Negligible Vulnerability found in package - mount (CVE-2015-5218 - https://security-tracker.debian.org/tracker/CVE-2015-5218)
Negligible Vulnerability found in package - mount (CVE-2015-5224 - https://security-tracker.debian.org/tracker/CVE-2015-5224)
Negligible Vulnerability found in package - mount (CVE-2017-2616 - https://security-tracker.debian.org/tracker/CVE-2017-2616)
Negligible Vulnerability found in package - multiarch-support (CVE-2010-4051 - https://security-tracker.debian.org/tracker/CVE-2010-4051)
Negligible Vulnerability found in package - multiarch-support (CVE-2010-4052 - https://security-tracker.debian.org/tracker/CVE-2010-4052)
Negligible Vulnerability found in package - multiarch-support (CVE-2010-4756 - https://security-tracker.debian.org/tracker/CVE-2010-4756)
Negligible Vulnerability found in package - multiarch-support (CVE-2015-8985 - https://security-tracker.debian.org/tracker/CVE-2015-8985)
Negligible Vulnerability found in package - openssh-client (CVE-2007-2243 - https://security-tracker.debian.org/tracker/CVE-2007-2243)
Negligible Vulnerability found in package - openssh-client (CVE-2007-2768 - https://security-tracker.debian.org/tracker/CVE-2007-2768)
Negligible Vulnerability found in package - openssh-client (CVE-2008-3234 - https://security-tracker.debian.org/tracker/CVE-2008-3234)
Negligible Vulnerability found in package - openssh-client (CVE-2016-10010 - https://security-tracker.debian.org/tracker/CVE-2016-10010)
Negligible Vulnerability found in package - openssl (CVE-2007-6755 - https://security-tracker.debian.org/tracker/CVE-2007-6755)
Negligible Vulnerability found in package - openssl (CVE-2010-0928 - https://security-tracker.debian.org/tracker/CVE-2010-0928)
Negligible Vulnerability found in package - passwd (CVE-2007-5686 - https://security-tracker.debian.org/tracker/CVE-2007-5686)
Negligible Vulnerability found in package - passwd (CVE-2013-4235 - https://security-tracker.debian.org/tracker/CVE-2013-4235)
Negligible Vulnerability found in package - patch (CVE-2010-4651 - https://security-tracker.debian.org/tracker/CVE-2010-4651)
Negligible Vulnerability found in package - perl (CVE-2011-4116 - https://security-tracker.debian.org/tracker/CVE-2011-4116)
Negligible Vulnerability found in package - perl (CVE-2012-3878 - https://security-tracker.debian.org/tracker/CVE-2012-3878)
Negligible Vulnerability found in package - perl-base (CVE-2011-4116 - https://security-tracker.debian.org/tracker/CVE-2011-4116)
Negligible Vulnerability found in package - perl-base (CVE-2012-3878 - https://security-tracker.debian.org/tracker/CVE-2012-3878)
Negligible Vulnerability found in package - perl-modules (CVE-2011-4116 - https://security-tracker.debian.org/tracker/CVE-2011-4116)
Negligible Vulnerability found in package - perl-modules (CVE-2012-3878 - https://security-tracker.debian.org/tracker/CVE-2012-3878)
Negligible Vulnerability found in package - python (CVE-2008-4108 - https://security-tracker.debian.org/tracker/CVE-2008-4108)
Negligible Vulnerability found in package - python-minimal (CVE-2008-4108 - https://security-tracker.debian.org/tracker/CVE-2008-4108)
Negligible Vulnerability found in package - python2.7 (CVE-2013-7040 - https://security-tracker.debian.org/tracker/CVE-2013-7040)
Negligible Vulnerability found in package - python2.7 (CVE-2016-1000110 - https://security-tracker.debian.org/tracker/CVE-2016-1000110)
Negligible Vulnerability found in package - python2.7-minimal (CVE-2013-7040 - https://security-tracker.debian.org/tracker/CVE-2013-7040)
Negligible Vulnerability found in package - python2.7-minimal (CVE-2016-1000110 - https://security-tracker.debian.org/tracker/CVE-2016-1000110)
Negligible Vulnerability found in package - systemd (CVE-2013-4392 - https://security-tracker.debian.org/tracker/CVE-2013-4392)
Negligible Vulnerability found in package - systemd-sysv (CVE-2013-4392 - https://security-tracker.debian.org/tracker/CVE-2013-4392)
Negligible Vulnerability found in package - tar (CVE-2005-2541 - https://security-tracker.debian.org/tracker/CVE-2005-2541)
Negligible Vulnerability found in package - udev (CVE-2013-4392 - https://security-tracker.debian.org/tracker/CVE-2013-4392)
Negligible Vulnerability found in package - util-linux (CVE-2015-5218 - https://security-tracker.debian.org/tracker/CVE-2015-5218)
Negligible Vulnerability found in package - util-linux (CVE-2015-5224 - https://security-tracker.debian.org/tracker/CVE-2015-5224)
Negligible Vulnerability found in package - util-linux (CVE-2017-2616 - https://security-tracker.debian.org/tracker/CVE-2017-2616)
Unknown Vulnerability found in package - curl (CVE-2016-8625 - https://security-tracker.debian.org/tracker/CVE-2016-8625)
Unknown Vulnerability found in package - curl (CVE-2016-9586 - https://security-tracker.debian.org/tracker/CVE-2016-9586)
Unknown Vulnerability found in package - curl (CVE-2017-1000100 - https://security-tracker.debian.org/tracker/CVE-2017-1000100)
Unknown Vulnerability found in package - curl (CVE-2017-1000254 - https://security-tracker.debian.org/tracker/CVE-2017-1000254)
Unknown Vulnerability found in package - libcurl3 (CVE-2016-8625 - https://security-tracker.debian.org/tracker/CVE-2016-8625)
Unknown Vulnerability found in package - libcurl3 (CVE-2016-9586 - https://security-tracker.debian.org/tracker/CVE-2016-9586)
Unknown Vulnerability found in package - libcurl3 (CVE-2017-1000100 - https://security-tracker.debian.org/tracker/CVE-2017-1000100)
Unknown Vulnerability found in package - libcurl3 (CVE-2017-1000254 - https://security-tracker.debian.org/tracker/CVE-2017-1000254)
Unknown Vulnerability found in package - libcurl3-gnutls (CVE-2016-8625 - https://security-tracker.debian.org/tracker/CVE-2016-8625)
Unknown Vulnerability found in package - libcurl3-gnutls (CVE-2016-9586 - https://security-tracker.debian.org/tracker/CVE-2016-9586)
Unknown Vulnerability found in package - libcurl3-gnutls (CVE-2017-1000100 - https://security-tracker.debian.org/tracker/CVE-2017-1000100)
Unknown Vulnerability found in package - libcurl3-gnutls (CVE-2017-1000254 - https://security-tracker.debian.org/tracker/CVE-2017-1000254)
Unknown Vulnerability found in package - libdb5.3 (CVE-2017-10140 - https://security-tracker.debian.org/tracker/CVE-2017-10140)
Unknown Vulnerability found in package - libice6 (CVE-2017-2626 - https://security-tracker.debian.org/tracker/CVE-2017-2626)
Unknown Vulnerability found in package - libicu52 (CVE-2017-14952 - https://security-tracker.debian.org/tracker/CVE-2017-14952)
Unknown Vulnerability found in package - libxdmcp6 (CVE-2017-2625 - https://security-tracker.debian.org/tracker/CVE-2017-2625)

Is there a plan to address these sort of security issues on an ongoing basis?

Cannot run matplotlib graphs inside continuumio/anaconda

I am trying to do some visualizations, but could not find good libraries that would enable me to do this. Can you advise if that is possible? Or, If I need to get a full ubuntu image and then run my visualizations from X11?

Thank you

Why continuumio/anaconda3 image takes about 1.8G?

docker.io/continuumio/anaconda3 latest 9ec02efa6720 3 days ago 1.878 GB

What's the purpose of tini in the Dockerfiles?

I'm going out on a limb here and hoping someone will be kind enough to satisfy my curiosity. Thanks in advance :)

OSError: dlopen: cannot load any more object with static TLS

I've tried to install gym and launched one of examples (CartPole-v0) inside of this docker but got error:

ImportError: Library "GL" not found.

But actually I have libGL.so. So after debugging I've found that pyglet (which is used inside of gym) found the lib but just couldn't load because of error:

OSError dlopen: cannot load any more object with static TLS

In other words pyglet can't load libGL.so and libGLU.so as TLS libraries because it doesn't have enough slots.

Here is the line where pyglet tries to load libGL.so and fails https://bitbucket.org/pyglet/pyglet/src/3d464716883b1a8b07a67f4932fdbe7c4af788f9/pyglet/lib.py?at=pyglet-1.3-maintenance&fileviewer=file-view-default#lib.py-137

It's well known issue with TLS glibc. Debian (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793641), which is used in this docker has glibc with 14 slots for TLS libs only. And it would be better to increase it to 32 or even more (64) (const DTV_SURPLUS inside of glibc-source/sysdeps/generic/ldsodefs.h). openai/gym#396

As well I've found few other issues related to *.so libs, which could be related:

#62
#49
Kaggle/docker-python#157 this container uses continuumio/anaconda3:5.0.1 under the hood and got the same error for pytorch.

I sure this is not complete list of related issues because it is core problem which could be faced in many way. So it is quite critical.

AttributeError: type object 'IOLoop' has no attribute 'initialized'

How to reproduce:

$ docker run -i -t -p 8888:8888 continuumio/miniconda3 /bin/bash -c "/opt/conda/bin/conda install jupyter -y --quiet && mkdir /opt/notebooks && /opt/conda/bin/jupyter notebook --notebook-dir=/opt/notebooks --ip='*' --port=8888 --no-browser"
Solving environment: ...working... done


==> WARNING: A newer version of conda exists. <==
  current version: 4.4.10
  latest version: 4.4.11

Please update conda by running

    $ conda update -n base conda



## Package Plan ##

  environment location: /opt/conda

  added / updated specs: 
    - jupyter


The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    send2trash-1.5.0           |           py36_0          16 KB
    icu-58.2                   |       h9c2bf20_1        22.5 MB
    traitlets-4.3.2            |   py36h674d592_0         131 KB
    pickleshare-0.7.4          |   py36h63277f8_0          11 KB
    libxml2-2.9.7              |       h26e45fe_0         2.0 MB
    jinja2-2.10                |   py36ha16c418_0         184 KB
    nbconvert-5.3.1            |   py36hb41ffb7_0         398 KB
    pyzmq-16.0.3               |   py36he2533c7_0         430 KB
    ipywidgets-7.1.2           |           py36_0          96 KB
    glib-2.53.6                |       h5d9569c_2         8.4 MB
    jupyter-1.0.0              |           py36_4           5 KB
    simplegeneric-0.8.1        |           py36_2           9 KB
    sip-4.18.1                 |   py36h51ed4ed_2         277 KB
    webencodings-0.5.1         |   py36h800622e_1          19 KB
    parso-0.1.1                |   py36h35f843b_0         118 KB
    freetype-2.8               |       hab7d2ae_1         804 KB
    ipython-6.2.1              |   py36h88c514a_1         1.0 MB
    zeromq-4.2.2               |       hbedb6e5_2         662 KB
    testpath-0.3.1             |   py36h8cadb63_0          89 KB
    jedi-0.11.1                |           py36_0         306 KB
    nbformat-4.4.0             |   py36h31c9010_0         137 KB
    qtconsole-4.3.1            |   py36h8f73b5b_0         150 KB
    terminado-0.8.1            |           py36_1          21 KB
    libpng-1.6.34              |       hb9fc6fc_0         334 KB
    gst-plugins-base-1.12.4    |       h33fb286_0         4.8 MB
    mistune-0.8.3              |           py36_0          52 KB
    jupyter_client-5.2.2       |           py36_0         124 KB
    python-dateutil-2.6.1      |   py36h88d3b88_1         237 KB
    pcre-8.41                  |       hc27e229_1         251 KB
    markupsafe-1.0             |   py36hd9260cd_1          24 KB
    prompt_toolkit-1.0.15      |   py36h17d85b1_0         339 KB
    ipython_genutils-0.2.0     |   py36hb52b0d5_0          39 KB
    gstreamer-1.12.4           |       hb53b477_0         3.6 MB
    jupyter_console-5.2.0      |   py36he59e554_1          35 KB
    ptyprocess-0.5.2           |   py36h69acd42_0          22 KB
    pandoc-1.19.2.1            |       hea2e7c5_1        17.8 MB
    gmp-6.1.2                  |       h6c8ec71_1         744 KB
    decorator-4.2.1            |           py36_0          15 KB
    expat-2.2.5                |       he0dffb1_0         186 KB
    tornado-5.0                |           py36_0         640 KB
    jsonschema-2.6.0           |   py36h006f8b5_0          62 KB
    qt-5.6.2                   |      hd25b39d_14        44.5 MB
    pygments-2.2.0             |   py36h0d3125c_0         1.3 MB
    jpeg-9b                    |       h024ee3a_2         248 KB
    pexpect-4.4.0              |           py36_0          73 KB
    html5lib-1.0.1             |   py36h2f9c1c0_0         181 KB
    libsodium-1.0.15           |       hf101ebd_0         313 KB
    notebook-5.4.0             |           py36_0         6.6 MB
    dbus-1.12.2                |       hc3f9b76_1         552 KB
    ipykernel-4.8.2            |           py36_0         145 KB
    widgetsnbextension-3.1.4   |           py36_0         1.7 MB
    wcwidth-0.1.7              |   py36hdf4376a_0          25 KB
    entrypoints-0.2.3          |   py36h1aec115_2           9 KB
    jupyter_core-4.4.0         |   py36h7c827e3_0          61 KB
    libxcb-1.12                |       hcd93eb1_4         446 KB
    bleach-2.1.3               |           py36_0          33 KB
    pyqt-5.6.0                 |   py36h0386399_5         5.5 MB
    pandocfilters-1.4.2        |   py36ha6701b7_1          12 KB
    fontconfig-2.12.4          |       h88586e7_1         282 KB
    ------------------------------------------------------------
                                           Total:       128.9 MB

The following NEW packages will be INSTALLED:

    bleach:             2.1.3-py36_0         
    dbus:               1.12.2-hc3f9b76_1    
    decorator:          4.2.1-py36_0         
    entrypoints:        0.2.3-py36h1aec115_2 
    expat:              2.2.5-he0dffb1_0     
    fontconfig:         2.12.4-h88586e7_1    
    freetype:           2.8-hab7d2ae_1       
    glib:               2.53.6-h5d9569c_2    
    gmp:                6.1.2-h6c8ec71_1     
    gst-plugins-base:   1.12.4-h33fb286_0    
    gstreamer:          1.12.4-hb53b477_0    
    html5lib:           1.0.1-py36h2f9c1c0_0 
    icu:                58.2-h9c2bf20_1      
    ipykernel:          4.8.2-py36_0         
    ipython:            6.2.1-py36h88c514a_1 
    ipython_genutils:   0.2.0-py36hb52b0d5_0 
    ipywidgets:         7.1.2-py36_0         
    jedi:               0.11.1-py36_0        
    jinja2:             2.10-py36ha16c418_0  
    jpeg:               9b-h024ee3a_2        
    jsonschema:         2.6.0-py36h006f8b5_0 
    jupyter:            1.0.0-py36_4         
    jupyter_client:     5.2.2-py36_0         
    jupyter_console:    5.2.0-py36he59e554_1 
    jupyter_core:       4.4.0-py36h7c827e3_0 
    libpng:             1.6.34-hb9fc6fc_0    
    libsodium:          1.0.15-hf101ebd_0    
    libxcb:             1.12-hcd93eb1_4      
    libxml2:            2.9.7-h26e45fe_0     
    markupsafe:         1.0-py36hd9260cd_1   
    mistune:            0.8.3-py36_0         
    nbconvert:          5.3.1-py36hb41ffb7_0 
    nbformat:           4.4.0-py36h31c9010_0 
    notebook:           5.4.0-py36_0         
    pandoc:             1.19.2.1-hea2e7c5_1  
    pandocfilters:      1.4.2-py36ha6701b7_1 
    parso:              0.1.1-py36h35f843b_0 
    pcre:               8.41-hc27e229_1      
    pexpect:            4.4.0-py36_0         
    pickleshare:        0.7.4-py36h63277f8_0 
    prompt_toolkit:     1.0.15-py36h17d85b1_0
    ptyprocess:         0.5.2-py36h69acd42_0 
    pygments:           2.2.0-py36h0d3125c_0 
    pyqt:               5.6.0-py36h0386399_5 
    python-dateutil:    2.6.1-py36h88d3b88_1 
    pyzmq:              16.0.3-py36he2533c7_0
    qt:                 5.6.2-hd25b39d_14    
    qtconsole:          4.3.1-py36h8f73b5b_0 
    send2trash:         1.5.0-py36_0         
    simplegeneric:      0.8.1-py36_2         
    sip:                4.18.1-py36h51ed4ed_2
    terminado:          0.8.1-py36_1         
    testpath:           0.3.1-py36h8cadb63_0 
    tornado:            5.0-py36_0           
    traitlets:          4.3.2-py36h674d592_0 
    wcwidth:            0.1.7-py36hdf4376a_0 
    webencodings:       0.5.1-py36h800622e_1 
    widgetsnbextension: 3.1.4-py36_0         
    zeromq:             4.2.2-hbedb6e5_2     

Preparing transaction: ...working... done
Verifying transaction: ...working... done
Executing transaction: ...working... done
Traceback (most recent call last):
  File "/opt/conda/bin/jupyter-notebook", line 7, in <module>
    from notebook.notebookapp import main
  File "/opt/conda/lib/python3.6/site-packages/notebook/notebookapp.py", line 45, in <module>
    ioloop.install()
  File "/opt/conda/lib/python3.6/site-packages/zmq/eventloop/ioloop.py", line 210, in install
    assert (not ioloop.IOLoop.initialized()) or \
AttributeError: type object 'IOLoop' has no attribute 'initialized'

Note that updating conda as requested does not help.

Create official DockerHub images

Could you create official images on DockerHub for miniconda and anaconda? I think this would help lead to better / wider adoption, and a better perception of the usability of these images.

miniconda3 4.3.21 has python2

docker run -it continuumio/miniconda3:4.3.21 python --version
Python 2.7.13 :: Continuum Analytics, Inc.

Version 4.3.14 is ok

docker run -it continuumio/miniconda3:4.3.14 python --version
Python 3.6.0 :: Continuum Analytics, Inc.

No license file?

The repository is missing a license file

Cannot run the spyder after download this images for anaconda

After downloaded and run docker image of anconda followed by bash command as " sudo docker pull continuumio/anaconda " and "sudo docker run -i -t continuumio/anaconda /bin/bash" respectively , I want to run bash command like " spyder" . But it indicates " Traceback (most recent call last):
File "/opt/conda/bin/spyder", line 2, in
from spyderlib import start_app
File "/opt/conda/lib/python2.7/site-packages/spyderlib/start_app.py", line 12, in
from spyderlib.baseconfig import get_conf_path, running_in_mac_app
File "/opt/conda/lib/python2.7/site-packages/spyderlib/baseconfig.py", line 188, in
from spyderlib.otherplugins import PLUGIN_PATH
File "/opt/conda/lib/python2.7/site-packages/spyderlib/otherplugins.py", line 17, in
from spyderlib.utils import programs
File "/opt/conda/lib/python2.7/site-packages/spyderlib/utils/programs.py", line 29, in
username = encoding.to_unicode_from_fs(os.environ.get('USER'))
File "/opt/conda/lib/python2.7/site-packages/spyderlib/utils/encoding.py", line 62, in to_unicode_from_fs
string = to_text_string(string.toUtf8(), 'utf-8')
AttributeError: 'NoneType' object has no attribute 'toUtf8' "

Any suggestion is appreciated , Thanks alot.

Cannot pull image, docker hangs indefinitely

$ docker pull continuumio/anaconda
Using default tag: latest
latest: Pulling from continuumio/anaconda
f36fcb403dfd: Extracting 101.9 MB/378.8 MB
a4d3bdd941e4: Layer already being pulled by another client. Waiting. 
a4d3bdd941e4: Layer already being pulled by another client. Waiting. 
405cce5cd17d: Already exists 
e565fbbc6033: Already exists 
d005ace4ebb9: Already exists 
a93aeb3d421b: Already exists 
Pulling repository docker.io/continuumio/anaconda

Then it hangs indefinitely, I'm using official mac toolbox from docker, and only continuumio/anaconda has this issue.

Related: moby/moby#12823

anaconda3 README has wrong version of Python

The README says the container has Anaconda (based on Python 3.5), but it actually has Anaconda 4.3.1 based on Python 3.6.

binutils too young

The binutils version on the image is too young: libraries built with it can be incompatible with older binutils due to the introduction of a new "relocation" kind.

See example at:
https://travis-ci.org/numba/llvmlite/jobs/147789631#L373

Update debian for images

I think we should update debian image to latest one FROM debian:stretch-slim. It has latest glibc which is required by latest Tensorflow.

packge lsb-release required

Package lsb-release is required so that conda install gcc works.
This is quite explanatory, just test with the command above and it will return an error.

Tagged images

At the moment https://hub.docker.com/r/continuumio/miniconda3/tags/ lists only a "3.9.0" tag (and obviously the "latest" tag).

I'm guessing that 3.9.0 tag is from c152ac0 , is there any reason why later images aren't tagged?

Cheers

container based on minconda3 image eats up file system memory in /var/lib/docker/aufs/

I've setup a Dockerfile with first line FROM continuumio/miniconda3:4.3.11. Then I've setup a Microsoft ODBC driver. On the python side I am using a combination of conda install and pip install for packages like luigi, pyodbc, sqlalchemy and pandas.

The purpose of this docker container is to define a cron job that once per day:

goes to the database ,
streams out around ~1.5 million rows (a few columns) with pyodbc using something like rowsCursor.fetchone(),
calculates some aggregates based on an in-memory pandas dataframe of around ~3500 rows (a few columns),
flushes this dataframe back to the database.

The cron job takes around ~4 hours (+/- 45 mins).

The docker image takes around 1.6 GB and the virtual machine has a disk of around ~30 GB capacity with around ~25 GB free at startup (after building/pulling the docker image).

After 4 5 days those 25 GB are eaten up by the stuff contained in /var/lib/docker/aufs/, no matter if I cleanup the file system with docker system prune -a (which says it cleans 0 GB). Instead I have to:

stop the container,
run docker system prune -a which shows to free up ~25 GB
pull the docker image again
run the docker container again

I am not sure the issue is with docker itself, I don't think so because I could not find that many issues with docker and AUFS (mainly this moby/moby#21925 which seems to be not related to docker). Anyway the output of docker -v is Docker version 17.03.1-ce, build c6d412e.

I thought the issue was with debian (the docker image underneath the minoconda3 image), but after cleaning up the apt-cache data I've freed up just around ~ 150 MB.

I am wondering if the combination of those python packages is writing anything to the file system, but for example the logs of the cron job are a few KB per day, not that much.

The cron job is mainly working in-memory and I am not writing anything to the file system in the python code.

Does this ring any bell? Is there anything I could do better to avoid those docker images eating up the space on the file system? Is there anything wrong I am doing in the miniconda/python setup?

Messed up (no) fonts in Qt apps - missing fontconfig?

I have a script that I am running (I didn't write it myself) that uses python and Qt, via matplotlib, to generate a GUI. When running it using the anaconda docker image I don't see any text in the menus, etc - just a load of black squares.

If I install fontconfig (apt-get install fontconfig) into the running container then everything then starts working perfectly.

Does fontconfig need to be added to the image build? Or is there some other config missing that would solve the problem another way?

Thanks!
Rob

Intel MKL FATAL ERROR: Cannot load libmkl_avx.so or libmkl_def.so

I use image continuumio/anaconda3:4.4.0 and was trying to run this example http://scikit-learn.org/stable/auto_examples/applications/plot_out_of_core_classification.html
And I got similar error ContinuumIO/anaconda-issues#698.

Intel MKL FATAL ERROR: Cannot load libmkl_avx.so or libmkl_def.so

Should I use this hack https://stackoverflow.com/questions/36659453/intel-mkl-fatal-error-cannot-load-libmkl-avx2-so-or-libmkl-def-so?

conda install nomkl numpy scipy scikit-learn numexpr
conda remove mkl mkl-service

Or there another proper way to solve this hack?

add libgl to Anaconda docker images

I'm not sure if this is related to the Docker image, conda, or PyQt5, but here is the repro:

docker run -it continuumio/miniconda bash

root@486a15ca93d5:/# conda install pyqt

root@486a15ca93d5:/# python -c "from PyQt5 import QtGui"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: libGL.so.1: cannot open shared object file: No such file or directory

root@486a15ca93d5:/# conda list
# packages in environment at /opt/conda:
#
cffi                      1.9.1                    py27_0
conda                     4.3.8                    py27_0
conda-env                 2.6.0                         0
cryptography              1.7.1                    py27_0
dbus                      1.10.10                       0
enum34                    1.1.6                    py27_0
expat                     2.1.0                         0
fontconfig                2.12.1                        2
freetype                  2.5.5                         2
glib                      2.50.2                        1
gst-plugins-base          1.8.0                         0
gstreamer                 1.8.0                         0
icu                       54.1                          0
idna                      2.2                      py27_0
ipaddress                 1.0.18                   py27_0
jpeg                      9b                            0
libffi                    3.2.1                         1
libgcc                    5.2.0                         0
libiconv                  1.14                          0
libpng                    1.6.27                        0
libxcb                    1.12                          1
libxml2                   2.9.4                         0
openssl                   1.0.2h                        1
pcre                      8.39                          1
pip                       8.1.2                    py27_0
pyasn1                    0.1.9                    py27_0
pycosat                   0.6.1                    py27_1
pycparser                 2.17                     py27_0
pycrypto                  2.6.1                    py27_4
pyopenssl                 16.2.0                   py27_0
pyqt                      5.6.0                    py27_2
python                    2.7.12                        1
pyyaml                    3.11                     py27_4
qt                        5.6.2                         3
readline                  6.2                           2
requests                  2.12.4                   py27_0
ruamel_yaml               0.11.14                  py27_0
setuptools                23.0.0                   py27_0
sip                       4.18                     py27_0
six                       1.10.0                   py27_0
sqlite                    3.13.0                        0
tk                        8.5.18                        0
wheel                     0.29.0                   py27_0
yaml                      0.1.6                         0
zlib                      1.2.8                         3

If I downgrade to PyQt4 however, things seem to work:

root@486a15ca93d5:/# conda install pyqt=4
root@486a15ca93d5:/# python -c "from PyQt4 import QtGui"

The image of continuumio/anaconda3 has been hacked?

I found strange minergate-cli process running in background and cosuming a lot of cpu, after I run docker of continuumio/anaconda3.

process infos are as follows:
26119 pts/0 Sl 29:24 ./opt/minergate-cli/minergate-cli -user [email protected] -fcn+xmr
26126 pts/0 Sl 0:00 ./opt/minergate-cli/minergate-cli -user [email protected] -fcn+xmr 0 2

find / -name minergate-cli

/var/lib/docker/devicemapper/mnt/40a3b8140d398645055cab495a8449711ab011e47bced5c0ae3a81f93e0867cf/rootfs/root/.local/share/minergate-cli
/var/lib/docker/devicemapper/mnt/40a3b8140d398645055cab495a8449711ab011e47bced5c0ae3a81f93e0867cf/rootfs/root/.ttmp/usr/bin/minergate-cli
/var/lib/docker/devicemapper/mnt/40a3b8140d398645055cab495a8449711ab011e47bced5c0ae3a81f93e0867cf/rootfs/root/.ttmp/opt/minergate-cli
/var/lib/docker/devicemapper/mnt/40a3b8140d398645055cab495a8449711ab011e47bced5c0ae3a81f93e0867cf/rootfs/root/.ttmp/opt/minergate-cli/minergate-cli

docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
40a3b8140d39 continuumio/anaconda3 "/usr/bin/tini -- /b 5 hours ago Up 2 hours 0.0.0.0:8888->8888/tcp notebook

what happened?

"yum" crashes

$ yum info binutils
Loaded plugins: fastestmirror
Segmentation fault (core dumped)

Anaconda images aren't available on Docker Hub

The GitHub READMEs say they can be pulled:

https://github.com/ContinuumIO/docker-images/blob/master/anaconda/README.md
https://github.com/ContinuumIO/docker-images/blob/master/anaconda3/README.md

But they don't seem to be available yet:

https://registry.hub.docker.com/search?q=continuumio

$ docker pull continuumio/anaconda
Pulling repository continuumio/anaconda
FATA[0002] Tag latest not found in repository continuumio/anaconda

(same with anaconda3)

[conda_builder_linux ] Cannot use start_cpp98.sh with script

This used to work:

$ start_cpp98.sh my_build_script.sh

it doesn't any longer, I'm pretty sure this is to blame:
https://github.com/ContinuumIO/docker-images/blame/master/conda_builder_linux/docker_wrapper.sh#L32

any thoughts @stefanseefeld?

Use HTTPS when fetching Miniconda

When the miniconda installer is grabbed, it's done over HTTP. Perhaps as an upstream issue, repo.continuum.io should have certificates.

latest images broken due to Docker-related issue in conda 4.4.10

#78 updated continuumio/miniconda3:latest to use conda 4.4.10, but this is problematic due to conda/conda#6811 (comment).
Could we get a non-conda >4.4.7,<4.4.11 image with continuumio/miniconda3:latest?

Default string encoding is set to ascii

The default string encoding in the anaconda3 docker image is set to ascii, so when I try to open a file containing characters such as ä with open(<filename>).read(), I get the following error:

UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 278: ordinal not in range(128)

This seems to be a common problem, see here

Switching to open(<filename>,encoding='utf-8').read() works, but some other things dont, not sure whether it is because of this problem. In general not satisfactory, quite unexpected.

P.S. This seems to be a debian/ubuntu problem, not happening with alpine linux

Readline package appears broken

Moved from ContinuumIO/anaconda-recipes#19

It appears the copy of readline that now fills the channels, possibly the same one provided here, is broken. To see what I mean, try downloading any of the docker images and install ipython with conda. The colors are missing, tab completion fails, using up/down arrows to traverse history fails. This is normally due to a broken readline or a copy of python that failed to link against readline. This really hurts the usability of things like the terminal based iPython.

Unable to verify the certificate

I used the base of the Dockerfile to build a container based on Ubuntu but I'm not able to download the script. When removing the --quiet option I get:

ERROR: cannot verify repo.continuum.io's certificate, issued by '/C=US/O=thawte, Inc./CN=thawte SSL CA - G2':
  Unable to locally verify the issuer's authority.
To connect to repo.continuum.io insecurely, use `--no-check-certificate'.
The command '/bin/sh -c wget https://repo.continuum.io/miniconda/Miniconda2-3.19.0-Linux-x86_64.sh' returned a non-zero code: 5

I resolved it adding --no-check-certificate.

pyplot not available - anaconda3:5.0.1

could be regression of #8 and certainly related to #49

$ docker run -it continuumio/anaconda3:latest python -c '\
> import matplotlib; \
> import matplotlib.pyplot as plt; \
> '
Traceback (most recent call last):
  File "<string>", line 3, in <module>
  File "/opt/conda/lib/python3.6/site-packages/matplotlib/pyplot.py", line 113, in <module>
    _backend_mod, new_figure_manager, draw_if_interactive, _show = pylab_setup()
  File "/opt/conda/lib/python3.6/site-packages/matplotlib/backends/__init__.py", line 60, in pylab_setup
    [backend_name], 0)
  File "/opt/conda/lib/python3.6/site-packages/matplotlib/backends/backend_qt5agg.py", line 16, in <module>
    from .backend_qt5 import (
  File "/opt/conda/lib/python3.6/site-packages/matplotlib/backends/backend_qt5.py", line 18, in <module>
    import matplotlib.backends.qt_editor.figureoptions as figureoptions
  File "/opt/conda/lib/python3.6/site-packages/matplotlib/backends/qt_editor/figureoptions.py", line 20, in <module>
    import matplotlib.backends.qt_editor.formlayout as formlayout
  File "/opt/conda/lib/python3.6/site-packages/matplotlib/backends/qt_editor/formlayout.py", line 56, in <module>
    from matplotlib.backends.qt_compat import QtGui, QtWidgets, QtCore
  File "/opt/conda/lib/python3.6/site-packages/matplotlib/backends/qt_compat.py", line 137, in <module>
    from PyQt5 import QtCore, QtGui, QtWidgets
ImportError: libGL.so.1: cannot open shared object file: No such file or directory

Unable to build a simple program with gcc provided in docker image

I am using the continuumio/conda_builder_linux:latest image and start the image with the build64/start_cpp98.sh script that is provided but I fail to compile a simple program with boost and conda-build.

The test cpp code is this:

#include <boost/filesystem.hpp>

int main() {
  boost::filesystem::path("a.out").extension().c_str();
}

The recipe to build it with conda-build is this:

package:
  name: test
  version: 0.0.1

source:
  path: test.cpp

build:
  script:
    - g++ test.cpp -I ${CONDA_DEFAULT_ENV}/include/ -L ${CONDA_DEFAULT_ENV}/lib -lboost_filesystem -lboost_system
    - cp a.out ${PREFIX}/bin/

requirements:
  build:
    - python 2.7*
    - boost 1.61.0
  run:
    - python 2.7*
    - boost 1.61.0

test:
  commands:
    - a.out

And these are the commands that I run:

$ ./start_cpp98.sh --rm=true -v ~/recipes/:/recipes


Welcome to the conda-builder image, brought to you by Continuum Analytics.

Binaries produced with this image should be compatible with any Linux OS
that is at least CentOS 5 or newer (Glibc lower bound), and anything 
that uses G++ 5.2 or older (libstdc++ upper bound)

    GCC is: gcc (GCC) 5.2.0
    Default C++ ABI: 4 (C++98)
    GLIBC is: glibc 2.5
    ld/binutils is: GNU ld (GNU Binutils) 2.26.20160125

    Native arch is x86_64.  To build 32-bit code, set the ARCH environment
        variable to 32. (-e "ARCH=32" docker argument)

    The dev user (currently signed in) has passwordless sudo access.
    miniconda (2.7) is installed at /opt/miniconda.
    git is also available.
    Your .gitconfig has been imported.

Helpful aliases:
    clone_recipes: clones the conda/conda-recipes repo from Github
    clone_anaconda: clones the continuumIO/anaconda (private) repo from Github
    anaconda_setup: clones anaconda repo and sets up continuum internal build system.

[dev@63520f40e292 ~]$ conda build /recipes/test
BUILD START: test-0.0.1-0
updating index in: /opt/miniconda/conda-bld/linux-64
updating index in: /opt/miniconda/conda-bld/noarch

The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    icu-54.1                   |                0        11.3 MB
    xz-5.2.2                   |                1         669 KB
    python-3.5.2               |                0        17.2 MB
    boost-1.61.0               |           py35_0        16.3 MB
    setuptools-27.2.0          |           py35_0         526 KB
    wheel-0.29.0               |           py35_0          82 KB
    pip-9.0.1                  |           py35_1         1.7 MB
    ------------------------------------------------------------
                                           Total:        47.7 MB

The following NEW packages will be INSTALLED:

    boost:      1.61.0-py35_0
    icu:        54.1-0       
    openssl:    1.0.2j-0     
    pip:        9.0.1-py35_1 
    python:     3.5.2-0      
    readline:   6.2-2        
    setuptools: 27.2.0-py35_0
    sqlite:     3.13.0-0     
    tk:         8.5.18-0     
    wheel:      0.29.0-py35_0
    xz:         5.2.2-1      
    zlib:       1.2.8-3      


WARNING: conda-build appears to be out of date. You have version 2.0.11 but the
latest version is 2.1.0. Run

conda update -n root conda-build

to get the latest version.

Copying /recipes/test/test.cpp to /opt/miniconda/conda-bld/test_1483546947159/work
Package: test-0.0.1-0
source tree in: /opt/miniconda/conda-bld/test_1483546947159/work
+ source /opt/miniconda/bin/activate /opt/miniconda/conda-bld/test_1483546947159/_b_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac
+ g++ test.cpp -I /opt/miniconda/conda-bld/test_1483546947159/_b_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/include/ -L /opt/miniconda/conda-bld/test_1483546947159/_b_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib -lboost_filesystem -lboost_system
+ cp a.out /opt/miniconda/conda-bld/test_1483546947159/_b_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/bin/
number of files: 1
Fixing permissions
patchelf: file: /opt/miniconda/conda-bld/test_1483546947159/_b_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/bin/a.out
    setting rpath to: $ORIGIN/../lib
Fixing permissions
updating index in: /opt/miniconda/conda-bld/linux-64
updating: test-0.0.1-0.tar.bz2
TEST START: test-0.0.1-0
updating index in: /opt/miniconda/conda-bld/linux-64
updating index in: /opt/miniconda/conda-bld/noarch

The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    test-0.0.1                 |                0           7 KB  local

The following NEW packages will be INSTALLED:

    boost:      1.61.0-py35_0      
    icu:        54.1-0             
    openssl:    1.0.2j-0           
    pip:        9.0.1-py35_1       
    python:     3.5.2-0            
    readline:   6.2-2              
    setuptools: 27.2.0-py35_0      
    sqlite:     3.13.0-0           
    test:       0.0.1-0       local
    tk:         8.5.18-0           
    wheel:      0.29.0-py35_0      
    xz:         5.2.2-1            
    zlib:       1.2.8-3            


WARNING: conda-build appears to be out of date. You have version 2.0.11 but the
latest version is 2.1.0. Run

conda update -n root conda-build

to get the latest version.

+ source /opt/miniconda/bin/activate /opt/miniconda/conda-bld/test_1483546947159/_t_env
+ /bin/bash -x -e /opt/miniconda/conda-bld/test_1483546947159/test_tmp/run_test.sh
+ a.out
/opt/miniconda/conda-bld/test_1483546947159/test_tmp/run_test.sh: line 3:   140 Segmentation fault      (core dumped) a.out
TESTS FAILED: test-0.0.1-0

It segfaults.
This is easily reproducible through this test code that I have provided here.
It segfaults on ArchLinux's gcc too:

$ g++ --version
g++ (GCC) 6.2.1 20160830
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

but it compiles fine when I use the gcc and libgcc packages from the defaults channel:

package:
  name: test
  version: 0.0.1

source:
  path: test.cpp

build:
  script:
    - g++ test.cpp -I ${CONDA_DEFAULT_ENV}/include/ -L ${CONDA_DEFAULT_ENV}/lib -lboost_filesystem -lboost_system
    - cp a.out ${PREFIX}/bin/

requirements:
  build:
    - python 2.7*
    - boost 1.61.0
    - gcc
  run:
    - python 2.7*
    - boost 1.61.0
    - libgcc

test:
  commands:
    - a.out

Isn't boost in the defaults channel compiled with the same image? Is this a boost bug or a gcc problem?

ping @msarahan @ccordoba12

trouble using a program installed by Miniconda

I have a program that's called MAC2 and it's requiring HTSeq as a prerequisite .
I managed to install all the prerequisites using miniconda. HTSeq couldn't be detected by conda, so I used pip of the miniconda to install it(it installed in miniconda2/bin)

However whenever I try to run the program i get this message:
/home/pk2/miniconda2/lib/python2.7/site-packages/HTSeq/_HTSeq.so: undefined symbol: PyFPE_jbuf. This module is required.

I read online , they said it's probably because another HTSeq is installed somewhere else but :
I removed all the other HTSeq install using sudo pip uninstall HTSeq
Also my path is directed immediately to the miniconda work environment .

Any insight would helpful.

Creating the anaconda3/Dockerfile fails

When trying to build the anaconda3 image locally I get the following error -

E: Failed to fetch http://httpredir.debian.org/debian/pool/main/s/shared-mime-info/shared-mime-info_1.3-1_amd64.deb  Error reading from server. Remote end closed connection ¡IP: 5.153.231.35 80¿

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

After adding the --fix-missing flag to the apt-get install command the image builds fine. Shouldn't that be added to the dockerfile?

Bump Python version on Docker Hub

Could you bump the python version in the description on the docker hub? I wanted python 3.6 and I only noticed it was already updated when I came here.

Create light example/sample of follow on Docker image

It would be nice to see what the best practice would be for a follow on image.

If I know Docker, how do I get started using miniconda in this way?
Where should my conda environments go if I create a new user?

Can't install gcc in image

Installing any packages that use gcc as dep don't work.

root@ddd06055156a:/# conda install gcc
Using Anaconda Cloud api site https://api.anaconda.org
Fetching package metadata: ....
Solving package specifications: ....................
Package plan for installation in environment /opt/conda:

The following NEW packages will be INSTALLED:

    gcc: 4.8.5-3

Proceed ([y]/n)?

Linking packages ...
/opt/conda/bin/.gcc-post-link.sh: line 114: ld: command not found                                                                                                                                                                                                                                                                                                     |   0%
Couldn't locate crtXXX.o in default library search paths. You may not have it  at all. It is usually packaged in libc6-dev/glibc-devel packages. We will try  to locate crtXXX.o with system installed gcc...
There is no /usr/bin/gcc
*** Can't install the gcc package unless your system has crtXXX.o. ***
Error: Error: post-link failed for: gcc-4.8.5-3

conda activate <SMTH>

I do: docker run -i -t continuumio/anaconda3 /bin/bash
Then i try to activate any env (for ex base) with conda activate base i recieve

CommandNotFoundError: Your shell has not been properly configured to use 'conda activate'.
If your shell is Bash or a Bourne variant, enable conda for the current user with

    $ echo ". /opt/conda/etc/profile.d/conda.sh" >> ~/.bashrc

or, for all users, enable conda with

    $ sudo ln -s /opt/conda/etc/profile.d/conda.sh /etc/profile.d/conda.sh

The options above will permanently enable the 'conda' command, but they do NOT
put conda's base (root) environment on PATH.  To do so, run

    $ conda activate

in your terminal, or to put the base environment on PATH permanently, run

    $ echo "conda activate" >> ~/.bashrc

Previous to conda 4.4, the recommended way to activate conda was to modify PATH in
your ~/.bashrc file.  You should manually remove the line that looks like

    export PATH="/opt/conda/bin:$PATH"

^^^ The above line should NO LONGER be in your ~/.bashrc file! ^^^

I believe this is related with the change in recomended way to enable conda in shell
https://github.com/conda/conda/releases/tag/4.4.0

more specifically this is the line that creates this problem

docker-images/anaconda3/Dockerfile

Line 11 in 1304433

RUN echo 'export PATH=/opt/conda/bin:$PATH' > /etc/profile.d/conda.sh && \

unfortunatelly i can't figure out how to fix it.

Built libraries incompatible with Travis-CI

The libstdc++ used on the build image is too young. When trying to use a shared library built under Ubuntu 14.04 (e.g. on Travis-CI), it fails:
https://travis-ci.org/numba/llvmlite/jobs/147763059#L375

We didn't have this issue when we built on CentOS 5 with the RH developer toolset 2.

Cannot import matplotlib.pyplot in docker container

I get this error: ImportError: libgthread-2.0.so.0: cannot open shared object file: No such file or directory

The full error output is below.

I am running Docker using boot2docker on a Mac.

bash-3.2$ docker run -i -t continuumio/anaconda /bin/bash
root@a14804e988fd:/# ipython
WARNING: Readline services not available or not loaded.
WARNING: The auto-indent feature requires the readline library
Python 2.7.9 |Anaconda 2.2.0 (64-bit)| (default, Mar 9 2015, 16:20:48)
Type "copyright", "credits" or "license" for more information.

IPython 3.0.0 -- An enhanced Interactive Python.
Anaconda is brought to you by Continuum Analytics.
Please check out: http://continuum.io/thanks and https://binstar.org
? -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help -> Python's own help system.
object? -> Details about 'object', use 'object??' for extra details.

In [1]: import matplotlib.pyplot

ImportError Traceback (most recent call last)
in ()
----> 1 import matplotlib.pyplot

/opt/conda/lib/python2.7/site-packages/matplotlib/pyplot.py in ()
107
108 from matplotlib.backends import pylab_setup
--> 109 _backend_mod, new_figure_manager, draw_if_interactive, _show = pylab_setup()
110
111

/opt/conda/lib/python2.7/site-packages/matplotlib/backends/init.pyc in pylab_setup()
30 # imports. 0 means only perform absolute imports.
31 backend_mod = import(backend_name,
---> 32 globals(),locals(),[backend_name],0)
33
34 # Things we pull in from all backends

/opt/conda/lib/python2.7/site-packages/matplotlib/backends/backend_qt4agg.py in ()
15 from matplotlib.figure import Figure
16
---> 17 from .backend_qt5agg import NavigationToolbar2QTAgg
18 from .backend_qt5agg import FigureCanvasQTAggBase
19

/opt/conda/lib/python2.7/site-packages/matplotlib/backends/backend_qt5agg.py in ()
16
17 from .backend_agg import FigureCanvasAgg
---> 18 from .backend_qt5 import QtCore
19 from .backend_qt5 import QtGui
20 from .backend_qt5 import FigureManagerQT

/opt/conda/lib/python2.7/site-packages/matplotlib/backends/backend_qt5.py in ()
29 figureoptions = None
30
---> 31 from .qt_compat import QtCore, QtGui, QtWidgets, _getSaveFileName, version
32 from matplotlib.backends.qt_editor.formsubplottool import UiSubplotTool
33

/opt/conda/lib/python2.7/site-packages/matplotlib/backends/qt_compat.py in ()
89 if QT_API in [QT_API_PYQT, QT_API_PYQTv2]: # PyQt4 API
90
---> 91 from PyQt4 import QtCore, QtGui
92
93 try:

ImportError: libgthread-2.0.so.0: cannot open shared object file: No such file or directory

Can't build your docker files

I'm trying to build your dockerfiles (both miniconda and conda) where I've only edited the conda version from 64bit to 32bit - unfortunately in any case (even with 64bit) I always get the same error:

/root/anaconda.sh: line 358: /opt/conda/pkgs/python-2.7.14-h41cc02d_21/bin/python: No such file or directory

The above error happens on step 5/9 (anaconda installation)

I would appreciate help here as I need specifically 32bit, otherwise I would have pulled a pre-built image from docker hub.

Thanks

What's the best way of building own docker image using a particular Python version?

Instead of using e.g. https://repo.continuum.io/archive/Anaconda3-4.1.1-Linux-x86_64.sh?

gcc does not work

This is quite broken:

FROM continuumio/miniconda:3.19.0
ENV PATH /opt/miniconda2/bin:$PATH
RUN conda install conda-build gcc

...
Couldn't locate crtXXX.o in default library search paths. You may not have it  at all. It is usually packaged in libc6-dev/glibc-devel packages. We will try  to locate crtXXX.o with system installed gcc...
There is no /usr/bin/gcc
*** Can't install the gcc package unless your system has crtXXX.o. ***
conda-build-1. 100% |###############################| Time: 0:00:00 492.87 kB/s
Extracting packages ...
[      COMPLETE      ]|##################################################| 100%
Unlinking packages ...
[      COMPLETE      ]|##################################################| 100%
Linking packages ...
Error: Error: post-link failed for: gcc-4.8.5-3