This is a brand new script, which is the logical extension to the Nash!Com Domino Start script. A while ago I introduced Docker support for the start script inside the Domino container. It comes with an entry-point script we are also leveraging in out Domino Docker Github community script. This new script is intended to manage and run your Docker and Podman containers. It includes also a systemd script to run a Domino server on Podman in production using the new systemd options introduced in Podman 1.7+. Beside that it includes a simple framework to build and manage your own add-on images

Now that we have the Sametime Premium Meeting Server, there are more customers looking into Domino on Linux. In earlier days I had some issues getting the start script in combination with SLES working. So ST wasn't never on my support list.

I never said Docker is completely dead, even I see today better integration and more features in Podman. This new release of Docker CE is helping specially on CentOS 8 and you don't need to work-around compatibility issues with an older version of containerd shipped with CentOS 8. At the same time Docker updated Docker desktop to a new major version -- which also includes Docker version 20.10.

This week and I am migrating my Domino server to a new provider updating to CentOS 8. Because I am working a lot with Domino in the Docker/Podman/Kubernetes space, I am looking into it also for my own server. The big benefit is that I can apply my private "NashCom" image derived from the standard image to all servers needed without installation. And switching versions is means just a restart. My own image will be based on the Docker Project version and use the add-on functionality to build your own image on top of it. In my case to add all my tools starting with the "nsh.." prefix.. And also the Domino V12 DSAPI filter for Let's Encrypt/ACME integration.

We ran into this today. A customer is using ST Meetings Premium in their intranet and have no connection outside. This isn't only a challenge for software installation and updates, but also causes issues with ST meetings if the Google STUN servers cannot be reached. Side note: The update from Pre-Release to Premium by the way just took 1 hour for the meeting server, community server and proxy server all togehter! A STUN server is actually a TURN server, taking care that server and client can talk to each other if a NAT environment is involved. This can hit you even in an intranet depending on the network segmentation with IPv4 addressing. In case NAT is involved you would need an internal TURN server. If no NAT is involved you still have to disable the Google STUN servers.