BioSystemsUM / drug_response_pipeline

MIT License
5 stars 1 forks source link

Dockerfile is no longer working #1

Open jjacobson95 opened 7 months ago

jjacobson95 commented 7 months ago

The docker build command no longer works. Is this docker image hosted on dockerhub anywhere? A stable version would be a great addition to this project.

Docker build error:

WARNING: experimental flag squash is removed with BuildKit. You should squash inside build using a multi-stage Dockerfile for efficiency.
[+] Building 5.8s (6/39)                                                                                                                                                                                           docker:desktop-linux
 => [internal] load .dockerignore                                                                                                                                                                                                  0.0s
 => => transferring context: 2B                                                                                                                                                                                                    0.0s
 => [internal] load build definition from Dockerfile                                                                                                                                                                               0.0s
 => => transferring dockerfile: 3.32kB                                                                                                                                                                                             0.0s
 => [internal] load metadata for docker.io/nvidia/cuda:11.1.1-cudnn8-runtime-ubuntu18.04                                                                                                                                           0.6s
 => [ 1/36] FROM docker.io/nvidia/cuda:11.1.1-cudnn8-runtime-ubuntu18.04@sha256:62d739ff971db134d035baa73380899d433cd9132c26635bb478f021671822cd                                                                                   0.0s
 => CACHED [ 2/36] RUN apt-get update &&  apt-get upgrade -yq &&  DEBIAN_FRONTEND="noninteractive" apt-get install -yq wget bzip2 libxrender1 libxext-dev gcc git-all &&  apt-get clean                                            0.0s
 => ERROR [ 3/36] RUN MINICONDA="Miniconda3-latest-Linux-x86_64.sh" &&     wget --quiet https://repo.continuum.io/miniconda/$MINICONDA &&     bash $MINICONDA -b -p /miniconda &&     rm -f $MINICONDA                             5.1s
------                                                                                                                                                                                                                                  
 > [ 3/36] RUN MINICONDA="Miniconda3-latest-Linux-x86_64.sh" &&     wget --quiet https://repo.continuum.io/miniconda/$MINICONDA &&     bash $MINICONDA -b -p /miniconda &&     rm -f $MINICONDA:                                        
4.418 PREFIX=/miniconda                                                                                                                                                                                                                 
4.830 Unpacking payload ...
4.832 qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory
------
Dockerfile:15
--------------------
  14 |     # Install miniconda
  15 | >>> RUN MINICONDA="Miniconda3-latest-Linux-x86_64.sh" && \
  16 | >>>     wget --quiet https://repo.continuum.io/miniconda/$MINICONDA && \
  17 | >>>     bash $MINICONDA -b -p /miniconda && \
  18 | >>>     rm -f $MINICONDA
  19 |     ENV PATH /miniconda/bin:$PATH
--------------------
ERROR: failed to solve: process "/bin/sh -c MINICONDA=\"Miniconda3-latest-Linux-x86_64.sh\" &&     wget --quiet https://repo.continuum.io/miniconda/$MINICONDA &&     bash $MINICONDA -b -p /miniconda &&     rm -f $MINICONDA" did not complete successfully: exit code: 255
dlrsb commented 7 months ago

Hi jjacobson95. Thank you for reporting this issue. We haven't pushed this image to Docker Hub. I'm no longer working on this project and don't have access to the machines where I used to build this image. I tried to build it on my current laptop and with the legacy builder it didn't fail at the same step (step 3), but it did fail further on (step 5), so I'll have to look into this. I saw this StackOverflow post which seems to be related to the issue you're reporting here, if you want to try out some of the suggestions in the meanwhile.