我的Dockerfile类似于
FROM my/base
ADD . /srv
RUN pip install -r requirements.txt
RUN python setup.py install
ENTRYPOINT ["run_server"]
每次我构建新的镜像时,都必须重新安装依赖项,这在我所在的区域可能会非常慢。
对于已经安装的cache
包,我想到的一种方法是用更新的镜像覆盖my/base
镜像,如下所示:
docker build -t new_image_1 .
docker tag new_image_1 my/base
因此,下次我使用此Dockerfile进行构建时,我的/base已经安装了一些包。
但是这个解决方案有两个问题:
那么我可以使用什么更好的解决方案来解决这个问题呢?
编辑:
关于我机器上的docker的一些信息:
☁ test docker version
Client version: 1.1.2
Client API version: 1.13
Go version (client): go1.2.1
Git commit (client): d84a070
Server version: 1.1.2
Server API version: 1.13
Go version (server): go1.2.1
Git commit (server): d84a070
☁ test docker info
Containers: 0
Images: 56
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Dirs: 56
Execution Driver: native-0.2
Kernel Version: 3.13.0-29-generic
WARNING: No swap limit support
发布于 2014-08-14 20:01:48
尝试构建如下所示的Dockerfile:
FROM my/base
WORKDIR /srv
ADD ./requirements.txt /srv/requirements.txt
RUN pip install -r requirements.txt
ADD . /srv
RUN python setup.py install
ENTRYPOINT ["run_server"]
只要您不对requirements.txt
进行任何更改,Docker将在pip安装过程中使用缓存,而不管Docker上的其他代码文件是否已更改。下面是一个例子。
下面是一个简单的Hello, World!
程序:
$ tree
.
├── Dockerfile
├── requirements.txt
└── run.py
0 directories, 3 file
# Dockerfile
FROM dockerfile/python
WORKDIR /srv
ADD ./requirements.txt /srv/requirements.txt
RUN pip install -r requirements.txt
ADD . /srv
CMD python /srv/run.py
# requirements.txt
pytest==2.3.4
# run.py
print("Hello, World")
docker build的输出:
Step 1 : WORKDIR /srv
---> Running in 22d725d22e10
---> 55768a00fd94
Removing intermediate container 22d725d22e10
Step 2 : ADD ./requirements.txt /srv/requirements.txt
---> 968a7c3a4483
Removing intermediate container 5f4e01f290fd
Step 3 : RUN pip install -r requirements.txt
---> Running in 08188205e92b
Downloading/unpacking pytest==2.3.4 (from -r requirements.txt (line 1))
Running setup.py (path:/tmp/pip_build_root/pytest/setup.py) egg_info for package pytest
....
Cleaning up...
---> bf5c154b87c9
Removing intermediate container 08188205e92b
Step 4 : ADD . /srv
---> 3002a3a67e72
Removing intermediate container 83defd1851d0
Step 5 : CMD python /srv/run.py
---> Running in 11e69b887341
---> 5c0e7e3726d6
Removing intermediate container 11e69b887341
Successfully built 5c0e7e3726d6
让我们修改一下run.py
# run.py
print("Hello, Python")
尝试再次构建,以下是输出:
Sending build context to Docker daemon 5.12 kB
Sending build context to Docker daemon
Step 0 : FROM dockerfile/python
---> f86d6993fc7b
Step 1 : WORKDIR /srv
---> Using cache
---> 55768a00fd94
Step 2 : ADD ./requirements.txt /srv/requirements.txt
---> Using cache
---> 968a7c3a4483
Step 3 : RUN pip install -r requirements.txt
---> Using cache
---> bf5c154b87c9
Step 4 : ADD . /srv
---> 9cc7508034d6
Removing intermediate container 0d7cf71eb05e
Step 5 : CMD python /srv/run.py
---> Running in f25c21135010
---> 4ffab7bc66c7
Removing intermediate container f25c21135010
Successfully built 4ffab7bc66c7
正如您在上面看到的,这一次docker在构建过程中使用缓存。现在,让我们更新requirements.txt
# requirements.txt
pytest==2.3.4
ipython
以下是docker build的输出:
Sending build context to Docker daemon 5.12 kB
Sending build context to Docker daemon
Step 0 : FROM dockerfile/python
---> f86d6993fc7b
Step 1 : WORKDIR /srv
---> Using cache
---> 55768a00fd94
Step 2 : ADD ./requirements.txt /srv/requirements.txt
---> b6c19f0643b5
Removing intermediate container a4d9cb37dff0
Step 3 : RUN pip install -r requirements.txt
---> Running in 4b7a85a64c33
Downloading/unpacking pytest==2.3.4 (from -r requirements.txt (line 1))
Running setup.py (path:/tmp/pip_build_root/pytest/setup.py) egg_info for package pytest
Downloading/unpacking ipython (from -r requirements.txt (line 2))
Downloading/unpacking py>=1.4.12 (from pytest==2.3.4->-r requirements.txt (line 1))
Running setup.py (path:/tmp/pip_build_root/py/setup.py) egg_info for package py
Installing collected packages: pytest, ipython, py
Running setup.py install for pytest
Installing py.test script to /usr/local/bin
Installing py.test-2.7 script to /usr/local/bin
Running setup.py install for py
Successfully installed pytest ipython py
Cleaning up...
---> 23a1af3df8ed
Removing intermediate container 4b7a85a64c33
Step 4 : ADD . /srv
---> d8ae270eca35
Removing intermediate container 7f003ebc3179
Step 5 : CMD python /srv/run.py
---> Running in 510359cf9e12
---> e42fc9121a77
Removing intermediate container 510359cf9e12
Successfully built e42fc9121a77
注意docker在pip安装过程中没有使用缓存。如果它不工作,请检查您的docker版本。
Client version: 1.1.2
Client API version: 1.13
Go version (client): go1.2.1
Git commit (client): d84a070
Server version: 1.1.2
Server API version: 1.13
Go version (server): go1.2.1
Git commit (server): d84a070
发布于 2016-10-29 23:19:44
要最小化网络活动,您可以将pip
指向主机上的缓存目录。
运行docker容器,并将主机的pip缓存目录bind挂载到容器的pip缓存目录中。docker run
命令应如下所示:
docker run -v $HOME/.cache/pip-docker/:/root/.cache/pip image_1
然后,在您的Dockerfile文件中,将需求作为ENTRYPOINT
语句(或CMD
语句)的一部分安装,而不是作为RUN
命令。这一点很重要,因为(正如注释中指出的)挂载在映像构建期间不可用(当执行RUN
语句时)。Docker文件应如下所示:
FROM my/base
ADD . /srv
ENTRYPOINT ["sh", "-c", "pip install -r requirements.txt && python setup.py install && run_server"]
发布于 2021-06-19 07:27:06
pipenv install
默认情况下会尝试重新锁定。当它这样做的时候,Docker构建的缓存层不会被使用,因为Pipfile.lock已经改变了。See the docs
解决此问题的方法是对Pipfile.lock进行版本化,并使用
RUN pipenv sync
而不是。
感谢JFG Piñeiro。
https://stackoverflow.com/questions/25305788
复制相似问题