Hello @empbilly
Welcome to the Bacularis User Group.
There are many scenarios and many ways to configure Bacula with Bacularis. Using Bacula server on VM and Bacularis in Docker container can be hard to achieve. Bacularis very closely works with Bacula and its configuration and for example to use configuration function the API needs direct access to Bacula configuration files.
This and other reasons cause that we provide Bacularis container images together with Bacula components inside (such as bacularis-api-sd or bacularis-api-fd...). The exception of that are two containers: bacularis-standalone that is just a "demo" of Bacularis with all Bacula components inside. The second exception is bacularis-web that is clear the web interface without API part.
I am afraid that none of these container images can easily work with your Bacula server in VM. Using it with your setup may require additional user work to adopt them to custom needs.
The easiest way for your environment seems to be use the bacularis-web container for the web interface and connect the Bacularis API installed directly on the VM (not in container). This way at least the web interface part will be inside container.
Good luck.
Best regards,
Marcin Haba (gani)
