a ML to be helpful it must run someplace. This someplace is probably not your native machine. A not-so-good mannequin that runs in a manufacturing surroundings is best than an ideal mannequin that by no means leaves your native machine.
Nevertheless, the manufacturing machine is often totally different from the one you developed the mannequin on. So, you ship the mannequin to the manufacturing machine, however one way or the other the mannequin doesn’t work anymore. That’s bizarre, proper? You examined every part in your native machine and it labored positive. You even wrote unit assessments.
What occurred? Almost definitely the manufacturing machine differs out of your native machine. Maybe it doesn’t have all of the wanted dependencies put in to run your mannequin. Maybe put in dependencies are on a distinct model. There will be many causes for this.
How will you remedy this drawback? One method may very well be to precisely replicate the manufacturing machine. However that may be very rigid as for every new manufacturing machine you would want to construct an area duplicate.
A a lot nicer method is to make use of Docker containers.
Docker is a instrument that helps us to create, handle, and run code and functions in containers. A container is a small remoted computing surroundings by which we will bundle an software with all its dependencies. In our case our ML mannequin with all of the libraries it must run. With this, we don’t have to depend on what’s put in on the host machine. A Docker Container allows us to separate functions from the underlying infrastructure.
For instance, we bundle our ML mannequin regionally and push it to the cloud. With this, Docker helps us to make sure that our mannequin can run wherever and anytime. Utilizing Docker has a number of benefits for us. It helps us to ship new fashions quicker, enhance reproducibility, and make collaboration simpler. All as a result of now we have precisely the identical dependencies irrespective of the place we run the container.
As Docker is broadly used within the business Information Scientists want to have the ability to construct and run containers utilizing Docker. Therefore, on this article, I’ll undergo the essential idea of containers. I’ll present you all it is advisable to learn about Docker to get began. After now we have lined the speculation, I’ll present you how one can construct and run your individual Docker container.
What’s a container?
A container is a small, remoted surroundings by which every part is self-contained. The surroundings packages up all code and dependencies.
A container has 5 most important options.
- self-contained: A container isolates the applying/software program, from its surroundings/infrastructure. As a result of this isolation, we don’t have to depend on any pre-installed dependencies on the host machine. All the pieces we want is a part of the container. This ensures that the applying can at all times run whatever the infrastructure.
- remoted: The container has a minimal affect on the host and different containers and vice versa.
- impartial: We will handle containers independently. Deleting a container doesn’t have an effect on different containers.
- transportable: As a container isolates the software program from the {hardware}, we will run it seamlessly on any machine. With this, we will transfer it between machines with out a drawback.
- light-weight: Containers are light-weight as they share the host machine’s OS. As they don’t require their very own OS, we don’t have to partition the {hardware} useful resource of the host machine.
This may sound just like digital machines. However there’s one huge distinction. The distinction is in how they use their host laptop’s sources. Digital machines are an abstraction of the bodily {hardware}. They partition one server into a number of. Thus, a VM features a full copy of the OS which takes up extra space.
In distinction, containers are an abstraction on the software layer. All containers share the host’s OS however run in remoted processes. As a result of containers don’t include an OS, they’re extra environment friendly in utilizing the underlying system and sources by decreasing overhead.

Now we all know what containers are. Let’s get some high-level understanding of how Docker works. I’ll briefly introduce the technical phrases which can be used usually.
What’s Docker?
To grasp how Docker works, let’s have a quick take a look at its structure.
Docker makes use of a client-server structure containing three most important elements: A Docker consumer, a Docker daemon (server), and a Docker registry.
The Docker consumer is the first solution to work together with Docker by means of instructions. We use the consumer to speak by means of a REST API with as many Docker daemons as we would like. Typically used instructions are docker run, docker construct, docker pull, and docker push. I’ll clarify later what they do.
The Docker daemon manages Docker objects, reminiscent of photos and containers. The daemon listens for Docker API requests. Relying on the request the daemon builds, runs, and distributes Docker containers. The Docker daemon and consumer can run on the identical or totally different methods.
The Docker registry is a centralized location that shops and manages Docker photos. We will use them to share photos and make them accessible to others.
Sounds a bit summary? No worries, as soon as we get began will probably be extra intuitive. However earlier than that, let’s run by means of the wanted steps to create a Docker container.

