Question

我有以下Dockerfile。

FROM continuumio/miniconda3:4.5.11

# create a new user (defaults to 'al-khawarizmi')
USER root
ARG username=al-khawarizmi
RUN useradd --create-home --home-dir /home/${username} ${username}
ENV HOME /home/${username}

# switch to newly created user to avoid running container as root
USER ${username}
WORKDIR $HOME

# build and activate the specified conda environment from a file (defaults to 'environment.yml')
ARG environment=environment.yml
COPY ${environment} .
RUN conda env create --file ${environment} && \
    echo ". /opt/conda/etc/profile.d/conda.sh" >> ~/.bashrc && \ 
    echo "conda activate $(head -1 ${environment} | cut -d' ' -f2)" >> ~/.bashrc

Dockerfile允许用户将conda环境文件指定为构建arg。这是典型的environment.yml file。

name: nessie-py

channels:
  - conda-forge
  - defaults

dependencies:
  - python=3.6
  - "notebook=5.7.*"
  - "matplotlib=3.0.*"
  - "numpy=1.15.*"
  - "pandas=0.23.*"

用户可以以标准方式运行图像，conda环境将被自动激活。正在运行

$ docker run -it image_name:image_tag

在激活conda环境的Docker容器中产生bash提示。

(environment_name)$

现在，我想使用docker-compose在容器中启动Jupyter笔记本服务器（使用指定Jupyter作为依赖项的conda环境文件构建）。

当我使用以下docker-compose.yml

时

version: "3.7"

services:
  notebook-server:
    build:
      context: ./
    ports:
      - "8888:8888"
    volumes:
      - ./:/home/al-khawarizmi
    command: jupyter notebook --no-browser ip=0.0.0.0

我收到以下错误消息。

$ docker-compose up
Creating network "nessie-py_default" with the default driver
Creating nessie-py_notebook-server_1 ... done
Attaching to nessie-py_notebook-server_1
notebook-server_1  | [FATAL tini (7)] exec jupyter failed: No such file or directory
nessie-py_notebook-server_1 exited with code 127

我怀疑此错误意味着未激活conda环境。然后，我尝试将tty: true和stdin_open: true添加到docker-compose.yml上，以为这应该在运行command之前调用交互式bash提示。这导致了与上述相同的错误。

我还尝试定义一个start-notebook.sh脚本，该脚本在运行笔记本电脑之前显式激活conda环境。

#!/bin/bash
set -e

# activate the environment and start the notebook
conda activate nessie-py
jupyter notebook --no-browser ip=0.0.0.0

导致其他错误

$ docker-compose up
Creating network "nessie-py_default" with the default driver
Creating nessie-py_notebook-server_1 ... done
Attaching to nessie-py_notebook-server_1
notebook-server_1  | 
notebook-server_1  | CommandNotFoundError: Your shell has not been properly configured to use 'conda activate'.
notebook-server_1  | If your shell is Bash or a Bourne variant, enable conda for the current user with
notebook-server_1  | 
notebook-server_1  |     $ echo ". /opt/conda/etc/profile.d/conda.sh" >> ~/.bashrc
notebook-server_1  | 
notebook-server_1  | or, for all users, enable conda with
notebook-server_1  | 
notebook-server_1  |     $ sudo ln -s /opt/conda/etc/profile.d/conda.sh /etc/profile.d/conda.sh
notebook-server_1  | 
notebook-server_1  | The options above will permanently enable the 'conda' command, but they do NOT
notebook-server_1  | put conda's base (root) environment on PATH.  To do so, run
notebook-server_1  | 
notebook-server_1  |     $ conda activate
notebook-server_1  | 
notebook-server_1  | in your terminal, or to put the base environment on PATH permanently, run
notebook-server_1  | 
notebook-server_1  |     $ echo "conda activate" >> ~/.bashrc
notebook-server_1  | 
notebook-server_1  | Previous to conda 4.4, the recommended way to activate conda was to modify PATH in
notebook-server_1  | your ~/.bashrc file.  You should manually remove the line that looks like
notebook-server_1  | 
notebook-server_1  |     export PATH="/opt/conda/bin:$PATH"
notebook-server_1  | 
notebook-server_1  | ^^^ The above line should NO LONGER be in your ~/.bashrc file! ^^^
notebook-server_1  | 
notebook-server_1  | 
nessie-py_notebook-server_1 exited with code 1

此错误表明bash在运行脚本之前没有采购~/.bashrc。

在激活conda环境之前，我尝试显式采购/opt/conda/etc/profile.d/conda.sh。

#!/bin/bash
set -e

# activate the environment and start the notebook
. /opt/conda/etc/profile.d/conda.sh
conda activate nessie-py
jupyter notebook --no-browser ip=0.0.0.0

这会导致其他错误！

$ docker-compose up
Creating network "nessie-py_default" with the default driver
Creating nessie-py_notebook-server_1 ... done
Attaching to nessie-py_notebook-server_1
notebook-server_1  | Could not find conda environment: nessie-py
notebook-server_1  | You can list all discoverable environments with `conda info --envs`.
notebook-server_1  | 
nessie-py_notebook-server_1 exited with code 1

我可以通过运行查看是否可以在容器中发现哪些conda envs

$ docker run -it nessie-py conda info --envs

说环境确实存在。

$ docker run -it nessie-py_notebook-server conda info --envs
# conda environments:
#
nessie-py                /home/al-khawarizmi/.conda/envs/nessie-py
base                  *  /opt/conda

我现在没有主意。这应该是可能的。 Here是带有docker-compose.yml文件的项目的示例，该文件是一个指定conda环境并启动Jupyter笔记本服务器的Dockerfile。

我需要的其他复杂性包括将非root用户添加到Dockerfile并创建新的conda环境，而不是更新默认的base conda环境。

Answer 1

发生的事情是由于以下原因造成的：

在docker-compose.yml中，您在ip=0.0.0.0中有一个错字，应该是--ip=0.0.0.0
将主机的文件夹绑定到容器中将覆盖.bashrc。一个简单的更改就是将其装入子目录
您需要以交互模式（-i）运行bash，以便正确读取.bashrc

例如，这些点的变化反映在您的docker-compose.yml中：

version: "3.7"

    services:
      notebook-server:
        build:
          context: ./
        ports:
          - "8888:8888"
        volumes:
          - ./:/home/al-khawarizmi/hosthome
        command: bash -ic 'jupyter notebook --no-browser --ip=0.0.0.0'

使用docker-compose启动Jupyter Notebook时，在Docker容器内激活conda env

1 个答案: