I believe it was an issue with my DNS server. Nevertheless, the issue cannot be reproduced so the bug report can be closed.

@n.fort
Nope, no VRF set up.

@Viacheslav
I will check it today or tomorrow. But I believe I know the culprit, the new firewall rules didn't allow my VyOS instance to contact the CoreDNS (set to host mode) container that is hosted as a container in VyOS. I was unable to ping 127.0.0.1 as well as all of my VyOS's IP addresses.

If I pre-load my zone firewall with the new interface format (pod-$containerName) and upgrade to vyos-1.4-rolling-202304290647, it seems to upgrade seamlessly

Certbot (specifically certbot/dns-cloudflare container) is another situation where a command & argument is required. Currently, I get around it by running a task-schedule to run the podman command directly (its a task because the container runs to completion). But having a way to do this via VyOS CLI would be extra helpful.

I can confirm the firewall errors are fixed in the newest rolling VyOS 1.4-rolling-202212070318

A simple work around could be to trigger a podman start command when a restart container $CONTAINER_NAME is entered. If the pod isnt already running or in a stopped state, it will look at the config and start it up.

You are correct, my config is not correct.

I was able to test and get a screenshot of the exact error eapol spits out when using certstore as well.