Sam at the Bronx Zoo

When I switched to Twenty Nineteen almost a year ago, I wasn’t sure if I was going to stick with the theme so I never did my theme documentation blog post. So here’s what the previous theme, Twenty Sixteen, which I had for about 2.5 years, looked like:

And here are the previous theme changes:

/2018/12/14/just-switched-to-twenty-nineteen-theme/ /2015/04/21/lets-do-the-theme-change-again/ /2013/04/18/changing-themes-after-4-years/ /2009/02/05/changing-themes-again-2/ /2008/04/09/changing-themes-again/

/2007/09/30/a-reminder-of-my-previous-theme/

Over the years I’ve taken many, many photos of my kids at Coney Island. Lots of them have come out great. But I think this batch of photos is among the best photos I’ve taken of the kids at Coney Island thus far.

In some cases, it’s the expressions on the twins’ faces.

• 
• I’m on a motorcycle!
• 
• I see you!
• 
• Yeah, I know how to use this

Other times, I succeeded in getting the perfect action shot.

Turns out that on my Fedora 30 VM something got screwed up with the CNI networking (the networking that Podman uses) and instead of pointing to the address that Podman is using according to Cockpit:

10.88.0.1

It’s pointing somewhere else. I found that via iptables -L. Not sure how to fix it, though. When I tried, it complained:

“`87-podman-bridge.conflist’ not found”

But changing the hostname environment variable turned out to be the solution as I tested on my Fedora 31 VM:

Adding the –name mysql - it wasn’t enough to get the PHPIpam apache container to find the mysql container. They’re in the same pod, but something’s not quite right. So I decided to see if I could modify the config.php by mounting the container and modifying that.

# podman mount beautiful_gauss
/var/lib/containers/storage/overlay/5a33decc2cfad7e9bda5f9048d94a814267d954e97d5dd7befb057a84367f27a/merged

While this allowed me to see the config files and open them in vi (not included in the container) I could not modify the contents. I think the key is passing “phpIPAM5” (or whatever the pod is called) into the MYSQL_ENV_MYSQL_HOST environment variable. So let’s try that. First, I had to stop phpIPAM5. I’ve been using

Like these random container names that podman generated:

# podman ps
 CONTAINER ID  IMAGE                               COMMAND               CREATED        STATUS            PORTS                 NAMES
 b83a26bb2c5d  docker.io/library/mysql:5.6         mysqld                2 minutes ago  Up 2 minutes ago  0.0.0.0:8081->80/tcp  hungry_wilson
 f35ec64d3b3c  docker.io/pierrecdn/phpipam:latest  apache2-foregroun…  2 minutes ago  Up 2 minutes ago  0.0.0.0:8081->80/tcp  nice_johnson

Makes me think perhaps there should be a list of adjectives and names that shouldn’t go together?

I’ve been hearing about Podman for a while now - at Red Hat Summit and at various local Red Hat presentations. I’ve seen the slides where the RHEL presenter (it’s always the same guy, but I’m terrible with names - after a bit of research, I think it’s Dan Walsh) asks you to pledge to call them container images, not Docker images, etc. But up until now, even though I’m a huge Red Hat fan, I’ve continued to use Docker as my container engine because I am just running a few containers for myself. I don’t even use a one-machine Docker Swarm. I use docker-compose. And that’s just not something that Podman is ever going to officially support. This makes sense because Red Hat is thinking enterprise. And in the enterprise there are two scenarios: 1) Orchestration - vanilla Kubernetes, OpenShift, etc - and 2) are devs running docker run (or podman run) to test the images before putting them into the orchestrator. I’m an anti-pattern, even if I’m not the only one doing things this way.

When I tried to upgrade the laptop a couple days ahead of the Tuesday release date, assuming that the sources were as good as gold at that point, the upgrade process complained about the Kdevelop Python plugin and didn’t want to proceed. I figured if this persisted past Tuesday I would just use it as an opportunity to try out PyCharm Community Edition. But once Tuesday came around I was able to upgrade to Fedora 31 with nary a problem. So that was probably the smoothest upgrade I’ve had since Fedora Core 1.

Back when Fedora 30 came out, I updated my laptop, but I left my main computer and the HTPC on Fedora 29. The former because I was busy with something at the time and didn’t want the disruption of an upgrade; the latter because the family depends on it for entertainment. However, with Fedora 31 coming out next Tuesday, the support window of Fedora 29 is over. The HTPC didn’t give any issues when I started the upgrade (at of this time it’s still running the upgrade), but my main computer did. This time it complaint about ripright and whois-mkpasswd.

Just in time for Halloween I discovered the Dracula set of dark themes.They’ve got themes for nearly every code editor and shell/console program you can think of. Here’s Yakuake with the Dracula Konsole theme:

Yakuake with Dracula theme

And here’s Kate with the Dracula theme:

Kate with Dracula theme

I like the color scheme, but the font’s a bit small, so I might make a variant theme with a slightly larger font size.