<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Containers on Personal Blog of Maximilian Ehlers</title><link>https://blog.sodawa.com/tags/containers/</link><description>Recent content in Containers on Personal Blog of Maximilian Ehlers</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 13 Apr 2022 17:04:15 +0200</lastBuildDate><atom:link href="https://blog.sodawa.com/tags/containers/index.xml" rel="self" type="application/rss+xml"/><item><title>Postgres Update in Docker</title><link>https://blog.sodawa.com/blog/postgres-update-in-container/</link><pubDate>Wed, 13 Apr 2022 17:04:15 +0200</pubDate><guid>https://blog.sodawa.com/blog/postgres-update-in-container/</guid><description>I recently wanted to upgrade a postgres database to the latest version.
This is the workflow to achieve this with the following prerequisites:
Data of old database is inside new-data-folder Data of new database is at old-data-folder Both folders are inside the same directory Upgrading from 11 to 14 Your setup will surely differ, so just change the paths, download links and postgres version accordingly when using this.
podman pull docker.</description></item><item><title>Container Deep Diving: Part 3</title><link>https://blog.sodawa.com/blog/containers-deep-dive-part-3/</link><pubDate>Mon, 11 Apr 2022 11:42:42 +0200</pubDate><guid>https://blog.sodawa.com/blog/containers-deep-dive-part-3/</guid><description>After looking at the nitty gritty functionality of containers in Part 2 lets make life a bit easier now. First by making this post a short one and secondly by using tools for abstracting away the manual labour that had to be done in order to switch namespaces and set them up. For this lets take a look at container runtimes.
While you have probably heard of and used Docker lets talk about the common layer that underlies modern Docker and other runtimes.</description></item><item><title>Container Deep Diving: Part 2</title><link>https://blog.sodawa.com/blog/containers-deep-dive-part-2/</link><pubDate>Thu, 03 Feb 2022 11:42:42 +0200</pubDate><guid>https://blog.sodawa.com/blog/containers-deep-dive-part-2/</guid><description>Okay, so here we are in part 2 of the container post series.
At the end of part 1 we were able to identify the problems of just using chroot to achieve process isolation on a machine. With this post the goal is to have the same functionality - running bash with test-root as the new root directory with the same technologies as containers. Once that is running we will adress the problems of seeing all the network interfaces as well as still being able to kill arbitrary processes on the machine.</description></item><item><title>Container Deep Diving: Part 1</title><link>https://blog.sodawa.com/blog/containers-deep-dive-part-1/</link><pubDate>Fri, 07 Jan 2022 11:42:42 +0200</pubDate><guid>https://blog.sodawa.com/blog/containers-deep-dive-part-1/</guid><description>Containers serve 1 purpose. Selling kubernetes certificates! \s
But of course there is more to it then just hype.
Over the next few posts on my blog I would like to dig into the container world, see how we got to the current state and show what the current state actually is.
Overview So what is the real purpose of containers?
Isolate different families of processes on 1 computer from each other, so that if a process is ever compromised it does not affect any other processes on the same machine.</description></item></channel></rss>