Is there a containerized MID server (Docker/etc.)?

[Kerry Hormann]

Is anyone working on a containerized version of the MID server software?  I have built my own stuff, but the Tanuki service wrapper is REALLY getting in the way, basically making the container idea non-workable.

If you like the idea of containerization but don't have a solution, please up-vote the idea I posted on this forum!

[pain]

I never use the daemon wrapper. I directly just use the start n stop.sh scripts. That way I was able to install multiple. I am running Orlando version.

[lasse3]

There is one on GitHub that actually works. You need to update the image with the ZIP file for your current version of ServiceNow, but other than that it is good to go.

https://github.com/andrekosak/docker-sn-midserver

I am working on an updated version that gets the MID server file automatically based on you ServiceNow version, which I plan to put on GitHub for everybody to enjoy 🙂

Let me know if you would be interested in getting a beta version to play with.

[Kerry Hormann]

Thank you lasse, but as I stated in previous comments, this uses supervisord, and is not a true "containerized application", merely another wrapper to the existing problem.

Containers are DEFINED as “a collection of binaries required to run an application”. The implicit expectation is that the “version” does not change – that the binaries in said container should not be updated – or the container will be rebuilt/published with a new version/tag.

Imagine a (only slightly contrived) DR scenario – the physical system the container was running on has died, and we need to spin-up a new one ASAP. I should be able to download the container’s image from the repository and apply a config (from Git or Puppet) and it’s back online. No intermediary upgrade/change process should be required to return the new container to the same pre-crash version/state.

Using "supervisord" enables the upgrade script, which breaks the fundamental concept of a container.

[lasse3]

Hi Kerry,

I hear what you are saying. I do not think that there is anything out there that will give you this experience.

I have just completed a debian based docker image, that takes the URL to the MID Server ZIP as an input. This way you can always spin up a new container using what ever version of ServiceNow that you would like.

https://github.com/LasseAhhMann/sn-mid-server

I know that it is not exactly what you are asking for, but it will give you the flexibility to spin up a container for any version of ServiceNow.

/Lasse

[Kerry Hormann]

Thank you.  Although we are moving to containers, I currently have a VM, which solves my needs at the moment.  This question is really intended to generate interest, hopefully in getting the developers to re-think their implementation.

If you support this concept, please consider voting for the idea I posted.  The more votes it gets, the more we can lean on ServiceNow to get rid of Tanuki!