Trying to deploy a bind slave on vyos as a secondary backup to the master hosted elsewhere.
However what ever container I deploy, regardless of how simple, I run into an error:
Failed to obtain podman configuration: runroot must be set
I tried copying and pasting the example from the docs and i get the same error.
Doing a little digging, if I run podman commands directly by calling podman on the CLI i’m able to interact with podman
vyos@Core-Router:~/podman/bind9/slave$ podman --version
podman version 4.3.1
vyos@Core-Router:~/podman/bind9/slave$ podman pull ubuntu/bind9:9.18-22.04_beta
docker.io/ubuntu/bind9:9.18-22.04_beta
Trying to pull docker.io/ubuntu/bind9:9.18-22.04_beta…
Getting image source signatures
Copying blob 453dc20a2d02 done
Copying blob 9e7b2fe80104 done
Copying blob 3d18cbd4c114 done
Copying config 7ae23a5b00 done
Writing manifest to image destination
Storing signatures
7ae23a5b00e8606785148ce40ff61ac070253f78fad1af790d9223e77c7a8d3f
vyos@Core-Router:~/podman/bind9/slave$ podman image ls
REPOSITORY TAG IMAGE ID CREATED SIZE
docker.io/ubuntu/bind9 9.18-22.04_beta 7ae23a5b00e8 47 hours ago 143 MB
However if i do this as root is also fails with the same error as the vyos config method:
sudo podman --version
Failed to obtain podman configuration: runroot must be set
I’m not very familiar with how vyos works under the hood. I notice the podman config in “/etc/containers/containers.conf” is generated by “/usr/libexec/vyos/conf_mode/container.py”.
Editing containers.conf manually to add runroot gets overwritten when back in the vyos config setup.
Has anyone had this issue before? Any tips to help solve it or is it just a bug 
Versions tried:
vyos-1.4-rolling-202305260317-amd64.iso
vyos-1.4-rolling-202305250317-amd64.iso
vyos-1.4-rolling-202305240317-amd64.iso
System:
VMware Workstation (labbing before bare metal deployment)
