diff --git a/articles/2016-05-26-Docker-Taming-the-Beast-Part-1.md b/articles/2016-05-26-Docker-Taming-the-Beast-Part-1.md index 52ec8ad..9573c70 100644 --- a/articles/2016-05-26-Docker-Taming-the-Beast-Part-1.md +++ b/articles/2016-05-26-Docker-Taming-the-Beast-Part-1.md @@ -20,7 +20,7 @@ The idea seemed very attractive to me, even more because I recently switched to In another word, my goal in this first post is to spare you the trouble of fishing for information about Docker to understand it as well as sharing the love about Docker, of course! 5 days a week I'm hanging on the #docker IRC chan (I'm **nschoe** by the way, if you want to come and say hello :-)) and too many times I see newcomers asking questions that clearly indicates they are missing some very important base notions: if you're in that case, I hope to help you in this series of articles. Let's fix that together! ![](/images/warning.png "Notice")I just want to clarify that Docker (and more generally _software containers_) is a complex topic, that goes back all the way down to the _kernel_. I'm not a Docker developers and I'm not an expert on the field. I just like to _understand_, and I work better if I really get what's going under the hood. -I'll do my best to transmit what I understand of all of this, but if you spot any mistakes, **please** don't hesitate to [shoot me an email](mailto:ns.schoe@gmail.com) to let me know, I'll fix it. +I'll do my best to transmit what I understand of all of this, but if you spot any mistakes, **please** don't hesitate to [shoot me an email](mailto:nschoe@protonmail.com) to let me know, I'll fix it. Likewise, if you're a newcomer and think I missed a point or left a gray area, tell me so I can fill in the gap! In this first post, we won't play with Docker directly, we won't issue any `docker` commands, but we will understand the basics, the _fundamentals_: what's going on under the hood. But don't worry, we _will_ start playing with Docker right from part 2! @@ -421,9 +421,9 @@ Depending on your personality and expectations, you might be frustrated after re Too often I see people coming on the #docker IRC chan and ask questions which show that they are trying to use docker like they are trying to use a new text editor. Docker is not simple. The tools on which Docker relies are not trivial. Docker does a wonderful job of packaging complex, low-level tools into a simple, beautiful API (and it has very [well-written documentation](https://docs.docker.com/engine/)). But it still remains that the overall system is a beautifully complex one. It is relatively easy to get a few containers running with Docker, because it makes such a beautiful job of abstracting the complexity away, but if you don't take the time to analyze, document and _understand_ what is going on under, you will quickly run into walls: you won't understand the notion of images vs. containers (topic of next post!), you won't be able to share your environment, you will have your disk space used by up unnecessary redundancy, etc. -On the contrary, you don't need to be an expert in every of the details we saw: I am not myself. This is why I did no go into too much details. Feel free to document more on the topics you want, and if there are topics you'd like me to talk about more in-depth, [email me](mailto:ns.schoe@gmail.com). +On the contrary, you don't need to be an expert in every of the details we saw: I am not myself. This is why I did no go into too much details. Feel free to document more on the topics you want, and if there are topics you'd like me to talk about more in-depth, [email me](mailto:nschoe@protonmail.com). -I hope I was clear enough and that I shed some lights on some concepts that were obscure, if you still have gray areas, feel free to [email me](mailto:ns.schoe@gmail.com) or poke me (**nschoe**) on IRC (`#docker`). +I hope I was clear enough and that I shed some lights on some concepts that were obscure, if you still have gray areas, feel free to [email me](mailto:nschoe@protonmail.com) or poke me (**nschoe**) on IRC (`#docker`). In the next article, I will relieve some of the frustration and we will begin playing with "real" `docker` commands. In the meantime, you don't need to do anything specific, I'll begin the next article with the installation instructions. **Part II is available to read [here](/articles/2016-07-03-Docker-Taming-the-Beast-Part-2.html)**! diff --git a/articles/2016-07-03-Docker-Taming-the-Beast-Part-2.md b/articles/2016-07-03-Docker-Taming-the-Beast-Part-2.md index 66b5927..beba8ef 100644 --- a/articles/2016-07-03-Docker-Taming-the-Beast-Part-2.md +++ b/articles/2016-07-03-Docker-Taming-the-Beast-Part-2.md @@ -180,7 +180,7 @@ So back to our `docker run ubuntu`, we created and started a process from the `u This allows me to highlight another specificity of docker containers: they stop when their PID 1 process terminates. This is important: when the process you are running inside your container exits/returns/terminates/crashes, the docker containers stops, because it has nothing to do anymore. -Here it is, I hope I was crystal-clear about the differences between images and containers, because that is arguable the _most important part_ of docker for a newcomer. If you have _any hesitation_, **do not** pursue further: take a break, re-read this part and [shoot me an email](mailto:ns.schoe@gmail.com) if you have to. +Here it is, I hope I was crystal-clear about the differences between images and containers, because that is arguable the _most important part_ of docker for a newcomer. If you have _any hesitation_, **do not** pursue further: take a break, re-read this part and [shoot me an email](mailto:nschoe@protonmail.com) if you have to. ![](/images/warning.png "") I have been using the class / object analogy quite a lot, but this is just a simple analogy to give you the feeling. It doesn't mean that they are implemented in terms of class and objects. Besides, don't push the analogy further than what I intended: do not look for concepts of heritage, polymophism, etc. It should be obvious, but one is never careful enough and I just wanted to highlight that. @@ -1075,6 +1075,6 @@ The first two articles were---I think---the most theoretical. But it was necessa I hope I made the docker concepts clear, this was the goal of this article. From now one, the articles will be shorter---at least I think!---and _definitely_ more applied. I believe I have covered the majority of the docker concepts that can be applied to build complex setups. It's important that you keep everything we saw in mind, before now, in the following articles, we will apply all of these concepts. -As usual I will try to give as many examples as possible to give you _insights_ and material to go on. I'm not yet settled on the next article, but there's a high probability that we will cover the process of building images and writing Dockerfiles. If you have a personal suggestion, don't hesitate to [shoot me an email](mailto:ns.schoe@gmail.com) and I'll see what I can do! +As usual I will try to give as many examples as possible to give you _insights_ and material to go on. I'm not yet settled on the next article, but there's a high probability that we will cover the process of building images and writing Dockerfiles. If you have a personal suggestion, don't hesitate to [shoot me an email](mailto:nschoe@protonmail.com) and I'll see what I can do! **Part III is available to read [here](/articles/2016-10-12-Docker-Taming-the-Beast-Part-3.html)**! diff --git a/site.hs b/site.hs index 2132973..5f18747 100644 --- a/site.hs +++ b/site.hs @@ -106,7 +106,7 @@ nschoeslabsRSSConfig = FeedConfiguration { feedTitle = "nschoe's labs" , feedDescription = "Haskell, Artificial Intelligence and WebRTC." , feedAuthorName = "Nicolas SCHOEMAEKER" - , feedAuthorEmail = "ns.schoe@gmail.com" + , feedAuthorEmail = "nschoe@protonmail.com" , feedRoot = "http://www.nschoe.com" } diff --git a/templates/articles.html b/templates/articles.html index 2b762ce..2c806b2 100644 --- a/templates/articles.html +++ b/templates/articles.html @@ -1,5 +1,5 @@ Here is what I wrote so far, hope you find something of interest.
-If you have any suggestions, please contact me. +If you have any suggestions, please contact me. \ No newline at end of file + diff --git a/templates/default.html b/templates/default.html index d76fb8a..557fdd9 100644 --- a/templates/default.html +++ b/templates/default.html @@ -2,7 +2,7 @@ - + @@ -24,7 +24,7 @@ A.I. WebRTC About - Contact + Contact RSS feed logo