I’m familiar with both tools. I was expecting that toolbox somehow would allow for bootstrapping the container with IDK a yaml file or something like that which is then included with the toolbox create part. This yaml file could also be used for Ansible by including it in a loop for non Silverblue systems.
But I guess I’ll do it the other way around. I’ll create a templated Dockerfile with a package install list based on the package install list I have in Ansible. Then I’ll create a separation, a part will be installed with rpm-ostree and (a part) will be included in that Dockerfile. Then I’ll load that custom image with toolbox rather than a vanilla distro image. It’s not pretty, but it will keep things centrally organized.
I guess rkhunter, postfix, and other software that needs to run as a daemon/cron will be included in the Silverblue installation and the rest will be in the container.