Hi Jan,
thank you for your thoughts.
The biggest hurdles
seem to be to get the container running and the ipa-server-install
properly finished the first time the container is started.
We simply run the
container manually from command line once, for further restarts we use a compose file for
docker swarm - we didn't encounter any issues there.
If you have infrastructure that is biased towards containers
(for example Kubernetes all over), you might pick that. You might gain
more flexibility in the setup and potentially a bit leaner solution.
It's also easier to get things confused and broken.
Since all the VMs we use
run Debian, setting up VMs with Fedora or RHEL would require an additional effort for us.
That's one of the main reasons why we'd like to go for containerization. As most
other things we run is in containers that fits well into our landscape.
Since for production deployment you will want to have a master plus
a couple of replicas, you can even mix and match.
That's something I had not
considered but is interesting and problably a help in case we need to migrate to VMs
later.
Thanks,
Jonas