I think there’s a problem with Orthanc’s use of the MySQL connection when a user has been configured on the MySQL server to connect from a specific network.
On our database server, we are restricted to using accounts from a known network (we’re in an ephemeral environment) and due to security policies, unable to use a global user account (“user”@“%”). Therefore, our only option is to configure a user with a network and subnet mask (“user”@“192.168.56.0/255.255.255.0”).
When Orthanc starts up, there’s an error connecting to the MySQL database as it appears that the network and subnet mask gets parsed incorrectly. The logging reads:
Please provide us with a way to start MySQL in Docker using such a mask, so that the core development team of Orthanc can independently reproduce your setup on their computer: https://hub.docker.com/_/mysql
I’m working on providing you this - but it’s not overly easy within Docker as you can’t ascertain which IP address Docker is going to be using and that is the core of the issue. It’s easier with multiple VMs as you can set up MySQL in a known network and configure it to only permit IPs from the same network.
Would providing an OVA with this set up, or utilizing VirtualBox / VMware be acceptable?
This would certainly be acceptable to provide a minimal working example.
However, I would highly suggest you to take advantage of technologies like Vagrant, that can automate the provisioning of multiple virtual machines without distributing several OVA: https://en.wikipedia.org/wiki/Vagrant_(software)