Problem with docker build to contribute on Mac

[Mxchaeltrxn]

Hi. I'm not sure if this is the right place to post this but I would love to contribute so I'm asking here. I apologise if this is the wrong place to post it. If it is, could someone redirect me to a better person or place to ask?

I use:

• Mac OS version 10.15.1
• I used brew cask install anaconda to install anaconda and I have export PATH=~/opt/anaconda3/bin:$PATH in my .zshrc file. conda --version outputs conda 4.7.12

I'm having trouble using docker with this project. This is what happens when I follow VS code remote containers and run Remote-Containers: Reopen in Container. My error is below (I've removed the bits that were successful).

[2020-03-06T10:49:02.538Z] [PID 15817] [29814 ms] Step 8/9 : RUN conda env update -n base -f "$pandas_home/environment.yml"
[2020-03-06T10:49:02.538Z] [PID 15817] [29814 ms]
[2020-03-06T10:49:05.305Z] [PID 15817] [32581 ms] ---> Running in d123b4efef44
[2020-03-06T10:49:05.960Z] [PID 15817] [33236 ms] Traceback (most recent call last):
File "/opt/conda/bin/conda", line 12, in
from conda.cli import main
ModuleNotFoundError: No module named 'conda'
[2020-03-06T10:49:06.502Z] [PID 15817] [33778 ms] The command '/bin/sh -c conda env update -n base -f "$pandas_home/environment.yml"' returned a non-zero code: 1
[2020-03-06T10:49:06.505Z] [PID 15817] [33781 ms] Failed: Building an image from the Dockerfile (this can take a while).
[2020-03-06T10:49:06.508Z] [PID 15817] [33784 ms] Command failed: docker build -f /Users/mxchaeltrxn/Documents/10-19_learning/14_open_source/14.03_pandas/Dockerfile -t vsc-14.03_pandas-a5707944db87809e2912a2e16627e33b /Users/mxchaeltrxn/Documents/10-19_learning/14_open_source/14.03_pandas

[TomAugspurger]

Can you retry with a fresh environment? This sounds like #32241

[Mxchaeltrxn]

@TomAugspurger What do you mean by fresh environment and/or how do you make the environment fresh?

[TomAugspurger]

Pull pandas and recreate the conda env (so I guess rebuild the docker image)

…

On Mar 6, 2020, at 17:03, Mxchaeltrxn ***@***.***> wrote:  @TomAugspurger What do you mean by fresh environment? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[Mxchaeltrxn]

So I ran git pull upstream master and then did Remote-Container: Reopen in Container but I get the same error

[mroeschke]

Looks like this is based on the old Dockerfile we used to have. I think users have been using the newer Docker container with VSCode more successfully so closing