[v0.24.0] Local docker build fails
Closed this issue · 3 comments
Description
My local docker build is failing at v0.24.0 during the mamba env create step of the install script. Any guidance?
- Docker build runs fine when I role back to
v0.23.0 - May be related to bumping the ubuntu base image 256b015
Thanks for the help!
System details
- MacOS
Ventura 13.4 - Docker
24.0.5
Full error
$ docker build -f Dockerfile -t openwpm . [16:10:47]
[+] Building 97.8s (12/13) docker:desktop-linux
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 1.11kB 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 434B 0.0s
=> [internal] load metadata for docker.io/library/ubuntu:xenial 0.0s
=> [1/9] FROM docker.io/library/ubuntu:xenial 0.0s
=> [internal] load build context 0.2s
=> => transferring context: 28.93MB 0.2s
=> [2/9] RUN sed -i'' 's/archive\.ubuntu\.com/us\.archive\.ubuntu\.com/' /etc/apt/sources.list 0.2s
=> [3/9] RUN apt-get clean -qq && rm -r /var/lib/apt/lists/* -vf && apt-get clean -qq && apt-get u 71.9s
=> [4/9] COPY scripts/install-mamba.sh . 0.1s
=> [5/9] RUN ./install-mamba.sh 16.8s
=> [6/9] WORKDIR /opt/OpenWPM 0.0s
=> [7/9] COPY . . 0.1s
=> ERROR [8/9] RUN ./install.sh 8.6s
------
> [8/9] RUN ./install.sh:
0.303 Creating / Overwriting openwpm conda environment.
8.417 Could not solve for environment specs
8.417 The following packages are incompatible
8.417 ├─ geckodriver 0.33.0** does not exist (perhaps a typo or a missing channel);
8.417 ├─ pyvirtualdisplay 3.0** does not exist (perhaps a typo or a missing channel);
8.417 └─ selenium 4.12.0** is uninstallable because it requires
8.417 └─ selenium-manager 4.12.* , which does not exist (perhaps a missing channel).
------
Dockerfile:26
--------------------
24 | WORKDIR /opt/OpenWPM
25 | COPY . .
26 | >>> RUN ./install.sh
27 | ENV PATH $HOME/mamba/envs/openwpm/bin:$PATH
28 |
--------------------
ERROR: failed to solve: process "/bin/bash -c ./install.sh" did not complete successfully: exit code: 1
(base) FAIL
Hey,
thanks for reporting this bug.
I'm a bit surprised to hear that, as our CI is passing for that commit (which includes building and publishing a Docker image )
My first assumption would be an outage in conda-forge, but I'll try to reproduce the issue later.
Thanks for taking a look! I was also surprised since CI is building the image normally. Please let me know if you need anything for the repro. I've been seeing this issue since I started using the project about a week ago.
I did a clean checkout on my machine (Linux) and docker build -f Dockerfile -t openwpm . just ran through without an issue 🙁
I know you said you just checked out v0.24.0 but just to confirm:
- Did you run
./install.shlocally before this? (Shouldn't change anything, but 🤷) - Is your repo completely clean?
- Can you comment out everything line 25, and then
docker run -it --rm --name openwpm openwpm bashand execute./install.shin there yourself