A
asthomas
Guest
Hi Simon, What we have done so far is take a copy of a local install of OpenEdge on linux, tweaked it a little and then added this to a docker build as the base image. We then have other images built from this for special purposes. So for example, we have whogloo/openedge116 - as the base image whogloo/appserver116 - which has been built FROM whogloo/openedge116 with a separate Dockerfile. This has various things to support AppServer, aia, and more. One of the challenges with OpenEdge is that there are many components to an OE installation, so it is difficult to build images that follow the general rule of thumb with one container for one process. You also run into challenges with databases and dynamic ports. If you need shared memory access to your databases, you have to run databases and e.g. AppServer inside the same container, etc. etc. We have a working setup though where we can easily provision various OpenEdge related container collections with nice things custom URLs so that you can access the admin server, appserver etc for each of your containers.
Continue reading...
Continue reading...