Commit 48c00066 authored by Paddy's avatar Paddy 🐧

Fixed some more typo and separation between slides

parent 17c9e1df
Pipeline #562 passed with stage
in 2 minutes and 11 seconds
......@@ -73,7 +73,7 @@ Container are a way to have an application runnig safely and isolated without st
---
# Download, manage and run you container with Docker
## Download, manage and run you container with Docker
![Docker](https://upload.wikimedia.org/wikipedia/commons/4/4e/Docker_%28container_engine%29_logo.svg)
......@@ -153,6 +153,7 @@ $ docker run -d -p 8080:80 -v myVol:/usr/local/apache2/conf httpd
---
# Where do the containers come from?
----
## Where do the containers come from?
......@@ -183,11 +184,11 @@ $ docker run [options] image_name # We run the images and, if we don't have alr
---
# Container DIY: How to make a container at home
# Containers DIY: How to make a container at home
---
## Container DIY
## Containers DIY
Ok, now we know how to run a container.
......@@ -209,7 +210,7 @@ Docker define a DSL (Domain Specific Language) to declare each of this steps.
----
## Container DIY: An example
## Containers DIY: An example
```Dockerfile
FROM Alpine
......@@ -218,7 +219,7 @@ RUN echo "Hello World!"
----
## Container DIY
## Containers DIY
Once created our Dockerfile, we can build a container:
......@@ -228,16 +229,20 @@ $ docker build -f Dockerfile -t TagName
----
## Container DIY
## Containers DIY
Ok, nice, we can specific which packages we want, which command to run and docker will do that for us.
----
## Container DIY
## Containers DIY
But what if we want to make a container with a program that we wrote or that we must build from scratch?
We have to install all the dependencies or compile it and compy inside the imatge.
We have to install all the dependencies and compile it.
----
## Containers DIY
Is that clean and sane to do?
......@@ -247,7 +252,7 @@ Is that clean and sane to do?
----
## Container DIY
## Containers DIY
It's not clean because we have to install some packages only to compile our real application.
......@@ -255,7 +260,7 @@ Doing that we obtain only bigger container (and with higer chance to be compromi
----
## Container DIY
## Containers DIY
A solution to this problem are the multi-stage builds.
......@@ -337,7 +342,7 @@ volumes:
- [Docker](https://www.docker.com/)
- [Dockerfile Reference](https://docs.docker.com/engine/reference/builder/)
- [What even is a container](https://jvns.ca/blog/2016/10/10/what-even-is-a-container/)
---
......@@ -369,5 +374,8 @@ We can use:
If you are using SELinux on your system (e.g. CentOS, Fedora, RHEL), you could have an hard time to find the right policy to apply to your process (e.g. when mounting a volume).
SELinux will block the process to acess a file (unless you disable selinux or force a relabel in the volume, but if you do that you should burn in hell).
You can get help with that using a tool called [Udica](https://github.com/containers/udica)[uɟit͡sa], this tool will help you to create custom security profiles that will be used from SELinux.
----
## Using container with SELinux
You can get help with that using a tool called [Udica](https://github.com/containers/udica)[uɟit͡sa], this tool will help you to create custom security profiles that will be used from SELinux.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment