This shows two issues that come with a local export on an operating system than your deployment operating system. It suffices actually to only look at the libcxx=11.0.1=habf9029_0 line. In our initial setting, we have checked out the git repository and are running all commands from the repository root. The model is served via FastAPI and is already using the best practices like uvicorn there. While I have seen this approach in the wild, most of the ones I have seen were already using the basic things I will improve in the first sections.Īs an example, I have built a really simple machine learning model using scikit-learn and LightGBM that predicts a fare price for a taxi trip in New York City. I have chosen a particularly bad one here to explain some more things. There are several simple but not so effective approaches to put conda environments into a container.

We will look at all the flaws this approach brings with it and optimise the workflow bit-for-bit until we reach a near-perfect container.

In this article, I though want to start at the beginning again and have a look at the most obvious way one would put a conda environment into a Docker container. Over the course of time, we have also developed new techniques that help trim down the sizes of Docker containers even further. Due to changes in the default content of conda-forge packages and specific optimisation of some particular heavy packages, it will though yield fewer savings nowadays. It is still as valid nowadays as it was back then.

But with a bit more love for details, you can optimise the process so that the build is faster and the resulting container much smaller.įor optimising conda-environments-in-docker Jim Crist-Harif’s “Smaller Docker images with Conda” blog post has been the go-to resource for a long time. Deploying conda environments in (Docker) containers - how to do it rightĭeploying conda environments inside a container looks like a straight-forward conda install.

Conda install