What do we have to create a Docker container?
It’s easy. We solely have to do three steps:
- create a Dockerfile
- construct a Docker Picture from the Dockerfile
- run the Docker Picture to create a Docker container
Let’s go step-by-step.
A Dockerfile is a textual content file that incorporates directions on the right way to construct a Docker Picture. Within the Dockerfile we outline what the applying seems like and its dependencies. We additionally state what course of ought to run when launching the Docker container. The Dockerfile consists of layers, representing a portion of the picture’s file system. Every layer both provides, removes, or modifies the layer beneath it.
Primarily based on the Dockerfile we create a Docker Picture. The picture is a read-only template with directions to run a Docker container. Photos are immutable. As soon as we create a Docker Picture we can not modify it anymore. If we need to make modifications, we will solely add modifications on prime of current photos or create a brand new picture. After we rebuild a picture, Docker is intelligent sufficient to rebuild solely layers which have modified, decreasing the construct time.
A Docker Container is a runnable occasion of a Docker Picture. The container is outlined by the picture and any configuration choices that we offer when creating or beginning the container. After we take away a container all modifications to its inside states are additionally eliminated if they don’t seem to be saved in a persistent storage.
Utilizing Docker: An instance
With all the speculation, let’s get our arms soiled and put every part collectively.
For example, we are going to bundle a easy ML mannequin with Flask in a Docker container. We will then run requests towards the container and obtain predictions in return. We’ll prepare a mannequin regionally and solely load the artifacts of the skilled mannequin within the Docker Container.
I’ll undergo the overall workflow wanted to create and run a Docker container along with your ML mannequin. I’ll information you thru the next steps:
- construct mannequin
- create
necessities.txt
file containing all dependencies - create
Dockerfile
- construct docker picture
- run container
Earlier than we get began, we have to set up Docker Desktop. We’ll use it to view and run our Docker containers afterward.
1. Construct a mannequin
First, we are going to prepare a easy RandomForestClassifier on scikit-learn
’s Iris dataset after which retailer the skilled mannequin.
Second, we construct a script making our mannequin accessible by means of a Relaxation API, utilizing Flask. The script can also be easy and incorporates three most important steps:
- extract and convert the information we need to go into the mannequin from the payload JSON
- load the mannequin artifacts and create an onnx session and run the mannequin
- return the mannequin’s predictions as json
I took a lot of the code from right here and right here and made solely minor modifications.
2. Create necessities
As soon as now we have created the Python file we need to execute when the Docker container is working, we should create a necessities.txt
file containing all dependencies. In our case, it seems like this:
3. Create Dockerfile
The very last thing we have to put together earlier than having the ability to construct a Docker Picture and run a Docker container is to write down a Dockerfile.
The Dockerfile incorporates all of the directions wanted to construct the Docker Picture. The commonest directions are
FROM
— this specifies the bottom picture that the construct will prolong.WORKDIR
— this instruction specifies the “working listing” or the trail within the picture the place information might be copied and instructions might be executed.COPY
— this instruction tells the builder to repeat information from the host and put them into the container picture.RUN
— this instruction tells the builder to run the desired command.ENV
— this instruction units an surroundings variable {that a} working container will use.EXPOSE
— this instruction units the configuration on the picture that signifies a port the picture want to expose.USER
— this instruction units the default consumer for all subsequent directions.CMD ["
— this instruction units the default command a container utilizing this picture will run.", " "]
With these, we will create the Dockerfile for our instance. We have to comply with the next steps:
- Decide the bottom picture
- Set up software dependencies
- Copy in any related supply code and/or binaries
- Configure the ultimate picture
Let’s undergo them step-by-step. Every of those steps ends in a layer within the Docker Picture.
First, we specify the bottom picture that we then construct upon. As now we have written within the instance in Python, we are going to use a Python base picture.
Second, we set the working listing into which we are going to copy all of the information we want to have the ability to run our ML mannequin.
Third, we refresh the bundle index information to make sure that now we have the newest accessible details about packages and their variations.
Fourth, we copy in and set up the applying dependencies.
Fifth, we copy within the supply code and all different information we want. Right here, we additionally expose port 8080, which we are going to use for interacting with the ML mannequin.
Sixth, we set a consumer, in order that the container doesn’t run as the basis consumer
Seventh, we outline that the instance.py
file might be executed once we run the Docker container. With this, we create the Flask server to run our requests towards.
Moreover creating the Dockerfile, we will additionally create a .dockerignore
file to enhance the construct velocity. Just like a .gitignore
file, we will exclude directories from the construct context.
If you wish to know extra, please go to docker.com.
4. Create Docker Picture
After we created all of the information we would have liked to construct the Docker Picture.
To construct the picture we first have to open Docker Desktop. You may verify if Docker Desktop is working by working docker ps
within the command line. This command reveals you all working containers.
To construct a Docker Picture, we have to be on the identical degree as our Dockerfile and necessities.txt
file. We will then run docker construct -t our_first_image .
The -t
flag signifies the title of the picture, i.e., our_first_image
, and the .
tells us to construct from this present listing.
As soon as we constructed the picture we will do a number of issues. We will
- view the picture by working
docker picture ls
- view the historical past or how the picture was created by working
docker picture historical past
- push the picture to a registry by working
docker push
5. Run Docker Container
As soon as now we have constructed the Docker Picture, we will run our ML mannequin in a container.
For this, we solely have to execute docker run -p 8080:8080
within the command line. With -p 8080:8080
we join the native port (8080) with the port within the container (8080).
If the Docker Picture doesn’t expose a port, we may merely run docker run
. As an alternative of utilizing the image_name
, we will additionally use the image_id
.
Okay, as soon as the container is working, let’s run a request towards it. For this, we are going to ship a payload to the endpoint by working curl
X POST http://localhost:8080/invocations -H "Content material-Sort:software/json" -d @.path/to/sample_payload.json
Conclusion
On this article, I confirmed you the fundamentals of Docker Containers, what they’re, and the right way to construct them your self. Though I solely scratched the floor it ought to be sufficient to get you began and be capable to bundle your subsequent mannequin. With this information, you must be capable to keep away from the “it really works on my machine” issues.
I hope that you simply discover this text helpful and that it’s going to assist you to grow to be a greater Information Scientist.
See you in my subsequent article and/or depart a remark.