A colleague of mine asked me today to prove that rootless podman has worse I/O performance than running podman as root. Which I claimed.
My instinct is that it gotta be worse, because fuse-overlayfs is overlayfs implementation in userspace, so it gotta be less performant than a kernel module. Let’s see.
sshnaidm gave me an opportunity to play with Ansible Collections today.
Since I was at AnsibleFest 2019 in Atlanta, I heard so much about the collections but never actually used them.
People on my team asked me some time ago how I debug things in our python code base. So I thought I’d share here.
The easiest (and least efficient) way to debug is to use print statements and
logging. But since you’re not using a real debugger, you need to update the
code and rerun in order to get new results.
Hence the most efficient way to debug things in python is to use a debugger. Don’t be scared, they are easy to master and they’ll serve you nicely for the rest of your life. They all are very similar.
This blog post is a guide coming from ansible-bender#49 issue.
Okay, let’s start.
Building from scratch, what does it mean? It’s very simple: your base image is an empty directory:
We’ve just hit this point in our project (packit) that we want to split it to two repositories: CLI tool and a web service. I was thinking of keeping the git history for files I want to move to the other repository. There is a ton tutorials and guides how to do such a thing. This is what worked for me: Clone the original repository. Have a list of files I want to remove:
I wanted to update my gentoo box once again. I did last update probably ~6 months ago. This usually means for me that I get a ton of conflicts:
Exciting times! I just released ansible-bender-0.5.0.
This update contains a ton of new stuff. There is the one feature I am very proud of — configuring the build process by using Ansible variables. Apart from that, I did a lot of bug fixes and usability improvements.