dave/site
1
0
Fork 0
mirror of https://github.com/davegallant/davegallant.github.io.git synced 2025-08-14 12:20:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

deploy: 9b36effd5ed1f10049e7f786bfa6a05ed50affdd

Browse Source
This commit is contained in:
davegallant
2021-10-12 02:08:56 +00:00
parent bcaac32ce2
commit 528802fb70
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
blog/2021/10/11/replacing-docker-with-podman-on-macos-and-linux/index.html
View File

@@ -157,7 +157,7 @@ personal blog
<p>Docker has been one of the larger influencers in the container world, helping to standardize the (<a href=https://github.com/opencontainers/image-spec/blob/main/spec.md>OCI Image Format Specification</a>). For many developers, containers have become synonymous with terms like docker, and the <code>Dockerfile</code> being a file that contains the instructions on how to build an image. Docker has certainly made it very convenient to build and run containers, but it is not the only solution for doing so.</p>
<h3 id=what-are-containers>What are containers?</h3>
<p>A container is a standard unit of software that packages up all application dependencies within it. Multiple containers can be run on a host machine all sharing the same kernel as the host. In Linux, namespaces help provide an isolated view of the system: including networking, PIDs, UIDs, and mounts. There is an <a href="https://www.youtube.com/watch?v=sK5i-N34im8">in-depth video</a> that discusses what containers are made from, and <a href="https://youtu.be/sK5i-N34im8?t=2468">near the end</a> there is a demonstration about how to build your own containers on the command line.</p>
<p>By easily allowing the necessary dependencies to live alongside the application code, the &ldquo;works on my machine&rdquo; problem is less of a problem.</p>
<p>By easily allowing the necessary dependencies to live alongside the application code, containers make the &ldquo;works on my machine&rdquo; problem is less of a problem.</p>
<h3 id=benefits-of-podman>Benefits of podman</h3>
<p>One of the most interesting features of podman is that it is daemonless. There isn&rsquo;t a process running on your system managing your containers. In contrast, the docker client is reliant upon the docker daemon (often running as root) to be able to build and run containers.</p>
<p>Podman is rootless by default. It is now possible to <a href=https://docs.docker.com/engine/security/rootless/>run the docker daemon rootless</a> as well, but it&rsquo;s still not the default behaviour.</p>