This document discusses Azure AI on-premises using Docker containers. It covers Microsoft Cognitive Services, Docker, and Azure Cognitive Services containers. The key points are: - Microsoft Cognitive Services are AI algorithms that can be consumed via REST APIs to solve problems in areas like computer vision, natural language processing, and speech recognition. - Docker containers allow these cognitive services to run locally on-premises for applications that cannot send data to the cloud. The containers package the services and their dependencies to run consistently on any infrastructure. - A live demo will show how to utilize Docker containers for Azure Cognitive Services on an on-premises server to bring AI capabilities locally without needing internet access. Questions will be

1. Azure AI on premises
with Docker
@vishwasnarayan5 Vishwas N
https://hacksterdude.web.app/

2. About me
I am a Podcaster : http://tiny.cc/vnrpodcast
I love to talking to techies
A Bibliophile
Passionate about Image dataset - Computer Vision
Now exploring Azure cloud

3. Agenda
● Microsoft Cognitive Service
● Docker
● Azure Cognitive Services Containers
● Live Demo
● Q/A

4. Definition of AI
The replication of human intellectual
processes by machines, particularly
computer systems, is known as artificial
intelligence. Expert systems, natural
language processing, speech
recognition, and machine vision are
examples of AI applications.

5. Cognitive Service
Cognitive services are a set of automatic
learning algorithms that Microsoft was
developed to solve problems in the field of
artificial intelligence (AI). The goal of
cognitive services is democratized to
packing it into discrete components that
are easy to use for developers in their
applications. Developers of Windows and
Universal Windows platforms can
consume these algorithms through
standard rest calls through the Internet to
the cognitive service bees.

6. Containers Introduction

7. All of it started as a problem statement to make life easier
Lot of questions that they asked?
● When to pach
● When to create a backup
● When to upgrade the service

8. Getting started with container
1. Why containers?
2. What is the purpose of Building containers and Docker mainly
3. What is the main reason behind doing it?

9. How to utilize the hardware

11. Container are very light weight
SERVER
HOST OS
GUEST OS
HYPERVISOR
LIBRARIES/Bin
APP A
GUEST OS
LIBRARIES/Bin
APP B
VM
SERVER
HOST OS
APP A APP B
LIBRARIES LIBRARIES
CONTAINER
S
• Containers are isolated but share OS
• Increase the compute density and
memory utilization
DOCKER ENGINE

13. Virtual Machine
Container

14. Scalable by Design
● Containers are industry leaders in the time to start new instance
● Container spin time for new instance takes seconds
● Provisioning and starting new Virtual Machines takes from 5 to 20 minutes

15. Container + Microservice
● One microservice application = one container
● Granular fast scalability
● Similar experience on workstation and production
● Hybrid environments: deploy to cloud and on-premise

16. Container commands

18. Source : docker | Docker Documentation

20. Containers Introduction

21. All of it started as a problem statement to make life easier
Lot of questions that they asked?
● When to pach
● When to create a backup
● When to upgrade the service

22. Getting started with container
1. Why containers?
2. What is the purpose of Building containers and Docker mainly
3. What is the main reason behind doing it?

23. How to utilize the hardware

25. Container are very light weight
SERVER
HOST OS
GUEST OS
HYPERVISOR
LIBRARIES/Bin
APP A
GUEST OS
LIBRARIES/Bin
APP B
VM
SERVER
HOST OS
APP A APP B
LIBRARIES LIBRARIES
CONTAINER
S
• Containers are isolated but share OS
• Increase the compute density and
memory utilization
DOCKER ENGINE

27. Virtual Machine
Container

28. Scalable by Design
● Containers are industry leaders in the time to start new instance
● Container spin time for new instance takes seconds
● Provisioning and starting new Virtual Machines takes from 5 to 20 minutes

29. Container + Microservice
● One microservice application = one container
● Granular fast scalability
● Similar experience on workstation and production
● Hybrid environments: deploy to cloud and on-premise

30. Container commands

32. Source : docker | Docker Documentation

34. Building a Dockerfile

35. Some Command/lines of code that are very
important

36. Lets know some docker terms
Images - docker images
Tags/Layers - -t [tagname] , docker tag [source-images] [tagged-name]
Containers : docker container ls ,docker ps -a
Dockerfile : docker build -t [container-name] . (ful stop in end is very important)
Commit : docker commit [container-id] [tag-name]
Docker Hub/Container Registry : docker push [image-name]

37. Dockerfile instruction or argument
FROM
LABEL
RUN
WORKDIR
ADD
CMD

38. Dockerfile instruction or argument
● FROM
● LABEL
● RUN
● WORKDIR
● ADD
● CMD
● ARG
Thus study the documentation you will all lie it : Dockerfile
reference | Docker Documentation

39. From Dev To Ops
PHYSICAL VIRTUAL CLOUD
Any Application

40. Docker Platform
Docker Image
Docker Engine
Registry Service (Docker Hub or Docker Trusted Registry)
Cloud or server based storage and distribution service for images
Docker Container

42. Docker Hub: Build, Ship, Run Applications
Build Ship
Run
Dev
QA
Source
Staging
Physical
Virtual
Cloud
InfrastructureManagement
InfrastructureManagement
DockerFile
Source Code
Repository
TEST
TEST
TEST
TEST
TEST
GCE RAX Azure
Mac/Win Dev
Machine
Boot2Docker
Docker
Analytics
DB
Prod
Machine
Linux OS
Docker
Docker
++
Users Collab
Provenance Policy
Docker Hub
Registries
Public Curated Private
Docker Hub API
Third Party Tools
Prod
Machine
Linux OS
Docker
Docker
Prod
Machine
Linux OS
Docker
Docker
VM
Docker
Docker
VM
Docker
Docker
VM
Docker
Docker
QA Machine
Linux OS
Docker
Docker
Docker Hub provides a centralized resource for container image discovery,
distribution and change management, user and team collaboration, and workflow
automation

43. Docker Hub: Build, Ship, Run Applications
Build Ship
Run
Dev
QA
Source
Staging
Physical
Virtual
Cloud
InfrastructureManagement
InfrastructureManagement
DockerFile
Source Code
Repository
TEST
TEST
TEST
TEST
TEST
GCE RAX Azure
Mac/Win Dev
Machine
Boot2Docker
Docker
Analytics
DB
Prod
Machine
Linux OS
Docker
Docker
++
Users Collab
Provenance Policy
Docker Hub
Registries
Public Curated Private
Docker Hub API
Third Party Tools
Prod
Machine
Linux OS
Docker
Docker
Prod
Machine
Linux OS
Docker
Docker
VM
Docker
Docker
VM
Docker
Docker
VM
Docker
Docker
QA Machine
Linux OS
Docker
Docker
Docker Hub provides a centralized resource for container image discovery,
distribution and change management, user and team collaboration, and workflow
automation

45. Benefits of Containers
● Immutable Architecture
● Control over the Data
● Control over the Update
● Portable Architecture
● High Throughput and Low Latency
● Scalablity

46. Key Parameters
● API Key
● Billing
● EULA Agreement
● Application Insights
● Fluented
● HTTP Proxy
● Logging
● Mounts

47. When you run Containers
● Performs a feeling analysis container from the image of the
container
● assigns a core of the CPU and 8 Gigabyte (GB) of the
Memory
● exposes the TCP 5000 port and the assignment of Pseudo-
TTY for the container 443 TCP Port is used.
● Automatically deletes the container after it comes out. The
image of the container is still available on the host computer.

48. So let's go Hands ON